Hi, I don't think it's sufficient, take this:
"It implies that no decision is made against significant concerns" OK, so what does "implies" mean in this context? What is a "significant concern"? When is a concern not "significant"? How many people involved must have such a concern? If one person has a concern does it block the outcome? Who is having such a concern, is it a committer, a team member, a user? The manul provides an introduction to the principle, it doesn't deal with the specifics in the specific context. For example, in the context of Andreas' package removal RFC what does this mean: "A contributor (who may or may not have commit access) wishing to block a proposal ...." OK, so if a user wishes that a package should stay in Guix do they have the right to block removal? They can't realistically "contribute" to creating a solution, but this sentences "implies" they can do so. That might seem 'obviously' silly, but if something is not explicit it's implicit and open to argument. The reason I'm pointing at this is that _when_ there is conflict, there should be clear rules so everyone knows how to deal with them. - Who is involved - What is the process - How is deadlock resolved This is exactly what you did for the GCD process. I'm asking for the same thing here, that the process is defined. Steve / Futurile On Tue, Mar 24, 2026 at 03:56:24PM +0100, Simon Tournier wrote: > Hi, > > > Consensus is not defined within the manual > > Consensus appears to me defined here: > > 22.13 Making Decisions > ====================== > > It is expected from all contributors, and even more so from > committers, > to help build consensus and make decisions based on consensus. By > using > consensus, we are committed to finding solutions that everyone can > live > with. It implies that no decision is made against significant > concerns > and these concerns are actively resolved with proposals that work for > everyone. > > A contributor (who may or may not have commit access) wishing to > block a proposal bears a special responsibility for finding > alternatives, proposing ideas/code or explain the rationale for the > status quo to resolve the deadlock. To learn what consensus decision > making means and understand its finer details, you are encouraged to > read <https://www.seedsforchange.org.uk/consensus>. > > > [0] https://guix.gnu.org/manual/1.5.0/en/html_node/Making-Decisions.html > > Cheers, > simon
