On Sat, Mar 30, 2019 at 4:16 PM waddlesplash <waddlesplash@xxxxxxxxx> wrote:
It's not just that I'm forced to go through gerrit, so don't believe theobfuscation done here. Among the other abuses:
documentation
* I can't write articles in my personal blog anymore and help with
* I can't help with reviews in gerrit
* I can't manage anymore my tickets
The permission to do all of these items is part of "direct commit
access". The second one at least it should be immediately obvious;
only those with commit access can +2 or -2 a change. Further, you are
not stopped from making blogposts or changes to the website; GSoC
students maintain a blog via pull requests to the "website" repo, and
there is nothing stopping you from doing the same here.
* I have been removed from haikuports, this has nothing to do with Haikucommit access and has been gained completely independently, this is
all-in-all a true abuse of power.
HaikuPorts is much more loosely organized than Haiku is, but generally
it's regarded that if someone who already has commit access to Haiku
submits a few patches to HaikuPorts, we grant them commit access
there; otherwise they can gain commit access the "normal way" by
submitting a large number of good recipes. But if one runs into enough
problems that the Haiku developers are willing to vote them out of
commit access, HaikuPorts generally follows on that. This system has
worked so far, and we have not yet needed to formally codify it.