Forgejo is a very healthy product: the technical side is blossoming and making excellent progress, I'm extremely happy about where it is headed. It deserves a healthy, inclusive and welcoming community.
But in the past few weeks the Forgejo community suffered catastrophic failure. It started with a troll who plagued all spaces during weeks and created increasing tensions between members.
It culminated in the past week as I've been targeted by a number of baseless accusations from more than one community member and it created an environment so hostile for me that I had lost hope and saw no other option but to leave.
That's not what I want. That's not what I deserve. And that would be detrimental to Forgejo because there are not that many active contributors.
But more importantly it is not what an inclusive environment looks like. Active contributors should be rewarded and not punished and pressured to leave. Trolls should be excluded promptly and not allowed to plague every spaces during weeks.
Fortunately there is a simple solution: reboot and rebuild.
Forgejo is only a few months old so... why not? Who says it needs to succeed the first time?
Rebooting a community could be very problematic if Forgejo was an established independent organization. But Forgejo is only a few months old and under the umbrella of Codeberg, which makes it as easy as it can be.
This meta repository can be archived as a remembrance of our past mistakes and a new one could be created. Copying the good bits won't take long and we can start fresh.
Since I no longer feel welcome here, I fully expect this discussion won't be an easy one but I'm prepare to defend my point of view.
In the meantime, because I feel the need for a cosy place to keep working in Forgejo, I would be grateful if a governance repository could be created in the forgejo-contrib organization while this discussion is ongoing. I will start rebuilding there, with whoever is willing to join.
Update: https://codeberg.org/forgejo-contrib/governance was created and the reboot is in progress. Copy pasted with just a few differences compared to when Forgejo was created in October 2022:
- a decision process
- agreements on PR merging and branding
- values on transparency & software freedom
- no interim teams
- abuse@codeberg.org is trusted with moderation.
Discussions have their separate issue tracker https://codeberg.org/forgejo-contrib/discussions
Forgejo is a very healthy product: the technical side is blossoming and making excellent progress, I'm extremely happy about where it is headed. It deserves a healthy, inclusive and welcoming community.
But in the past few weeks the Forgejo community suffered catastrophic failure. It started with a troll who plagued all spaces during weeks and created increasing tensions between members.
It culminated in the past week as I've been targeted by a number of baseless accusations from more than one community member and it created an environment so hostile for me that I had lost hope and saw no other option but to leave.
That's not what I want. That's not what I deserve. And that would be detrimental to Forgejo because there are not that many active contributors.
But more importantly it is not what an inclusive environment looks like. Active contributors should be rewarded and not punished and pressured to leave. Trolls should be excluded promptly and not allowed to plague every spaces during weeks.
**Fortunately there is a simple solution: reboot and rebuild.**
Forgejo is only a few months old so... why not? Who says it needs to succeed the first time?
Rebooting a community could be very problematic if Forgejo was an established independent organization. But Forgejo is only a few months old and under the umbrella of Codeberg, which makes it as easy as it can be.
This `meta` repository can be archived as a remembrance of our past mistakes and a new one could be created. Copying the good bits won't take long and we can start fresh.
Since I no longer feel welcome here, I fully expect this discussion won't be an easy one but I'm prepare to defend my point of view.
In the meantime, because I feel the need for a cosy place to keep working in Forgejo, I would be grateful if a `governance` repository could be created in the forgejo-contrib organization while this discussion is ongoing. I will start rebuilding there, with whoever is willing to join.
Update: https://codeberg.org/forgejo-contrib/governance was created and the reboot is in progress. Copy pasted with just a few differences compared to when Forgejo was created in October 2022:
* a decision process
* agreements on PR merging and branding
* values on transparency & software freedom
* no interim teams
* abuse@codeberg.org is trusted with moderation.
Discussions have their separate issue tracker https://codeberg.org/forgejo-contrib/discussions