You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@couchdb.apache.org by wo...@apache.org on 2019/03/05 17:45:23 UTC
[couchdb-www] 01/01: Use Pony Mail links instead of old mail archive
This is an automated email from the ASF dual-hosted git repository.
wohali pushed a commit to branch add-rfc
in repository https://gitbox.apache.org/repos/asf/couchdb-www.git
commit d2b31e8b6f78e06d44f12aaa98938163b5997200
Author: Joan Touzet <jo...@atypical.net>
AuthorDate: Tue Mar 5 12:35:17 2019 -0500
Use Pony Mail links instead of old mail archive
---
bylaws.html | 22 +++++++++++-----------
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/bylaws.html b/bylaws.html
index b7444ab..4aea136 100644
--- a/bylaws.html
+++ b/bylaws.html
@@ -36,7 +36,7 @@
<p>We value the community more than the code. A strong and healthy community should be a fun and rewarding place for everyone involved. Code, and everything else that goes with that code, will be produced by a healthy community over time.
-<p>The direction of the project and the decisions we make are up to you. If you are participating on <a href="https://mail-archives.apache.org/mod_mbox/#couchdb">the mailing lists</a> you have the right to make decisions. All decisions about the project are taken on the mailing lists. There are no lead developers, nor is there any one person in charge.
+<p>The direction of the project and the decisions we make are up to you. If you are participating on <a href="https://couchdb.apache.org/#mailing-lists">the mailing lists</a> you have the right to make decisions. All decisions about the project are taken on the mailing lists. There are no lead developers, nor is there any one person in charge.
<p>Anyone can subscribe to the public mailing lists, and in fact, you are encouraged to do so. The development mailing list is not just for developers, for instance. It is for anyone who is interested in the development of the project. Everybody's voice is welcome.
@@ -60,7 +60,7 @@
<p><strong>The most important participants in the project are people who use our software.</strong>
-<p>Users can participate by talking about the project, providing feedback, and helping others. This can be done at the ASF or elsewhere, and includes being active on <a href="https://mail-archives.apache.org/mod_mbox/couchdb-user/">the user mailing list</a>, third-party support forums, blogs, and social media. Users who participate in this way automatically become contributors.
+<p>Users can participate by talking about the project, providing feedback, and helping others. This can be done at the ASF or elsewhere, and includes being active on <a href="https://lists.apache.org/list.html?user@couchdb.apache.org">the user mailing list</a>, third-party support forums, blogs, and social media. Users who participate in this way automatically become contributors.
<h3 id="contributors">2.2. Contributors</h3>
@@ -153,9 +153,9 @@
<p>Our goal is to build a community of trust, reduce mailing list traffic, and deal with disagreements swiftly when they occur.
-<p>All decision making must happen on <a href="https://mail-archives.apache.org/mod_mbox/#couchdb">the mailing lists</a>. Any discussion that takes place away from the lists (for example on IRC or in person) must be brought to the lists before anything can be decided. We have a saying: if it's not on the lists, it didn't happen. We take this approach so that the greatest amount of people have a chance to participate.
+<p>All decision making must happen on <a href="https://couchdb.apache.org/#mailing-lists">the mailing lists</a>. Any discussion that takes place away from the lists (for example on IRC or in person) must be brought to the lists before anything can be decided. We have a saying: if it's not on the lists, it didn't happen. We take this approach so that the greatest amount of people have a chance to participate.
-<p>Decisions should be made on the mailing list associated with the decision. For example, marketing decisions happen on <a href="https://mail-archives.apache.org/mod_mbox/couchdb-marketing/">the marketing list</a>. By default, anything without a specific list should be done in public on the main development list. Anything that needs to be private will be done on the private list.
+<p>Decisions should be made on the mailing list associated with the decision. For example, marketing decisions happen on <a href="https://lists.apache.org/list.html?marketing@couchdb.apache.org">the marketing list</a>. By default, anything without a specific list should be done in public on the main development list. Anything that needs to be private will be done on the private list.
<p>Our decision making processes are designed to reduce blockages. It is understood that people come and go as time permits. It is not practical to hear from everybody on every decision. Sometimes, this means a decision will be taken while you are away from the project. It is reasonable to bring such decisions up for discussion again, but this should be kept to a minimum.
@@ -178,7 +178,7 @@
<p>For this to work properly, active committers are expected to be paying attention to the project. Objecting a long time after a change has been made may require large amounts of additional work to be thrown away or redone.
-<p>Sometimes, you might not be sure what the community would want. If this is the case, you can post a note to the appropriate <a href="https://mail-archives.apache.org/mod_mbox/#couchdb">mailing list</a> with an outline of what you intend to do. If nobody objects after 72 hours, you can safely assume consensus and proceed with your plan.
+<p>Sometimes, you might not be sure what the community would want. If this is the case, you can post a note to the appropriate <a href="https://couchdb.apache.org/#mailing-lists">mailing list</a> with an outline of what you intend to do. If nobody objects after 72 hours, you can safely assume consensus and proceed with your plan.
<p>An important side effect of this policy is that <em>silence is assent</em>. There is no need for discussion, and no need for agreement to be voiced. If you make a proposal to the list and nobody responds, that should be interpreted as implicit support for your idea, and not a lack of interest. This can be hard to get used to, but is an important part of how we do things.
@@ -289,7 +289,7 @@
<h3 id="rtc">3.5. Review-Then-Commit and Technical Vetos</h3>
-<p>Typically, CouchDB uses the <a href="http://www.apache.org/foundation/glossary.html#ReviewThenCommit">Review-Then-Commit</a> (<em>RTC</em>) model of code collaboration. RTC allows work to proceed on separate feature or bugfix branches, and requires at least one other developer to review and approve the changes before they are committed to a release branch. A release branch is any branch that a release might be prepared from, such as <code>master</code>, <code>1.6.x</code>, and so on. [...]
+<p>Typically, CouchDB uses the <a href="http://www.apache.org/foundation/glossary.html#ReviewThenCommit">Review-Then-Commit</a> (<em>RTC</em>) model of code collaboration. RTC allows work to proceed on separate feature or bugfix branches, and requires at least one other developer to review and approve the changes before they are committed to a release branch. A release branch is any branch that a release might be prepared from, such as <code>master</code>, <code>1.6.x</code>, and so on. [...]
<p><strong>Any change made to a release branch or to the <code>master</code> branch is a <em>technical decision</em> of the project. If a committer wants to object to a technical decision, they have the option of casting a -1 vote. We call this a veto.</strong> Vetos can only be made for technical reasons. A -1 vote is not considered a veto in any other context. Vetos should be used sparingly, and only after careful consideration.
@@ -343,12 +343,12 @@ The process is:
<tr>
<td>Technical decision
<td>A technical decision is any change made to a release branch.
- <td><a href="https://mail-archives.apache.org/mod_mbox/couchdb-commits/">Commits list</a>
+ <td><a href="https://lists.apache.org/list.html?commits@couchdb.apache.org">Commits list</a>
<td>Allowed for trivial changes
<td>RTC
<td>No
<td>Committers
- <td> Yes
+ <td>Yes
</tr>
<tr>
<td>Request For Comments (RFC) decision
@@ -381,7 +381,7 @@ The process is:
<br>
<br>
A veto is only valid when it is justified with a sound technical argument.
- <td><a href="https://mail-archives.apache.org/mod_mbox/couchdb-dev/">Main development list</a>
+ <td><a href="https://lists.apache.org/list.html?dev@couchdb.apache.org">Main development list</a>
<td>No
<td>Lazy 2/3 majority
<td>No
@@ -395,7 +395,7 @@ The process is:
<br>
<br>
Release candidates can be prepared by anyone.
- <td><a href="https://mail-archives.apache.org/mod_mbox/couchdb-dev/">Main development list</a>
+ <td><a href="https://lists.apache.org/list.html?dev@couchdb.apache.org">Main development list</a>
<td>No
<td>Lazy majority
<td>No
@@ -473,7 +473,7 @@ The process is:
<tr>
<td>Create or amend official document
<td>Create or amend any document marked as official.
- <td><a href="https://mail-archives.apache.org/mod_mbox/couchdb-dev/">Main development list</a>
+ <td><a href="https://lists.apache.org/list.html?dev@couchdb.apache.org">Main development list</a>
<td>No
<td>Lazy 2/3 majority
<td>No