From svn-return-3269-apmail-forrest-svn-archive=forrest.apache.org@forrest.apache.org Sun Aug 07 01:56:45 2005 Return-Path: Delivered-To: apmail-forrest-svn-archive@www.apache.org Received: (qmail 81091 invoked from network); 7 Aug 2005 01:56:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 7 Aug 2005 01:56:45 -0000 Received: (qmail 13785 invoked by uid 500); 7 Aug 2005 01:56:44 -0000 Delivered-To: apmail-forrest-svn-archive@forrest.apache.org Received: (qmail 13749 invoked by uid 500); 7 Aug 2005 01:56:44 -0000 Mailing-List: contact svn-help@forrest.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: "Forrest Developers List" List-Id: Delivered-To: mailing list svn@forrest.apache.org Received: (qmail 13734 invoked by uid 99); 7 Aug 2005 01:56:43 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 06 Aug 2005 18:56:43 -0700 X-ASF-Spam-Status: No, hits=-9.8 required=10.0 tests=ALL_TRUSTED,NO_REAL_NAME X-Spam-Check-By: apache.org Received: from [209.237.227.194] (HELO minotaur.apache.org) (209.237.227.194) by apache.org (qpsmtpd/0.29) with SMTP; Sat, 06 Aug 2005 18:56:32 -0700 Received: (qmail 80700 invoked by uid 65534); 7 Aug 2005 01:56:41 -0000 Message-ID: <20050807015641.80698.qmail@minotaur.apache.org> Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r230615 - in /forrest/trunk/site-author/content/xdocs: committed-1.aart committed.xml Date: Sun, 07 Aug 2005 01:56:41 -0000 To: svn@forrest.apache.org From: crossley@apache.org X-Mailer: svnmailer-1.0.3 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Author: crossley Date: Sat Aug 6 18:56:35 2005 New Revision: 230615 URL: http://svn.apache.org/viewcvs?rev=230615&view=rev Log: New document to describe the process of becoming a committer. Add patch as-is, except converted tabs to two-space and used 'fold -s -w60' to break long lines. Submitted by: Addison Berry Issue: FOR-603 Added: forrest/trunk/site-author/content/xdocs/committed-1.aart (with props) forrest/trunk/site-author/content/xdocs/committed.xml (with props) Added: forrest/trunk/site-author/content/xdocs/committed-1.aart URL: http://svn.apache.org/viewcvs/forrest/trunk/site-author/content/xdocs/committed-1.aart?rev=230615&view=auto ============================================================================== --- forrest/trunk/site-author/content/xdocs/committed-1.aart (added) +++ forrest/trunk/site-author/content/xdocs/committed-1.aart Sat Aug 6 18:56:35 2005 @@ -0,0 +1,3 @@ ++----------------------------+------------------+---------+ +| Users | Developers | Mentors | ++----------------------------+------------------+---------+ Propchange: forrest/trunk/site-author/content/xdocs/committed-1.aart ------------------------------------------------------------------------------ svn:eol-style = native Added: forrest/trunk/site-author/content/xdocs/committed.xml URL: http://svn.apache.org/viewcvs/forrest/trunk/site-author/content/xdocs/committed.xml?rev=230615&view=auto ============================================================================== --- forrest/trunk/site-author/content/xdocs/committed.xml (added) +++ forrest/trunk/site-author/content/xdocs/committed.xml Sat Aug 6 18:56:35 2005 @@ -0,0 +1,117 @@ + + + + +
+ How to Become a Forrest Committer + This is a basic discussion of how users can progress to + become committers within the Apache Forrest project. +
+ +
+ What is a committer? + This is a work in progess taken from the mail list + discussion located at http://marc.theaimsgroup.com/?l=forrest-dev&m=112239074 +108858&w=2. Further editing of this page is needed and would + be greatly appreciated. +

Committer is an Apache term used to signify someone who is + committed to a particular project and who is invited to be part of + the core group within the project that ensures the project's vitality + (represented by the PMC, Project Management Committee). One thing + that is sometimes hard to understand when you are new to the Apache + Way1 is that we don't really care about code, it is the + community we care about. This is because a strong and healthy + community will usually generate strong and healthy code. As a result + of the Apache focus on community it is more important for people here + to discuss and explore within the community.

+
+
+ Contributing to the Project - CoPDoC +

The foundation of a project and how the community contributes + to it is known 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 within Apache 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 devs. A + main idea behind being a committer is the ability to be a mentor and + to work cooperatively with your peers.

+

The following diagram shows the progression of a user to a + committer/mentor.

+

committer path

+

Meritocracy progresses this way + ------------> ------------------------>

+

Note that this is not a heirarchy, it is a progression from a + broad user base from which those that wish to to contribute to the + ongoing development of the project (again, through any aspect of + CoPDoC, not just coding) can become involved as developers. From + these developers are those who take on additional roles of mentoring + and more fully commit themselves to the project.

+
+
+ Adding to the discussions +

Discussion leads to a clearer community understanding of the + project's goals and objectives and also of how the community works. + Of course, there has to be a balance between too much chat and not + enough code. If something is easy to do in code and does not impact + the overall product (such as a bug fix) then just go ahead and do it. + However, if something is to introduce a new feature it is best to + introduce your idea to the community via an email to the dev mail + list first. In this introduction you should outline why you want to + do something, how you propose to do it (pseudo code is a good way of + expressing this) and ask for comments. Any comments you receive will + help you fine tune your design and, in many cases, produce a quicker, + more elegant solution (this is the benefit of many eyes on a + solution). In Apache the absence of comments from others does not + mean it is not a good idea, in fact the reverse is true, it means + nobody has any objection or anything to add. It is only if people + respond that you need to discuss further. Once the discussion reaches + consensus then coding can proceed. Once you have implicit or explicit + approval for your contribution just go ahead and do it. Be sure to + document what you have done whilst you are at it. Without + documentation (comments in code, mailing list discussion and user + docs) your code is next to useless - nobody knows it is there and + nobody knows how it works.

+
+
+ References +

1 For more information on "the Apache Way" see http://www.a +pache.org/foundation/how-it-works.html.

+
+ + Propchange: forrest/trunk/site-author/content/xdocs/committed.xml ------------------------------------------------------------------------------ svn:eol-style = native