[couchdb-www] branch update-rfc-template-link-in-bylaws created (now adc833f)

[be...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

bessbd pushed a change to branch update-rfc-template-link-in-bylaws
in repository https://gitbox.apache.org/repos/asf/couchdb-www.git.


      at adc833f  Update RFC template link

This branch includes the following new commits:

     new adc833f  Update RFC template link

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.

[couchdb-www] 01/01: Update RFC template link

[be...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

bessbd pushed a commit to branch update-rfc-template-link-in-bylaws
in repository https://gitbox.apache.org/repos/asf/couchdb-www.git

commit adc833f9ade6fba0b93bc58e274f0bd75638eb92
Author: Bessenyei Balázs Donát <be...@users.noreply.github.com>
AuthorDate: Thu Feb 4 11:02:05 2021 +0100

    Update RFC template link
---
 bylaws.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/bylaws.html b/bylaws.html
index 4aea136..7f0545f 100644
--- a/bylaws.html
+++ b/bylaws.html
@@ -315,7 +315,7 @@ The process is:
 
   <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://s.apache.org/CouchDB-RFC">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-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>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>