doc: Mention the responsibilities that blocking comes with.

doc: Mention the responsibilities that blocking comes with.

[Maxim Cournoyer]

Hello,

I thought I'd advertise this proposed change here:
<https://issues.guix.gnu.org/66430> that touches to our common rules, so
that everyone gets to see it/comment on it.

-- 
Thanks,
Maxim

Re: doc: Mention the responsibilities that blocking comes with.

[Simon Tournier]

Hi,

On sam., 14 oct. 2023 at 11:44, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:

> I thought I'd advertise this proposed change here:
> <https://issues.guix.gnu.org/66430> that touches to our common rules, so
> that everyone gets to see it/comment on it.

Here is the change:

--8<---------------cut here---------------start------------->8---
+@url{https://www.seedsforchange.org.uk/consensus}.  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 (which 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>.
--8<---------------cut here---------------end--------------->8---

No more comment?  Ready for pushing it?

Cheers,
simon

Re: doc: Mention the responsibilities that blocking comes with.

[Ricardo Wurmus]

Simon Tournier <zimon.toutoune@gmail.com> writes:

> +concerns are actively resolved with proposals that work for everyone.  A
> +contributor (which may or may not have commit access) wishing to

Should be “who” instead of “which”.

> +understand its finer details, you are encouraged to read
> +<https://www.seedsforchange.org.uk/consensus>.

Isn’t this URL also supposed to be wrapped in @url?

-- 
Ricardo