You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@couchdb.apache.org by ro...@apache.org on 2023/01/25 10:46:34 UTC
[couchdb-www] branch asf-site updated: Correct RFC template link (#58)
This is an automated email from the ASF dual-hosted git repository.
ronny pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/couchdb-www.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 65b760e Correct RFC template link (#58)
65b760e is described below
commit 65b760e742caa1d499b773df0049d88fc65c2f89
Author: Mike Rhodes <mi...@gmail.com>
AuthorDate: Wed Jan 25 10:46:29 2023 +0000
Correct RFC template link (#58)
After moving the couchdb documentation site into the main couchdb repo,
the RFC link in the bylaws was out of date.
Paragraph tags are also added to the RFC intro paragraph to ensure the
text wraps the same way as other paragraphs in the document.
---
bylaws.html | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/bylaws.html b/bylaws.html
index 7f0545f..8f1947b 100644
--- a/bylaws.html
+++ b/bylaws.html
@@ -309,13 +309,13 @@
<h3 id="rfc">3.6 Request For Comment (RFC) process</h3>
-For major changes to the fuctionality of CouchDB, a Request For Comment (RFC) process has been established. The intent of an RFC is to ensure sufficient public discussion has occurred on the design of new features, that the proposal is adequately captured in a summary document, and that there is community acceptance of the proposal. The completed RFC template for the proposal then becomes the basis for the new functionality's documentation.
+<p>For major changes to the functionality of CouchDB, a Request For Comment (RFC) process has been established. The intent of an RFC is to ensure sufficient public discussion has occurred on the design of new features, that the proposal is adequately captured in a summary document, and that there is community acceptance of the proposal. The completed RFC template for the proposal then becomes the basis for the new functionality's documentation.</p>
-The process is:
+<p>The process is:</p>
<ul>
<li>Start a [DISCUSS] thread on <a href="https://lists.apache.org/list.html?dev@couchdb.apache.org">the developer mailing list</a>. Discuss your proposal in detail, including which modules/applications are affected, any HTTP API additions and deprecations, and security issues.</li>
- <li>When there is consensus on the approach from the community, <a href="https://github.com/apache/couchdb-documentation/blob/main/rfcs/template.md">complete the RFC template</a> and work through any final revisions to the document, with the support of the developer mailing list.</li>
+ <li>When there is consensus on the approach from the community, <a href="https://github.com/apache/couchdb/blob/main/src/docs/rfcs/template.md">complete the RFC template</a> and work through any final revisions to the document, with the support of the developer mailing list.</li>
<li>Start the RFC <strong>vote</strong> on the developer mailing list. Hold the vote according to the <em>lazy majority process</em>: at least 3 +1 votes, and more binding +1 than binding -1 votes.</li>
</ul>