forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r387787 - /forrest/trunk/site-author/content/xdocs/guidelines.xml
Date Wed, 22 Mar 2006 08:09:00 GMT
Author: crossley
Date: Wed Mar 22 00:08:58 2006
New Revision: 387787

URL: http://svn.apache.org/viewcvs?rev=387787&view=rev
Log:
Add paragraph to explain some ways that interested people
can find out who did what.

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=387787&r1=387786&r2=387787&view=diff
==============================================================================
--- forrest/trunk/site-author/content/xdocs/guidelines.xml (original)
+++ forrest/trunk/site-author/content/xdocs/guidelines.xml Wed Mar 22 00:08:58 2006
@@ -54,7 +54,8 @@
       in its own way - there is healthy diversity rather than uniformity across all projects.
       The main principles are to facilitate open collaborative development, with respect
for
       others; to ensure that there is a healthy community (even to give community issues
-      higher priority than code issues); to ensure that each contributor is recognised and
+      higher priority than code issues); to ensure that each
+      <link href="#contribution">contributor</link> is recognised and
       feels a productive part of the community; to encourage diversity; to make the project
a nice place to be.
     </p>
     <p>
@@ -710,6 +711,14 @@
         <link href="site:who">listed</link>.
       </li>
     </ul>
+    <p>
+      As discussed above, there is no specific documentation which lists each
+      contributor and their work. For those who are interested there are various
+      mechanisms: Use general internet search services; use search services provided
+      by various third-party mail archives; search the "svn" mailing list using
+      committer IDs and using contributor names; browse the
+      <link href="site:changes">changes</link> page; use 'svn log' and 'svn blame'.
+    </p>
   </section>
 
   <section id="develop">



Mime
View raw message