Update documentation on Consensus Building and Lazy Consensus after P…

…R 6297

The proposal in PR opencast#6297 suggested moving email-based proposals and making them PRs instead. Since this proposal was accepted, we must update the corresponding documentation accordingly.

Signed-off-by: Daniel Ziegenberg <daniel@ziegenberg.at>

docs/guides/developer/docs/participate/decision-making/consensus-building.md

@@ -11,15 +11,8 @@ successful project. However, there is a shorthand notation for showing support,
 Sending out a Proposal
 ----------------------
 
-Proposals should be send to list. It is common to indicate proposals by including the
-string `[#proposal]` at the beginning of the subject to make it easier for the community to identify that the mail
-contains an important proposal.
-
-The list used should usually be the development list. In very rare cases, other lists may also be used: The users list
-when the matter discussed only targets adopters/uses. The committers list if the matter discussed needs to be kept
-private e.g. for personal or security reasons.
-
-Please avoid cross-posting a proposal on multiple lists. It will usually fracture the discussion.
+Proposals shall be filed as a pull request. It is common to indicate proposals by adding the
+label `proposal` to make it easier for the community to identify that the PR contains an important proposal.
 
 Expressing Approval or Disapproval
 ----------------------------------

docs/guides/developer/docs/participate/decision-making/lazy-consensus.md

@@ -29,9 +29,8 @@ Sometimes a member of the community will believe a specific action is the correc
 that there will be consensus and may not wish to proceed the work without giving the community an opportunity to
 feedback. In these circumstances, they can make the proposal and state Lazy Consensus is in operation.
 
-Proposals should be sent to list, preferably the development list. It is common to indicate proposals by including the
-string `[#proposal]` at the beginning of the subject to make it easier for the community to identify that the mail
-contains an important proposal.
+Proposals shall be filed as a pull request. It is common to indicate proposals by adding the
+label `proposal` to make it easier for the community to identify that the PR contains an important proposal.
 
 This triggers the Lazy Consensus mechanism, by which the proposal is considered accepted if no one objects within 72
 hours after the proposal submission. The period of 72 hours is chosen because it accounts for different timezones and
@@ -45,6 +44,6 @@ work begins.
 Silence is Consent
 ------------------
 
-People may choose to indicate their support for the actions taken with a +1 mail - quick and easy to read and reassuring
+People may choose to indicate their support for the actions taken with a +1 comment - quick and easy to read and reassuring
 for the implementer. However, remember, in a lazy consensus world silence is the equivalent to support. This can take
 some time to get used to.