From 9389070b9cdec8f250714df1fec82aae8bd7f67d Mon Sep 17 00:00:00 2001 From: Simon Tournier Date: Sat, 3 Feb 2024 10:25:58 +0100 Subject: doc: contributing: Remove sentences appearing twice. * doc/contributing.texi (Commit Access): Remove sentences appearing twice and use @url. Change-Id: I2b0cb9eebc6f9f66147f286c0bdffdf8924ec412 --- doc/contributing.texi | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) (limited to 'doc') diff --git a/doc/contributing.texi b/doc/contributing.texi index 9a28a58c86..a7d91724fb 100644 --- a/doc/contributing.texi +++ b/doc/contributing.texi @@ -2111,11 +2111,6 @@ 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 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}. 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 @@ -2125,7 +2120,7 @@ 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 -. +@url{https://www.seedsforchange.org.uk/consensus}. The following sections explain how to get commit access, how to be ready to push commits, and the policies and community expectations for commits -- cgit v1.2.3