[Project] Public Relations #27

fnetX commented 2023年08月24日 21:29:01 +02:00

About the project

There is currently no team managing public relations for Codeberg. We could do much better here!

State

Planned - Looking for maintainers

List the people who joined the team.

• @fnetX
• various people in the respective Matrix chatroom

Tasks

• Prepare, schedule and post content to our social media accounts (Mastodon, eventually also Twitter to catch people in the proprietary ecosystem)
• Reply to requests on socialmedia, boost content etc
• Prepare the newsletter to Codeberg e.V. members and collect updates from all relevant teams
• add other content to the blog (e.g. project presentations)
• optional: add announcements to Codeberg members (but they are currently broken)
• optional: Organize events like hackerspaces, the contributor meetups and more

Which references are already available for the project?

• Community Spotlight thread: Codeberg/Community#200
• Matrix room: https://matrix.to/#/%23codeverg-pr%3Amatrix.tu-berlin.de (can also be found via the Codeberg Space)

Looking for ...

• Teamleads / Maintainers (taking responsibility)
• Co-Maintainers (sharing responsibility)
• Software developers
• System administrators
• Writers
• Designers
• Public Relation / Communication experts
• Input and suggestions
• Testing and Feedback

Details

We had an announcement widget added to Forgejo, but it was conflicting with changes in August 2023. Please connect with the Forgejo team on how to bring back announcement featuers (maybe reusable to let instance admins communicate to their users?)

Issue thread meta

• ... discuss the project idea and give general input
• ... discuss technical details about the project
• ... commit yourself to be part of the project (becoming a maintainer etc)
• ... suggest approaches to the project (e.g. creating a repository, chat etc)

### About the project There is currently no team managing public relations for Codeberg. We could do much better here! ### State Planned - Looking for maintainers ### List the people who joined the team. - @fnetX - various people in the respective Matrix chatroom ### Tasks - [ ] Prepare, schedule and post content to our social media accounts (Mastodon, eventually also Twitter to catch people in the proprietary ecosystem) - [ ] Reply to requests on socialmedia, boost content etc - [ ] Prepare the newsletter to Codeberg e.V. members and collect updates from all relevant teams - [ ] add other content to the blog (e.g. project presentations) - [ ] optional: add announcements to Codeberg members (but they are currently broken) - [ ] optional: Organize events like hackerspaces, the contributor meetups and more ### Which references are already available for the project? - Community Spotlight thread: https://codeberg.org/Codeberg/Community/issues/200 - Matrix room: https://matrix.to/#/%23codeverg-pr%3Amatrix.tu-berlin.de (can also be found via the Codeberg Space) ### Looking for ... - [x] Teamleads / Maintainers (taking responsibility) - [ ] Co-Maintainers (sharing responsibility) - [ ] Software developers - [ ] System administrators - [x] Writers - [x] Designers - [x] Public Relation / Communication experts - [ ] Input and suggestions - [ ] Testing and Feedback ### Details We had an announcement widget added to Forgejo, but it was conflicting with changes in August 2023. Please connect with the Forgejo team on how to bring back announcement featuers (maybe reusable to let instance admins communicate to their users?) ### Issue thread meta - [x] ... discuss the project idea and give general input - [ ] ... discuss technical details about the project - [x] ... commit yourself to be part of the project (becoming a maintainer etc) - [x] ... suggest approaches to the project (e.g. creating a repository, chat etc)

n0toose commented 2023年09月18日 09:35:38 +02:00

I'm interested in picking this up with one or two other people for the sake of forming a team for something - I may not always be available (I am also extremely pressed on time right now) but I can try my best, as my hopes are to build the initial structure and have other people participate as well.

I'd like for such a team to operate as simply as possible, so that it's optimal / saving time if other members are available but as "bad" as it is right now if none are available. (as in, do not enforce e.g. voting to make a post).

Workflow suggestions:

• Creating a publicly accessible Matrix chat for relevant discussions so as to alleviate concerns of the communications described as "honest" being sugarcoated.
• If there is some degree of uncertainty as to how something is communicated to the public, pass it on to the other participants just to be sure while keeping things relatively uncomplicated. Prefer this approach for PSAs and sensitive announcements, use @room to attract the attention of other members. Don't filter everything.
• Use social media channels to promote projects on Codeberg once or twice a week.
• Reconsider the approach if it is thought that it takes much more time to perform team-related or other Codeberg/IRL tasks.
• Investigate whether access to the account can be given without handing over a password.
• Make it read only? Read only would act as a safeguard against being "derailed" when trying to be productive, but prohibiting external participation would be counter-productive towards onboarding and "building trust".

Questions:

• Should an account manager respond to posts under hashtags like #codeberg using the official account, or using their personal account?
• Should posts be signed off? When?

As I'm imagining it, this task should take much less time for a participant than other Codeberg-related tasks, such as e.g. Forgejo patches or triaging tickets. It would be great if we tried onboarding members for this without too much pressure on active participation, in the same sense as we planned for https://codeberg.org/Codeberg-e.V./requests

