Hi Pjotr, I haven't really followed the issue, so I couldn't say whether the decision taken by the core maintainers was right or not. However, I find that your message is insightful in that it raises a few questions on _how_ this decision was taken. > I am not a core maintainer, but it should be obvious that core > maintainers would not take a decision to revoke commit rights lightly. I trust that it is the case, but being the devil's advocate, I could argue that from reading this thread does not make it obvious. Maybe the decision process should be made more transparent? Reading between the lines, I feel that some discussion happened behind closed curtains between some maintainers. Correct me if I'm wrong. I don't know if this is ideal in such circumstances, but if it is, then it is probably a good idea to mention it. Another question one could ask: why just the core maintainers actually? Shouldn't everyone be involved? Maybe the right answer is "no" here, and if so, I believe we should explain why in the community guidelines. Lest the community present an image where a few would benefit from arbitrary privileges. It'd be nice to explicit these and the reason behind the various roles found among the members of the community. Last, maybe a more important question: if core maintainers are entrusted to take executive decisions about the community members, what about executive decisions about the core maintainers themselves? Are there such provisions? Example: what if a core maintainers misbehaves? Can they see there privileges revoked? How? Is this documented? > Marius representing the core maintainers clearly wrote: This is the > next in a series of incidents. Considering this is the main cause for the decision, I believe it's important to detail it with references. "a series of incidents" is too vague and in isolation, it does not seem to justify the decision very well. It seems necessary to me to recap the whole series of points that led to the decision. So maybe there are some issues we could address with regard to the structural organization of the Guix community, which could help making it increasingly more welcoming, peaceful and strong. Food for thoughts! :) -- Pierre Neidhardt https://ambrevar.xyz/