forgejo/discussions
49
43

The cost of being inclusive and transparent #112

Open
opened 2024年02月03日 16:21:45 +01:00 by earl-warren · 3 comments

The governance agreement on having Forgejo be a hard fork of Gitea is controversial and there is no right or wrong: in the end it will be a leap of faith, a judgement call. It was clear from the start that:

  • unrelated discussions would (deliberately or not) derail the conversation
  • off-topic negative comments would be posted
  • it would be a target for people banned for harassment in Forgejo

As a member of the Forgejo moderation team, that was a concern and I made a mental note to:

  • actively create and participate in discussions that, although off topic, deserved to be be continued
  • gently remind people posting negative off-topic comments to do that elsewhere
  • enforce the harassment ban

About two weeks after the agreement was first posted, all of this has happened and I spent:

  • 98% of the time creating and participating in unrelated discussions (e.g. Gitea is Open Core)
  • 1% of the time reminding people to stay on topic (e.g. "Sad to see, that reasonable comments get deleted")
  • 1% of the time enforcing the ban

It is work but I'm happy to keep doing that because it means Forgejo is an inclusive environment where everything is transparent. None of that work would be necessary if this agreement was discussed behind closed doors. People banned for harassment would be blocked at the door. People who have no stake in Forgejo would not enter either and would not have the opportunity to derail the conversation.

The cost of being inclusive and transparent is dealing with the noise and unwanted attention. Quite cheap, I think.

This is my personal view of the situation and I would be interested to know if anyone has a different experience.

The governance agreement [on having Forgejo be a hard fork of Gitea](https://codeberg.org/forgejo/governance/issues/58) is controversial and there is no right or wrong: in the end it will be a leap of faith, a judgement call. It was clear from the start that: * unrelated discussions would (deliberately or not) derail the conversation * off-topic negative comments would be posted * it would be a target for people banned for harassment in Forgejo As a member of the Forgejo moderation team, that was a concern and I made a mental note to: * actively create and participate in discussions that, although off topic, deserved to be be continued * gently remind people posting negative off-topic comments to do that elsewhere * enforce the harassment ban About two weeks after the agreement was first posted, all of this has happened and I spent: * 98% of the time creating and participating in unrelated discussions (e.g. [Gitea is Open Core](https://codeberg.org/forgejo/discussions/issues/102)) * 1% of the time reminding people to stay on topic (e.g. "Sad to see, that reasonable comments get deleted") * 1% of the time enforcing the ban It is work but I'm happy to keep doing that because it means Forgejo is an inclusive environment where everything is transparent. None of that work would be necessary if this agreement was discussed behind closed doors. People banned for harassment would be blocked at the door. People who have no stake in Forgejo would not enter either and would not have the opportunity to derail the conversation. The cost of being inclusive and transparent is dealing with the noise and unwanted attention. Quite cheap, I think. This is my personal view of the situation and I would be interested to know if anyone has a different experience.

A message was redacted by the Codeberg moderation team for circumventing a ban established by a project.

We want to remind everyone that nice behaviour in project is key to collaboration. Thank you for your understanding.

Please contact the Forgejo moderation team, they have received a copy of the removed messages.

A message was redacted by the Codeberg moderation team for circumventing a ban established by a project. We want to remind everyone that nice behaviour in project is key to collaboration. Thank you for your understanding. Please contact the Forgejo moderation team, they have received a copy of the removed messages.

As someone who only recently started contributing to Forgejo, I can't emphasise enough how much transparency and inclusivity contribute to the accessibility of the project to all of its stakeholders. I believe this approach falls in line with the purpose and objectives of Forgejo, as it allows the project to stay connected with its community, leading to decisions being taken that address many more concerns than a rather exclusive and less transparent governance policy would take. It comes with the kind of trade-offs that shape up a mature, self-sustaining community around the project.

As someone who only recently started contributing to Forgejo, I can't emphasise enough how much transparency and inclusivity contribute to the accessibility of the project to *all* of its stakeholders. I believe this approach falls in line with the purpose and objectives of Forgejo, as it allows the project to stay connected with its community, leading to decisions being taken that address many more concerns than a rather exclusive and less transparent governance policy would take. It comes with the kind of trade-offs that shape up a mature, self-sustaining community around the project.

A message from an account created to circumvent a ban from Forgejo spaces was deleted, send a mail to moderation@forgejo.org for more information.

A message from an account created to circumvent a ban from Forgejo spaces was deleted, send a mail to moderation@forgejo.org for more information.
Sign in to join this conversation.
No Branch/Tag specified
No results found.
No results found.
Labels
Clear labels
User research - Accessibility
Requires input about accessibility features, likely involves user testing.
User research - Blocked
Do not pick as-is! We are happy if you can help, but please coordinate with ongoing redesign in this area.
User research - Community
Community features, such as discovering other people's work or otherwise feeling welcome on a Forgejo instance.
User research - Config (instance)
Instance-wide configuration, authentication and other admin-only needs.
User research - Errors
How to deal with errors in the application and write helpful error messages.
User research - Filters
How filter and search is being worked with.
User research - Future backlog
The issue might be inspiring for future design work.
User research - Git workflow
AGit, fork-based and new Git workflow, PR creation etc
User research - Labels
Active research about Labels
User research - Moderation
Moderation Featuers for Admins are undergoing active User Research
User research - Needs input
Use this label to let the User Research team know their input is requested.
User research - Notifications/Dashboard
Research on how users should know what to do next.
User research - Rendering
Text rendering, markup languages etc
User research - Repo creation
Active research about the New Repo dialog.
User research - Repo units
The repo sections, disabling them and the "Add more" button.
User research - Security
User research - Settings (in-app)
How to structure in-app settings in the future?
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
4 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
forgejo/discussions#112
Reference in a new issue
forgejo/discussions
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?