Related internal discussion: Codeberg-e.V./Discussion#106

I'm interested in picking this up with one or two other people for the sake of forming a team for something - I may not always be available (I am also extremely pressed on time right now) but I can try my best, as my hopes are to build the initial structure and have other people participate as well. I'd like for such a team to operate as simply as possible, so that it's optimal / saving time if other members are available but as "bad" as it is right now if none are available. (as in, do not enforce e.g. voting to make a post). Workflow suggestions: - Creating a publicly accessible Matrix chat for relevant discussions so as to alleviate concerns of the communications described as "honest" being sugarcoated. - If there is some degree of uncertainty as to how something is communicated to the public, pass it on to the other participants just to be sure while keeping things relatively uncomplicated. Prefer this approach for PSAs and sensitive announcements, use `@room` to attract the attention of other members. Don't filter everything. - Use social media channels to promote projects on Codeberg once or twice a week. - Reconsider the approach if it is thought that it takes much more time to perform team-related or other Codeberg/IRL tasks. - Investigate whether access to the account can be given without handing over a password. - Make it read only? Read only would act as a safeguard against being "derailed" when trying to be productive, but prohibiting external participation would be counter-productive towards onboarding and "building trust". Questions: - Should an account manager respond to posts under hashtags like `#codeberg` using the official account, or using their personal account? - Should posts be signed off? When? As I'm imagining it, this task should take much less time for a participant than other Codeberg-related tasks, such as e.g. Forgejo patches or triaging tickets. It would be great if we tried onboarding members for this without too much pressure on active participation, in the same sense as we planned for https://codeberg.org/Codeberg-e.V./requests Related internal discussion: https://codeberg.org/Codeberg-e.V./Discussion/issues/106

ccoenen commented 2023年09月18日 10:29:37 +02:00

Regarding the technical part: there's a project called toot-together, which uses a merge-request style of contribution to collaborate on a single mastodon account.

Here's an example of HedgeDoc using it for their Fediverse account, I'm pretty sure this could be adapted to Forgejo+Woodpecker.

