Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Social Media Strategy #678

Open
noelmiller opened this issue Nov 16, 2024 · 3 comments
Open

Social Media Strategy #678

noelmiller opened this issue Nov 16, 2024 · 3 comments

Comments

@noelmiller
Copy link
Member

Purpose

I would like to talk about our social media strategy.

Current State

Joseph runs the Universal Blue Mastodon

Jorge posts about Bluefin on his personal accounts as well as Discourse announcement posts.

Valerie currently runs the Bazzite Bluesky account. Bazzite also exists on Reddit which includes Kyle and Antheas in there.

It is obvious we also have a shared discord and a Discourse that hosts both projects with announcements in each.

Discussion

My personal view on the situation is Bazzite and Bluefin should have decisions about their socials controlled by Kyle and Jorge.

I believe this discussion should focus on whether universal blue should have any social presence at all. I think that the focus should be on the products and not on the group itself. I also think that the socials should not be a support engagement tool and should always shepherd people to the appropriate avenues for that.

Results of what I am proposing? We just do away with the mastodon and not create any extra social media accounts for Universal Blue. The focus should be on Bazzite and Bluefin.

Thoughts?

@castrojo
Copy link
Member

I'll summarize my thoughts from chat:

I think it's all about the end user products. The analogy is, no one cares about "The Volkswagen Group", they care about Audi, Porsche, Ducati, etc.

I originally agreed to having social accounts because Joseph has a proven track record with Fedora and sharing the media person was a nobrainer. I'm for sure not keen on having a single person run it, if we do it it needs to be shared maintenance with proper community review of everything that gets posted.

I'd +1 a shared repo using an automated tool that people could PR announcements in with another ack from a trusted person. Or just piping the announcements tag from discourse to it, etc. and never dealing with it again is also totally fine and would easily solve the problem.

Not keen on engaging with people individually on social, we set up Discourse for a reason. If people want to do social things they can ping a contributor instead. As I said in chat, our focus should be on contributors (who will use github anyway), and our target audiences, which aren't on Mastodon.

@xynydev
Copy link
Member

xynydev commented Nov 16, 2024

and our target audiences, which aren't on Mastodon.

I've seen a fair few Bazzite lovers on Mastodon by accident. But yes, the less Linux nerd type of users are probably well reached elsewhere.

@fiftydinar
Copy link
Contributor

fiftydinar commented Nov 16, 2024

If you go on making a bot to automatically post announcements in other social media platforms, then it would be good to disable comments & in every post to have an ending message which would direct users to the official source to comment there instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants