community-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rgard...@apache.org
Subject svn commit: r1130546 - /comdev/site/trunk/content/contributors/index.mdtext
Date Thu, 02 Jun 2011 13:42:41 GMT
Author: rgardler
Date: Thu Jun  2 13:42:40 2011
New Revision: 1130546

URL: http://svn.apache.org/viewvc?rev=1130546&view=rev
Log:
CMS commit to community by rgardler

Modified:
    comdev/site/trunk/content/contributors/index.mdtext

Modified: comdev/site/trunk/content/contributors/index.mdtext
URL: http://svn.apache.org/viewvc/comdev/site/trunk/content/contributors/index.mdtext?rev=1130546&r1=1130545&r2=1130546&view=diff
==============================================================================
--- comdev/site/trunk/content/contributors/index.mdtext (original)
+++ comdev/site/trunk/content/contributors/index.mdtext Thu Jun  2 13:42:40 2011
@@ -18,25 +18,73 @@ Notice:    Licensed to the Apache Softwa
 
 This page is intended for those people who are reasonably 
 comfortable with open source development models but need a helping hand finding 
-their way around The Apache Software Foundation.
-
-At the time of writing we don't have much here, so we suggest you mail us
-with your questions.
+their way around The Apache Software Foundation and our way of developing software
+(commonly called "The Apache Way"). For those wishing to start from
+the very beginning we have a [newcomers page][1] too.
 
 ## Project Independence
 
 While not all aspects of the Apache Way are practiced the same way by 
 all projects at the ASF, there are a number of rules that Apache 
 projects are required to follow – things like complying with PMC 
-[release voting][1], [legal policy][2], [brand policy][3], 
-using [mailing lists][4], etc., which are [documented in various places][5]. 
+[release voting][2], [legal policy][3], [brand policy][4], 
+using [mailing lists][5], etc., which are [documented in various places][6]. 
 
 One of these invariant rules is that projects are managed and used
 independently of any commercial interests. The goal is to createan 
 environemnt in which all participants are equal and thus have an equal
 opportunity to contribute to and benefit from our software, regardless
 of motivation or financial objectives. This is discussed in more detail
-in our document [Project Independence][6].
+in our document [Project Independence][7].
+
+## From contributor to committer
+
+Anyone can be a contributor to an Apache project. Being a contributor simply means
+that you take an interest in the project and contribute in some way, ranging from asking
+sensible questions (which documents the project and provides feedback to developers)
+through to providing new features as patches.
+
+If you become a valuable contributor to the project you may well be invited to become
+a committer. Committer is an term used at the ASF to signify someone who is
+committed to a particular project. It brings with it the privilege of right access to
+the project repository and resources. In many projects committers are also invited 
+to be part of the core group within the project that ensures the project's vitality 
+(represented by the Project Management Committee, PMC). In a few projects a only a subset
of 
+committers, who have earned even more merit, are invited to be a part of the PMC.
+
+One thing that is sometimes hard to understand when you are new to the open 
+development1 process used at the ASF, is that we value the community more than 
+the code. A strong and healthy community will be respectful and be a fun and 
+rewarding place. Strong code will evolve. 
+
+### Contributing to the Project - CoPDoC
+
+The foundations of an Apache project and how the community contributes to it is 
+sometimes referred to by the acronym CoPDoC:
+
+  - (Co)mmunity - one must interact with others, and share vision and knowledge
+  - (P)roject - a clear vision and consensus are needed
+  - (Do)cumentation - without it, the stuff remains only in the minds of the authors
+  - (C)ode - discussion goes nowhere without code
+
+### Becoming a Committer
+
+There is nothing at The Apache Software Foundation that says you must write code 
+in order to be a committer. Anyone who is supportive of the community and works 
+in any of the CoPDoC areas is a likely candidate for committership.
+
+Apache is a meritocracy. That is, once someone has contributed sufficiently to 
+any area of CoPDoC they can be voted in as a committer. Being a committer does 
+not mean you commit code, it means you are committed to the project.
+
+One of the key contributions people can make to the community is through the 
+support of a wide user base by assisting users on the user list, writing user 
+oriented docs and ensuring the user viewpoint is understood by all developers. 
+A main idea behind being a committer is the ability to be a mentor and to work 
+cooperatively with your peers.
+
+Some of those users become committers in their own write. Some will test code, 
+some will write documentation, some will do bug triage and some will write code.
 
 ## Questions and Feedback
 
@@ -46,9 +94,10 @@ list by sending a mail to 
 [dev@community.apache.org](mailto:dev@community.apache.org).
 
 
-  [1]: http://www.apache.org/dev/release.html
-  [2]: http://www.apache.org/legal/
-  [3]: http://www.apache.org/foundation/marks/
-  [4]: http://www.apache.org/dev/#mail
-  [5]: https://blogs.apache.org/comdev/entry/what_makes_apache_projects_different
-  [6]: /projectIndependence.html
\ No newline at end of file
+  [1]: /newcomers/index.html
+  [2]: http://www.apache.org/dev/release.html
+  [3]: http://www.apache.org/legal/
+  [4]: http://www.apache.org/foundation/marks/
+  [5]: http://www.apache.org/dev/#mail
+  [6]: https://blogs.apache.org/comdev/entry/what_makes_apache_projects_different
+  [7]: /projectIndependence.html
\ No newline at end of file



Mime
View raw message