doc: Add a reference to a page explaining consensus decision making.
This is to make explicit something which until now had always been implicit. * doc/contributing.texi (Commit Access): Mention that committers are expected to employ consensus decision making. Co-authored-by: Ludovic Courtès <ludo@gnu.org>master
parent
f3424ada31
commit
52d373dfef
|
@ -1727,7 +1727,12 @@ project for at least 6 months. This ensures enough interactions with
|
||||||
the contributor, which is essential for mentoring and assessing whether
|
the contributor, which is essential for mentoring and assessing whether
|
||||||
they are ready to become a committer. Commit access should not be
|
they are ready to become a committer. Commit access should not be
|
||||||
thought of as a ``badge of honor'' but rather as a responsibility a
|
thought of as a ``badge of honor'' but rather as a responsibility a
|
||||||
contributor is willing to take to help the project.
|
contributor is willing to take to help the project. It is expected from
|
||||||
|
all contributors, and even more so from committers, to help build
|
||||||
|
consensus and make decisions based on consensus. To learn what
|
||||||
|
consensus decision making means and understand its finer details, you
|
||||||
|
are encouraged to read
|
||||||
|
@url{https://www.seedsforchange.org.uk/consensus}.
|
||||||
|
|
||||||
The following sections explain how to get commit access, how to be ready
|
The following sections explain how to get commit access, how to be ready
|
||||||
to push commits, and the policies and community expectations for commits
|
to push commits, and the policies and community expectations for commits
|
||||||
|
|
Reference in New Issue