This is going to be a bit rude, but this is why I'm a fan of the BDFL approach of software development - it's better to have a single known dictator than a thousand tiny tyrants.
I don't think who is right matters, or at least I don't care. If someone wanted the project to go a different direction, they can fork it. Now it sounds like we are all out of a good piece of software.
In general the community owes you nothing. Maintaining is a thankless task. If you build your community as a flat hierarchy, it should be flat - you don't get to become dictator for life or have some club over your fellows when disagreements flare up.
I don't see an actual technical issue on Pleroma that is the issue here that would justify the effort of forking, the only complaint was some old merge requests that Alex expedited merging.
This blog post is mostly about a personality and communication style conflict, not a technical one.
The Soapbox change was perfectly fine to do, and long overdue for hellthreads. Waiting 12+ months for some consensus that would never arrive wasn't going to make things go any better.
4 comments
[ 2.8 ms ] story [ 17.9 ms ] threadI don't think who is right matters, or at least I don't care. If someone wanted the project to go a different direction, they can fork it. Now it sounds like we are all out of a good piece of software.
In general the community owes you nothing. Maintaining is a thankless task. If you build your community as a flat hierarchy, it should be flat - you don't get to become dictator for life or have some club over your fellows when disagreements flare up.
This blog post is mostly about a personality and communication style conflict, not a technical one.
The Soapbox change was perfectly fine to do, and long overdue for hellthreads. Waiting 12+ months for some consensus that would never arrive wasn't going to make things go any better.
They could just fork it and start a version not including Alex if they don't like him so much.