Skip to content
New issue

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

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

Already on GitHub? # to your account

Strategy for blog and social media #878

Open
cahfofpai opened this issue Feb 10, 2025 · 6 comments
Open

Strategy for blog and social media #878

cahfofpai opened this issue Feb 10, 2025 · 6 comments

Comments

@cahfofpai
Copy link
Contributor

This proposal has been created together with @jbruechert.


Currently, Transitous has no real channel to inform about project updates or other news related to the project. It could be changed in this way:

Create a Mastodon account and use it for:

  • small project updates
  • boosting posts related to the project (e.g. posts by apps using the API of Transitous)

Create a blog inside the website and use it for:

  • updates and information which do not fit inside a Mastodon post
  • don't use it for: Regular updates (e.g. monthly) which report about everything which happened inside the project, because this would be very resource intensive

For the Mastodon account, there are still a few questions to be clarified:

  • Who should have access to it?
  • Who takes care of it? E.g. posting, boosting and writing answers for comments and direct messages?

What do you think about this proposal?

@cahfofpai
Copy link
Contributor Author

This issue is for the overall strategy, #841 is rather for the technical implementation of the blog.

@AimPizza
Copy link

Am I right to understand that the blog would feature some details about updates? That'd be really cool to have as an rss feed aswell.

@cahfofpai
Copy link
Contributor Author

Am I right to understand that the blog would feature some details about updates? That'd be really cool to have as an rss feed aswell.

I took it for granted that the blog would automatically have a RSS feed 😉.

@1Maxnet1
Copy link
Contributor

I agree on the strategy. It seems sensible and we will see how regular the updates come, based on how much change happens.

Regarding your questions:

Who should have access to it?
Who takes care of it? E.g. posting, boosting and writing answers for comments and direct messages?

The ones who step up to do this. If e.g. you would offer to do this, I'd say fine by me :)

@jbruechert
Copy link
Collaborator

Since it looks like there are no requests to do this differently, let's create the Mastodon account + blog I guess.
I'll have a look which instance fits best. If you have any ideas, please leave a comment here.

@1Maxnet1
Copy link
Contributor

If you have any ideas, please leave a comment here

It depends a little on who we try to reach: floss.social would be a great fit to reach FLOSS enthusiasts while urbanists.social would be an instance to reach more players of the public transport community.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Development

No branches or pull requests

4 participants