Author: hboutemy
Date: Sat Jul 27 12:47:43 2013
New Revision: 1507630

URL: http://svn.apache.org/r1507630
Log:
added links to existing documentation for contributors and developers

Modified:
    maven/site/trunk/content/markdown/project-roles.md

Modified: maven/site/trunk/content/markdown/project-roles.md
URL: 
http://svn.apache.org/viewvc/maven/site/trunk/content/markdown/project-roles.md?rev=1507630&r1=1507629&r2=1507630&view=diff
==============================================================================
--- maven/site/trunk/content/markdown/project-roles.md (original)
+++ maven/site/trunk/content/markdown/project-roles.md Sat Jul 27 12:47:43 2013
@@ -119,6 +119,8 @@ Maven and Maven plugins,
 * Help curate bug reports by identifying duplicate reports, or
 related issues.
 
+We wrote [a guide for contributors](/guides/development/guide-helping.html).
+
 Keep up the contributions, you are a critical member of our 
 community. If we like what we see, we may even ask you to 
 consider taking a formal role in our project.
@@ -131,7 +133,8 @@ These are those people who have been giv
 Apache Maven code repository and have a signed 
 [Contributor License Agreement (CLA)][4] on file with the ASF.
 
-The Apache Maven project uses a Commit then Review policy.
+The Apache Maven project uses a Commit then Review policy and has
+[a number of conventions][5] which should be followed.
 
 Committers are responsible for ensuring that every file they 
 commit is covered by a valid CLA. 
@@ -174,6 +177,7 @@ The Project Management Committee has the
 * Proposing active contributors for committership,
 * Binding votes in project decisions,
 * Voting on release artifacts,
+* Ensure [Developers Conventions][5] are followed, or updated/improved if 
necessary,
 * <!-- TODO: get the rest of these -->
 
 #### Standards for Community Commitment
@@ -217,3 +221,4 @@ Committee as a whole that is responsible
   [2]: mailto:us...@maven.apache.org
   [3]: mailto:priv...@maven.apache.org
   [4]: http://www.apache.org/licenses/#clas
+  [5]: /developers/index.html#Developers_Conventions


Reply via email to