-
Notifications
You must be signed in to change notification settings - Fork 98
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
Tracking Issue: Rust Embedded on Mastodon #647
Comments
I'm happy to help also in favour of hachyderm.io (biased cos I already have an account there) I believe @thejpster is also there. We should definitely have some guidelines around how to operate such account. |
I'm @thejpster@hachyderm.io. I understant Kris at Hachyderm.io, like many volunteer instance mods, has a lot going on right now. So whoever we approach we should do it with care and understanding. |
Hachyderm has had a big infra upgrade. Could be a good home now the dust has settled. |
Sounds good to me! I've set up @rustembedded@hachyderm.io, and am just sorting out having it go to the resources team email address. As far as I could tell there's no reason not to just create the account their; registrations are open. I don't think there's any way to share ownership beyond just sharing the password, which I'm happy to do. We should work out some basic principles for operating the accounts as @jamesmunns suggested; perhaps something like:
How does that sound? |
Sounds good to me |
yup, good starter for ten. |
Lemme write up a quick first draft of a "social media operational guide" as a PR. I'll find a home somewhere in the current wg repo. |
Opened #651, feel free to add any feedback or suggestions there. |
@adamgreig also let me know when you want me to tweet/chost about the hachyderm account. |
Following up from chat, we probably want to have some kind of presence on Mastodon/fediverse.
The two main open questions:
Who is going to run it?
IMO (@jamesmunns): whoever runs it should be on the Resources team. We should also figure out how to share access to the account to avoid it getting abandoned, etc.
We may want an existing RE member, maybe @thejpster or @adamgreig, to help mentor whoever runs the account.
@jamesmunns can help with "open source brand" style and coming up with general practices to be consistent with the twitter and cohost accounts.
Which server should it be on?
There are open discussions on this. Chat discussed:
Feel free to discuss either question below, once we have answers for both, we can move forward with making the account.
The text was updated successfully, but these errors were encountered: