comaps/website
11
24
Fork
You've already forked website
14

Improve community page #485

Open
opened 2025年11月27日 12:18:22 +01:00 by gedankenstuecke · 1 comment

In #415, we discussed restructuring the Community page, which has a long and growing list of contact/communication channels.

Ultimately we settled on giving the different options according to type, and preferring the FLOSS options in each of the channels, see

@oleg-rswll wrote in #415 (comment):

Microblogging: Mastodon, Bluesky, X, Threads
Chat Messaging: Matrix, SimpleX, Signal, Telegram
Discussion Communities: Lemmy, Reddit
Photos: Pixelfed, Instagram
Social Network: Facebook
Professional Network: LinkedIn
Donations: OpenCollective
Email:

This would require some larger edits to the page than we did so far

In #415, we discussed restructuring the Community page, which has a long and growing list of contact/communication channels. Ultimately we settled on giving the different options according to type, and preferring the FLOSS options in each of the channels, see @oleg-rswll wrote in https://codeberg.org/comaps/website/issues/415#issuecomment-7140523: > **Microblogging**: Mastodon, Bluesky, X, Threads > **Chat Messaging**: Matrix, SimpleX, Signal, Telegram > **Discussion Communities**: Lemmy, Reddit > **Photos**: Pixelfed, Instagram > **Social Network:** Facebook > **Professional Network**: LinkedIn > **Donations**: OpenCollective > **Email**: This would require some larger edits to the page than we did so far

We've been having previous discussions of, let's call it, informal or semiformal support of SM channels. This is for example how the SimpleX group came to exist, one user/contributor proposed to create one and lead it and it was created without much validation or support from a broader community.

We also have some accounts that are acting more as a place holder, e.g. TikTok.

Then we have cases when we've been purposely giving more space to FOSS like SM like in the About page of the app.

IMO, we should therefor discuss a Social Media presence strategy that is coherent with maintenance time cost and project values, etc.

We've been having previous discussions of, let's call it, _informal_ or _semiformal_ support of SM channels. This is for example how the SimpleX group came to exist, one user/contributor proposed to create one and lead it and it was created without much validation or support from a broader community. We also have some accounts that are acting more as a place holder, e.g. TikTok. Then we have cases when we've been purposely giving more space to FOSS like SM like in the About page of the app. IMO, we should therefor discuss a Social Media presence strategy that is coherent with maintenance time cost and project values, etc.
Sign in to join this conversation.
No Branch/Tag specified
main
oleg-rswll-patch-1
ci
oleg-rswll-stats-article
oleg-rswll-f-droid-release-announcement
map-per-add-translations
oleg-rswll-preview-release-announcement
matheusgomesms-patch-1
zyphlar-patch-2
map-per-languages
No results found.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
comaps/website#485
Reference in a new issue
comaps/website
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?