Regarding the technical part: there's a project called [toot-together](https://github.com/joschi/toot-together/), which uses a merge-request style of contribution to collaborate on a single mastodon account. Here's an example of [HedgeDoc using it](https://github.com/hedgedoc/social-media) for [their Fediverse account](https://fosstodon.org/@hedgedoc), I'm pretty sure this could be adapted to Forgejo+Woodpecker.

n0toose commented 2023年09月18日 10:51:24 +02:00

Here's an example of HedgeDoc using it for their Fediverse account, I'm pretty sure this could be adapted to Forgejo+Woodpecker.

I'm interested in this, but I have a question: Don't you think that a PR model in general could be "too much bureaucracy"? I think that transforming a GitHub Action to Woodpecker is a major feat - this isn't just an Ansible-like script that clones / compiles / checks linting... I will have to ask someone else though.

> Here's an example of HedgeDoc using it for their Fediverse account, I'm pretty sure this could be adapted to Forgejo+Woodpecker. I'm interested in this, but I have a question: Don't you think that a PR model in general could be "too much bureaucracy"? I think that transforming a GitHub Action to Woodpecker is a major feat - this isn't just an Ansible-like script that clones / compiles / checks linting... I will have to ask someone else though.

ccoenen commented 2023年09月18日 11:24:34 +02:00

That entirely depends on how this is implemented within the team. My point is: with that project, there can be a group who has write access to that particular account, without knowing any of the credentials. Everyone who can push to main on that repo can publish a post.

If you layer 4 eyes principle (or whatever else) on top of that is completely up to codeberg. As mentioned over in the other discussion, I am not a fan of making this too complicated, but then again, it's not up to me to decide. I'm just saying, this is one way that this could be achieved.

That entirely depends on how this is implemented within the team. My point is: with that project, there can be a group who has write access to that particular account, without knowing any of the credentials. Everyone who can push to `main` on that repo can publish a post. If you layer 4 eyes principle (or whatever else) on top of that is completely up to codeberg. As mentioned over in the other discussion, I am not a fan of making this too complicated, but then again, it's not up to me to decide. I'm just saying, this is one way that this could be achieved.

fnetX commented 2023年09月18日 21:51:42 +02:00

I'm not sure how it works with replies, but maybe: Everyone can publish signed posts and replies, and posts without signing require at least a second approval?

Anyway, I think you should go ahead to form all you need for the team (channel, repos, whatever you need just name it here) and discuss the details with the other members. I'd think that the presidium approves your final proposal on how socialmedia will be handled going forward.

Thank you for the initiative!

I'm not sure how it works with replies, but maybe: Everyone can publish signed posts and replies, and posts without signing require at least a second approval? Anyway, I think you should go ahead to form all you need for the team (channel, repos, whatever you need just name it here) and discuss the details with the other members. I'd think that the presidium approves your final proposal on how socialmedia will be handled going forward. Thank you for the initiative!

n0toose commented 2023年09月20日 11:25:44 +02:00

I just found out about https://mastofeed.org/, which mirrors posts from an RSS feed to Mastodon automatically. Microblogging is not the same as blogging (in the other accounts I manage, when I share a link to a blog post, I tend to write a custom message meant for the audience on that platform with a brief summary) and blogging takes relatively more effort, but the PR workflow that we are looking for would already be 80% done, and the smaller announcements that "would not have to be posted without approval" could still be done anyways.

This would not resolve the reply problem among other things, but it would take advantage of already existing infrastructure without undertaking massive Forgejo refactoring efforts – it's much better when the effort for an imperfect approach is much lower.

I just found out about https://mastofeed.org/, which mirrors posts from an RSS feed to Mastodon automatically. Microblogging is not the same as blogging (in the other accounts I manage, when I share a link to a blog post, I tend to write a *custom* message meant for the audience on that platform with a brief summary) and blogging takes relatively more effort, but the PR workflow that we are looking for would already be 80% done, and the smaller announcements that "would not have to be posted without approval" could still be done anyways. This would not resolve the reply problem among other things, but it would take advantage of already existing infrastructure without undertaking massive Forgejo refactoring efforts – it's much better when the effort for an imperfect approach is much lower.

fnetX commented 2023年09月20日 22:06:01 +02:00

Maybe we can also have one or two people with the permission to reply and the part of writing content is open to "everyone".

Maybe we can also have one or two people with the permission to reply and the part of writing content is open to "everyone".

n0toose commented 2023年10月04日 08:20:09 +02:00

I found out about tootgroup.py through the Metalab, which is a hackerspace in Vienna.

When a message is supposed to be reposted by the account, you have to use an exclamation mark before the account itself, but other than that, I think that the use case essentially closely emulates what we're doing with the account right now. Maybe we could just respond to people from our personal accounts?

I found out about [tootgroup.py](https://github.com/oe4dns/tootgroup.py) through the [Metalab](https://chaos.social/@metalab), which is a hackerspace in Vienna. When a message is supposed to be reposted by the account, you have to use an exclamation mark before the account itself, but other than that, I think that the use case essentially closely emulates what we're doing with the account right now. Maybe we could just respond to people from our personal accounts?

fnetX commented 2024年01月29日 21:31:54 +01:00

There is a chatroom for the Forgejo project and it works great IMHO. I propose to do the same to move on here: Create a Matrix room, which I don't currently mind being public, and then discuss the work there.

I recommend that the group can decide on it's own about posts to the blog and socialmedia, but members of Presidium/Board or potentially future team leads need to approve before publication.

Drafting toots and small posts can be done in the chat, and contributions to the blog can probably be reviewed as PRs.

There is a chatroom for the Forgejo project and it works great IMHO. I propose to do the same to move on here: Create a Matrix room, which I don't currently mind being public, and then discuss the work there. I recommend that the group can decide on it's own about posts to the blog and socialmedia, but members of Presidium/Board or potentially future team leads need to approve before publication. Drafting toots and small posts can be done in the chat, and contributions to the blog can probably be reviewed as PRs.

fnetX commented 2024年05月22日 23:25:21 +02:00

There is now a Matrix room: https://matrix.to/#/%23codeverg-pr%3Amatrix.tu-berlin.de

There is now a Matrix room: https://matrix.to/#/%23codeverg-pr%3Amatrix.tu-berlin.de

n0toose commented 2025年11月23日 11:52:38 +01:00

FYI: We have a few people that share this responsibility now, but could always use more (especially because many are also involved in other projects)—the Matrix room has been currently private since February due to concerns involving potential raids during crises.

We'll document points of contact in the coming weeks in the repo.

FYI: We have a few people that share this responsibility now, but could always use more (especially because many are also involved in other projects)—the Matrix room has been currently private since February due to concerns involving potential raids during crises. We'll document points of contact in the coming weeks in the repo.

ShiningVenus commented 2025年11月26日 03:56:18 +01:00

@n0toose wrote in #27 (comment):

FYI: We have a few people that share this responsibility now, but could always use more (especially because many are also involved in other projects)—the Matrix room has been currently private since February due to concerns involving potential raids during crises.

We'll document points of contact in the coming weeks in the repo.

I am interested in joining in on this and am in the Matrix chat as Shining Venus. I posted my intro. :)

@n0toose wrote in https://codeberg.org/Codeberg/Contributing/issues/27#issuecomment-8415537: > FYI: We have a few people that share this responsibility now, but could always use more (especially because many are also involved in other projects)—the Matrix room has been currently private since February due to concerns involving potential raids during crises. > > We'll document points of contact in the coming weeks in the repo. I am interested in joining in on this and am in the Matrix chat as Shining Venus. I posted my intro. :)