forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r386937 - /forrest/trunk/site-author/content/xdocs/guidelines.xml
Date Sun, 19 Mar 2006 07:46:01 GMT
Author: crossley
Date: Sat Mar 18 23:45:59 2006
New Revision: 386937

URL: http://svn.apache.org/viewcvs?rev=386937&view=rev
Log:
Commence a new section "Contribution and acknowledgement" to define
how the project currently recognises contributions. More points to come.

Modified:
    forrest/trunk/site-author/content/xdocs/guidelines.xml

Modified: forrest/trunk/site-author/content/xdocs/guidelines.xml
URL: http://svn.apache.org/viewcvs/forrest/trunk/site-author/content/xdocs/guidelines.xml?rev=386937&r1=386936&r2=386937&view=diff
==============================================================================
--- forrest/trunk/site-author/content/xdocs/guidelines.xml (original)
+++ forrest/trunk/site-author/content/xdocs/guidelines.xml Sat Mar 18 23:45:59 2006
@@ -641,6 +641,67 @@
 
   </section>
 
+  <section id="contribution">
+    <title>Contribution and acknowledgement</title>
+    <p>
+      Some <link href="#way">principles</link> of the Apache Way are to ensure
that each
+      contributor is recognised and feels a productive part of the community, and to
+      encourage diversity, respect, and equality.
+      Key to this is the recognition of contributions from individuals
+      in a manner that also recognises the community effort that made it all
+      possible. It is important to remember that there is no concept of
+      individual leadership.
+    </p>
+    <p>
+      At Apache Forrest we use the following method to provide recognition:
+    </p>
+    <ul>
+      <li>
+        All developers encourage other developers to participate on the
+        mailing lists, treat each other with respect, and openly collaborate.
+        This enables the contributors to feel a part of the project and shows
+        that their discussion and ideas are valuable. These replies enhance
+        the presence of their name in the email archives and search engines.
+      </li>
+      <li>
+        Encourage contributors to add patches via the
+        <link href="site:bugs">issue tracker</link>. This also enables clear
+        tracking of the issue and by default specifically shows who was the
+        contributor.
+      </li>
+      <li>
+        When committers apply the patch, they refer to the issue number
+        and the contributor's name. This enables linkage between the issue
+        tracker and the Subversion history. It adds the contributor's name
+        to the mail archives.
+      </li>
+      <li>
+        Committers apply patches as soon as possible. This keeps the contributor
+        enthused and shows them that their work is valuable.
+      </li>
+      <li>
+        Committers add an entry for each significant contribution to the
+        top-level <link href="site:changes">changes</link> document (site-author/status.xml)
+        and detailed entries to the relevant plugin's changes document. This enables linkage
+        to the relevant issue and shows the contributor's name. It also shows
+        the initials of the committer who did the work to add the patch.
+      </li>
+      <li>
+        When committers are adding their own work, they similarly add entries
+        to the "changes" documents. Their initials are added to the entry.
+      </li>
+      <li>
+        The existing PMC will notice new contributors who are committed. It eventually
+        <link href="#elect">invites</link> them to become new committers/PMC
members. See the 
+        <link href="site:committed">notes</link> about this topic.
+      </li>
+      <li>
+        Committers/PMC members are
+        <link href="site:who">listed</link>.
+      </li>
+    </ul>
+  </section>
+
   <section id="develop">
     <title>Development procedure</title>
 



Mime
View raw message