community-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From n...@apache.org
Subject svn commit: r1037091 [2/2] - /comdev/site/trunk/content/
Date Sat, 20 Nov 2010 00:14:11 GMT
Modified: comdev/site/trunk/content/mentoringprogramme.mdtext
URL: http://svn.apache.org/viewvc/comdev/site/trunk/content/mentoringprogramme.mdtext?rev=1037091&r1=1037090&r2=1037091&view=diff
==============================================================================
--- comdev/site/trunk/content/mentoringprogramme.mdtext (original)
+++ comdev/site/trunk/content/mentoringprogramme.mdtext Sat Nov 20 00:14:10 2010
@@ -1,134 +1,247 @@
 Title: MentoringProgramme
-Many projects in the ASF are able to provide mentors for newcomers. In fact, most projects are happy to assist newcomers to their projects as part of their normal operations. However, some people are looking for more structure. The Mentor Programme of the The Apache Software Foundation provides additional support and structure for people looking to make an initial contribution to an ASF project.
-
-The mentoring programme is not here to teach you to write documentation or code. It is here to help you understand how to make a valuable contribution to an Apache project. You can expect to be guided through our contribution processes. You can also expect to get technical support with respect to your chosen project. You cannot expect your mentor to be a "teacher", they will provide enough information for you to progress within the project. You need to bring the confidence to take their guidance and discover the detail for yourself.
-
-This page is a description of the Mentoring Programme. The program is open for business, but, like many other things at the Foundation, it under constant improvement and revision. Therefore, the description below is marked 'draft.'
+Many projects in the ASF are able to provide mentors for newcomers. In
+fact, most projects are happy to assist newcomers to their projects as part
+of their normal operations. However, some people are looking for more
+structure. The Mentor Programme of the The Apache Software Foundation
+provides additional support and structure for people looking to make an
+initial contribution to an ASF project.
+
+The mentoring programme is not here to teach you to write documentation or
+code. It is here to help you understand how to make a valuable contribution
+to an Apache project. You can expect to be guided through our contribution
+processes. You can also expect to get technical support with respect to
+your chosen project. You cannot expect your mentor to be a "teacher", they
+will provide enough information for you to progress within the project. You
+need to bring the confidence to take their guidance and discover the detail
+for yourself.
+
+This page is a description of the Mentoring Programme. The program is open
+for business, but, like many other things at the Foundation, it under
+constant improvement and revision. Therefore, the description below is
+marked 'draft.'
 
+<a name="MentoringProgramme-QuickDefinitions"></a>
 # Quick Definitions
 
-The ASF believes that the best way for people (and, indeed, entire projects) to join the community is with the help of committed members of the community. A community member who makes a commitment to help a new contributor get started is a _mentor_. The new person, on the other hand, is a _mentee_. Believe it or not, that is the word in the dictionary for this role.
-
-The Foundation is organized into a series of Top Level Projects, or TLPs. The document uses &#39;TLP&#39; when it is referring to an ASF project. It uses the word &#39;project&#39; to refer to a the work a mentee does under the Mentoring Programme.
+The ASF believes that the best way for people (and, indeed, entire
+projects) to join the community is with the help of committed members of
+the community. A community member who makes a commitment to help a new
+contributor get started is a _mentor_. The new person, on the other hand,
+is a _mentee_. Believe it or not, that is the word in the dictionary for
+this role.
+
+The Foundation is organized into a series of Top Level Projects, or TLPs.
+The document uses 'TLP' when it is referring to an ASF project. It uses the
+word 'project' to refer to a the work a mentee does under the Mentoring
+Programme.
 
+<a name="MentoringProgramme-Whocanbeamentee?"></a>
 # Who can be a mentee?
 
-The Mentor Programme is intended to assist people in becoming contributors to ASF projects. Thus, anyone interested in contributing effort to an ASF project is a potential mentee. You need to be a self starter, your mentor will not take responsibility for &quot;managing&quot; your work here. Everyone who contributes to an Apache project does so on a voluntary basis, there are no managers here - only helpful peers.
-
-Mentoring is a significant volunteer effort, over and above what the mentor is already doing for the project. Therefore, the programme asks mentees to make a material commitment of time to the process. There are no legally binding commitments involved, but a mentee must, as described below, submit a plan for a significant effort and show ongoing progress.
-
-It is important to reiterate that all work on ASF projects is on a volunteer basis. The Foundation does not pay anyone to mentor or contribute.
+The Mentor Programme is intended to assist people in becoming contributors
+to ASF projects. Thus, anyone interested in contributing effort to an ASF
+project is a potential mentee. You need to be a self starter, your mentor
+will not take responsibility for "managing" your work here. Everyone who
+contributes to an Apache project does so on a voluntary basis, there are no
+managers here - only helpful peers.
+
+Mentoring is a significant volunteer effort, over and above what the mentor
+is already doing for the project. Therefore, the programme asks mentees to
+make a material commitment of time to the process. There are no legally
+binding commitments involved, but a mentee must, as described below, submit
+a plan for a significant effort and show ongoing progress.
+
+It is important to reiterate that all work on ASF projects is on a
+volunteer basis. The Foundation does not pay anyone to mentor or
+contribute.
 
+<a name="MentoringProgramme-ApplyingfortheMentorProgramme"></a>
 ## Applying for the Mentor Programme
 
 There are two simple steps to apply:
 
 # Review the content below to learn about the details of the requirements.
-# [Fill out the application form](mentorprogrammeapplication.html).
+#
+[Fill out the application form](mentorprogrammeapplication.html).
 
-If you are a student and wish to apply to the mentoring programme as part of your formal education there are some [additional requirements](mentorprogrammeformaleducation.html) that you must fulfill, along with your tutor.
+If you are a student and wish to apply to the mentoring programme as part
+of your formal education there are some
+[additional requirements](mentorprogrammeformaleducation.html) that you must
+fulfill, along with your tutor.
 
+<a name="MentoringProgramme-Draft:TheASFMentoringProgramme"></a>
 # Draft: The ASF Mentoring Programme
 
-The Mentoring Programme is structured around mentee projects. Each mentee project is a coherent task contributing to one of the ASF&#39;s ongoing TLPs.
-
-The Mentoring Programme does not work on a fixed calendar. Project start as mentees and mentors are matched. Typically a project will last around three months, but mentors and mentees are free to negotiate longer or shorter periods of work.
+The Mentoring Programme is structured around mentee projects. Each mentee
+project is a coherent task contributing to one of the ASF's ongoing TLPs.
 
-The work of a mentee project can be code or documentation, so long as it contributes to an existing Foundation project. Individual research or prototyping projects are not acceptable -- working with an ASF project community is an essential part of the process.
+The Mentoring Programme does not work on a fixed calendar. Project start as
+mentees and mentors are matched. Typically a project will last around three
+months, but mentors and mentees are free to negotiate longer or shorter
+periods of work.
+
+The work of a mentee project can be code or documentation, so long as it
+contributes to an existing Foundation project. Individual research or
+prototyping projects are not acceptable -- working with an ASF project
+community is an essential part of the process.
 
+<a name="MentoringProgramme-SettingupaMentoringProject"></a>
 ## Setting up a Mentoring Project
 
-The first step is for a potential mentee to make contact with the Mentoring Programme. Several of the following steps call for interactions with potential mentors and target projects, and the Mentoring Programme mailing list is the appropriate forum.
-
-Next, a potential mentee should identify a Foundation TLP that he or she would like to contribute to, and seek out a suitable project. The mentee can propose an idea for a project, or ask the community for suggestions, or ask the mentors for suggestions.
-
-Given a target project and a rough idea for a task, the proposed mentee must create a written proposal for the task, send it to the project&#39;s development list for review, to ask for a sponsoring mentor. The sponsoring mentor will be a member of the TLP.
-
-This will lead to some negotiations with the project and a potential mentor. If these negotiations succeed, the mentor and mentee agree to a schedule and time commitment.
+The first step is for a potential mentee to make contact with the Mentoring
+Programme. Several of the following steps call for interactions with
+potential mentors and target projects, and the Mentoring Programme mailing
+list is the appropriate forum.
+
+Next, a potential mentee should identify a Foundation TLP that he or she
+would like to contribute to, and seek out a suitable project. The mentee
+can propose an idea for a project, or ask the community for suggestions, or
+ask the mentors for suggestions.
+
+Given a target project and a rough idea for a task, the proposed mentee
+must create a written proposal for the task, send it to the project's
+development list for review, to ask for a sponsoring mentor. The sponsoring
+mentor will be a member of the TLP.
+
+This will lead to some negotiations with the project and a potential
+mentor. If these negotiations succeed, the mentor and mentee agree to a
+schedule and time commitment.
 
 The plan must include a mid-project checkpoint as described below.
 
-The mentor submits the agreed plan to the Programme, gets an acknowledgment from the Apache Mentoring Programme admin,
-and adds the project to the Mentoring Wiki as an &quot;In Progress&quot; Project. 
+The mentor submits the agreed plan to the Programme, gets an acknowledgment
+from the Apache Mentoring Programme admin,
+and adds the project to the Mentoring Wiki as an "In Progress" Project. 
 
-The mentee sets up a wiki page for the project on the development Wiki, linked from the Mentoring page.
+The mentee sets up a wiki page for the project on the development Wiki,
+linked from the Mentoring page.
 
 The mentee joins the development community of the TLP and sets to work.
 
+<a name="MentoringProgramme-WorkingontheProject"></a>
 ## Working on the Project
 
-During the course of the project, the mentee is a member of the TLP community. This has implications for both the mentee and the 
+During the course of the project, the mentee is a member of the TLP
+community. This has implications for both the mentee and the 
 TLP.
 
-All Apache Software Foundation TLPs share some basic rules and conventions for their operations. Each TLP has its own specific
-conventions. The details of the ASF&#39;s conventions are beyond the scope of this document, but a few principles bear repeating:
+All Apache Software Foundation TLPs share some basic rules and conventions
+for their operations. Each TLP has its own specific
+conventions. The details of the ASF's conventions are beyond the scope of
+this document, but a few principles bear repeating:
 
 * Polite, respectful discourse.
 * Open, transparent, discussions and decision-making.
 * Open Source!
 
-During the course of the work, the mentor is responsible for helping the mentee navigate the process. If the mentee has questions, the 
-mentor answers or helps extract an answer from the community. If the mentee has any problem in working with the community, the 
-mentor is available via email for private consultation. On the other hand, The mentor is not intended to replace mentee background work.
-Mentees must still read code, read email archive, and do any other work needed.
-
-Mentees have one additional responsibility over and above the usual work of a contributor to a TLP: to give back to the Mentor Programme. 
-Mentees must document their work and experiences on the Mentor Programme wiki, to help the programme improve the process.
-
-In particular, mentees should document their code changes for possible review. This can come in the form of subversion revision numbers or JIRAs. For projects that are set up with FishEye, the Mentor Programme may set up a JIRA project, and open a JIRA for each mentee. The 
-mentee can then ask committers to include their JIRA in commit comments and thus set up automatic tracking.
+During the course of the work, the mentor is responsible for helping the
+mentee navigate the process. If the mentee has questions, the 
+mentor answers or helps extract an answer from the community. If the mentee
+has any problem in working with the community, the 
+mentor is available via email for private consultation. On the other hand,
+The mentor is not intended to replace mentee background work.
+Mentees must still read code, read email archive, and do any other work
+needed.
+
+Mentees have one additional responsibility over and above the usual work of
+a contributor to a TLP: to give back to the Mentor Programme. 
+Mentees must document their work and experiences on the Mentor Programme
+wiki, to help the programme improve the process.
+
+In particular, mentees should document their code changes for possible
+review. This can come in the form of subversion revision numbers or JIRAs.
+For projects that are set up with FishEye, the Mentor Programme may set up
+a JIRA project, and open a JIRA for each mentee. The 
+mentee can then ask committers to include their JIRA in commit comments and
+thus set up automatic tracking.
 
+<a name="MentoringProgramme-TheMid-ProjectReview"></a>
 ## The Mid-Project Review
 
-The Mentoring Programme reviews all projects at the half-way point. The input to the programme review is a pair of reports: one  from the mentor and from the mentee. These are public documents.
-
-The mentor&#39;s report must summarize progress and make a recommendation for the 
-disposition of the project: continue to completion, or stop. The report must also describe any changes to the project&#39;s scope.
+The Mentoring Programme reviews all projects at the half-way point. The
+input to the programme review is a pair of reports: one  from the mentor
+and from the mentee. These are public documents.
+
+The mentor's report must summarize progress and make a recommendation for
+the 
+disposition of the project: continue to completion, or stop. The report
+must also describe any changes to the project's scope.
 
+<a name="MentoringProgramme-ScopeandScheduleChanges"></a>
 ## Scope and Schedule Changes
 
-Inevitably, ugly facts will conflict with plans and intentions. Mentors and mentees can agree to change the scope of a project and document the change on the wiki and, as appropriate, on reports. The programme does not encourage scope changes as a solution if the mentee is 
-unwilling to put in the time and effort to carry out the project. In such a case, it is preferable to terminate the project. However,
+Inevitably, ugly facts will conflict with plans and intentions. Mentors and
+mentees can agree to change the scope of a project and document the change
+on the wiki and, as appropriate, on reports. The programme does not
+encourage scope changes as a solution if the mentee is 
+unwilling to put in the time and effort to carry out the project. In such a
+case, it is preferable to terminate the project. However,
 nothing is completely black and white.
 
-Similiarly, the programme prefers that projects end on their original schedule, rather than drag out indefinitely. 
-If a mentee has made good progress on a substantial project over several months, all while participating in the TLP community, 
-it is very likely that they are ready to continue without the help of a mentor. Their Mentor Programme project can end in good 
+Similiarly, the programme prefers that projects end on their original
+schedule, rather than drag out indefinitely. 
+If a mentee has made good progress on a substantial project over several
+months, all while participating in the TLP community, 
+it is very likely that they are ready to continue without the help of a
+mentor. Their Mentor Programme project can end in good 
 order even though coding continues.
 
+<a name="MentoringProgramme-FinishuptheProject"></a>
 ## Finish up the Project
 
-Every project ends, either when the work is done. or when the agree time period is over. At the end, the mentee updates the Wiki page with a final summary of their work.
-
-The mentor submits a final progress report and determination of whether the project should be marked complete or incomplete. 
-The admin acks the review and moves the project to completed or incomplete as appropriate on the Mentoring Wiki.
+Every project ends, either when the work is done. or when the agree time
+period is over. At the end, the mentee updates the Wiki page with a final
+summary of their work.
+
+The mentor submits a final progress report and determination of whether the
+project should be marked complete or incomplete. 
+The admin acks the review and moves the project to completed or incomplete
+as appropriate on the Mentoring Wiki.
 
-Relevant certification is issued to both the mentor and mentee by the admin team.
+Relevant certification is issued to both the mentor and mentee by the admin
+team.
 
+<a name="MentoringProgramme-RolesandExpectations"></a>
 ## Roles and Expectations
 
+<a name="MentoringProgramme-Mentee"></a>
 ### Mentee
 
-* The mentee is any individual interested in getting involved in open source.
-* The mentee is expected to dedicate a pre-agreed amount of time each week to the project. Failure to 
+* The mentee is any individual interested in getting involved in open
+source.
+* The mentee is expected to dedicate a pre-agreed amount of time each week
+to the project. Failure to 
 commit the agreed time is likely to result in failure on the programme,
-* The mentee is expected to complete the project as described in the proposal or make necessary scope adjustments with their mentor.
-* The mentee is expected to maintain a Wiki page recording their progress, which upon completion will present a final summary of their work with links to code changes.
-* The mentee is responsible for submitting progress reports at the half way and completion points of the programme.
+* The mentee is expected to complete the project as described in the
+proposal or make necessary scope adjustments with their mentor.
+* The mentee is expected to maintain a Wiki page recording their progress,
+which upon completion will present a final summary of their work with links
+to code changes.
+* The mentee is responsible for submitting progress reports at the half way
+and completion points of the programme.
 
+<a name="MentoringProgramme-Mentor"></a>
 ### Mentor
 
-* The mentor must be a committer on the project accepting the mentees contributions.
-* The mentor is expected to dedicate at least 1/4 of the mentee time per week to support.
-* The mentor is expected to process supplied patches within reasonable timeframes.
-* The mentor is expected to ensure appropriate assitance is available from the project community.
-* The mentor is responsible for submitting progress reports at the half way and completion points of the programme.
+* The mentor must be a committer on the project accepting the mentees
+contributions.
+* The mentor is expected to dedicate at least 1/4 of the mentee time per
+week to support.
+* The mentor is expected to process supplied patches within reasonable
+timeframes.
+* The mentor is expected to ensure appropriate assitance is available from
+the project community.
+* The mentor is responsible for submitting progress reports at the half way
+and completion points of the programme.
 
+<a name="MentoringProgramme-Admin"></a>
 ### Admin
 
-* The Apache Mentoring Program admin(s) will liaise with ASF projects to maintain a JIRA list of projects that are available and in progress.
+* The Apache Mentoring Program admin(s) will liaise with ASF projects to
+maintain a JIRA list of projects that are available and in progress.
 * The admin(s) will assist with matching mentees with mentors
-* The admin(s) will approve proposals and progress reports, but generally won&#39;t do an in depth technical review but will rely on the mentor&#39;s assessment.
-* The admin(s) will mediate any dispute between mentee and mentor regarding assessments/etc if the project community is unable to reach a resolution
-
-        
\ No newline at end of file
+* The admin(s) will approve proposals and progress reports, but generally
+won't do an in depth technical review but will rely on the mentor's
+assessment.
+* The admin(s) will mediate any dispute between mentee and mentor regarding
+assessments/etc if the project community is unable to reach a resolution

Added: comdev/site/trunk/content/mentorprogrammeapplication.mdtext
URL: http://svn.apache.org/viewvc/comdev/site/trunk/content/mentorprogrammeapplication.mdtext?rev=1037091&view=auto
==============================================================================
--- comdev/site/trunk/content/mentorprogrammeapplication.mdtext (added)
+++ comdev/site/trunk/content/mentorprogrammeapplication.mdtext Sat Nov 20 00:14:10 2010
@@ -0,0 +1,90 @@
+Title: MentorProgrammeApplication
+<a name="MentorProgrammeApplication-MentoringProgrammeApplicationProcedure"></a>
+# Mentoring Programme Application Procedure
+
+Applying for the Apache Mentoring Programme is simple. This page will take
+you through the steps:
+
+<a name="MentorProgrammeApplication-Creatingaproposalandfindingamentor"></a>
+## Creating a proposal and finding a mentor
+
+ # Find the project you are interested in (see our
+[FAQ](newbiefaq.html) for some guidance on how to do this)
+ # Examine the projects issue tracker to find bugs that need fixing or
+features that need implementing that you feel you can tackle
+ # Join the projects mailing list and post an introduction mail (something
+like this
+[mentor request mail](mentor-request-mail.html) will do nicely). 
+ # Liaise with the project mailing list to refine your proposal
+ # Write up your project proposal (see next section) and submit it to the
+project mailing list asking for someone to be your mentor.
+
+<a name="MentorProgrammeApplication-Projectproposal"></a>
+### Project proposal
+
+Your project proposal should include:
+
+ * Your full name
+ * Apache Project of interest
+ * Name of mentor
+ * Planned  start date
+ * Expected mid-term evaluation date
+ * End date
+ * Expected deliverables
+ * Expected benefits to the Apache Community as a result of your work
+ * Detailed description and high level design for your proposed solution
+ * Approximate number of hours you intend to work on the project each week
+and the number of weeks you expect it to take
+ * A description of why you want to undertake this project and what you
+hope to gain from it and the mentor programme
+ * A brief CV of your skills
+
+Note, we do not expect people to come to our mentor programme with a full
+armoury of skills, however mentors are not their to teach you only to guide
+you. You must be willing and able to put in the effort to learn any new
+skills needed. This programme is designed to help people engage with Apache
+projects. However, we do expect people to have sufficient technical skills
+to understand the guidance that the mentor and project community will
+provide. We are not here to teach basic programming skills, rather we are
+here to teach the application of those skills to an Apache Project.
+
+<a name="MentorProgrammeApplication-Applyingtothementoringprogramme"></a>
+## Applying to the mentoring programme
+
+At this point you will probably want to apply to the Community Development
+mentoring programme, however, you are not required to do so. If you so
+desire you can just get on with your work within the project community,
+after all, you already generated enough interest in your work to have the
+community offer to mentor you.
+
+The advantage of joining the mentoring programme formally is that you have
+access to a growing community of people who have recently done exactly what
+you are doing. That is you are trying to figure out how to efficiently
+participate in a community developed software project.
+
+Whilst the project the project community are there to help you with project
+specific issues you may face they are sometimes less willing to help guide
+you through the processes and tools available to you within the broader
+Apache community. That's where the Community Development project comes in.
+We are here to help with issues that are not project specific.
+
+To make us aware of your work in the ASF we request that you formally
+become a part of the mentoring programme. To do so all you need to do is:
+
+ # Join the Community development mailing list at dev@community.apache.org
+mailing list by sending a mail to
+[mailto:dev-subscribe@community.apache.org](mailto:dev-subscribe@community.apache.org.html) (this is where we coordinate
+all mentoring efforts)
+ # Submit your project proposal (see above) to the community development
+[issue tracker](https://issues.apache.org/jira/browse/COMDEV)
+ # Have your mentor "sign off" the proposal (i.e. indicate in a comment
+that they are willing to mentor the proposal)
+ # That's it, you are ready to go. Start work under the guidance of your
+mentor.
+
+If you have any problems during the application process or during the
+mentoring programme simply ask for advice on the project mailing list
+first, if that doesn't solve your problem then ask on the
+dev@community.apache.org list (note project specific issues should be kept
+to the project list).
+

Added: comdev/site/trunk/content/mentorprogrammeformaleducation.mdtext
URL: http://svn.apache.org/viewvc/comdev/site/trunk/content/mentorprogrammeformaleducation.mdtext?rev=1037091&view=auto
==============================================================================
--- comdev/site/trunk/content/mentorprogrammeformaleducation.mdtext (added)
+++ comdev/site/trunk/content/mentorprogrammeformaleducation.mdtext Sat Nov 20 00:14:10 2010
@@ -0,0 +1,55 @@
+Title: MentorProgrammeFormalEducation
+<a name="MentorProgrammeFormalEducation-MentoringinFormalEducation"></a>
+# Mentoring in Formal Education
+
+It is expected that some mentees will wish to participate in the
+[Mentoring Programme](mentoringprogramme.html) as part of a formal education
+course. In these cases there will be additional requirements on the process
+to ensure that the mentees can be evaluated by their tutor. This section
+describes these additional requirements and process.
+
+<a name="MentorProgrammeFormalEducation-Overview"></a>
+## Overview
+
+Projects are defined by the students tutor in consultation with the project
+community/mentors and the student. They will need to be isolated enough
+from other ongoing work to ensure that success/failure to deliver is not
+dependent on someone else. They will also need to be of sufficient
+complexity/simplicity to be a final year project.
+
+Tutors are responsible for the day to day management of the student. If the
+student does not participate in the project it is not a concern of the
+mentor. The mentor must be available for the tutor should a problem arise
+and must be willing to mentor the tutor with respect to how they encourage
+the students to participate
+
+<a name="MentorProgrammeFormalEducation-RolesandExpectations"></a>
+## Roles and Expectations
+In addition to the notes found in the
+[Mentoring Programme](mentoringprogramme.html) documentation the following should
+be considered.
+
+<a name="MentorProgrammeFormalEducation-Tutors"></a>
+### Tutors
+
+* Ensure the mentee is participating in the program
+* Tutor grades the student within their formal education (the mentor
+feedback should assist here)
+* Take full responsibility for the learners morivation and progress
+** Mentors will guide but will not motivate
+
+<a name="MentorProgrammeFormalEducation-Mentees"></a>
+### Mentees
+
+* mentees are typically students in their final year (exceptional students
+may be considered)
+* mentees participate as part of a practical project which forms a formal
+part of their examined work.
+
+<a name="MentorProgrammeFormalEducation-Admins"></a>
+### Admins
+
+* Provide assistance interpreting reports to allow tutors to grade student
+participation
+* Provide mediation between student, mentor and tutor in the event of a
+dispute
\ No newline at end of file

Modified: comdev/site/trunk/content/newbiefaq.mdtext
URL: http://svn.apache.org/viewvc/comdev/site/trunk/content/newbiefaq.mdtext?rev=1037091&r1=1037090&r2=1037091&view=diff
==============================================================================
--- comdev/site/trunk/content/newbiefaq.mdtext (original)
+++ comdev/site/trunk/content/newbiefaq.mdtext Sat Nov 20 00:14:10 2010
@@ -1,99 +1,224 @@
 Title: NewbieFAQ
-This set of Frequently Asked Questions are intended to help newcomers to The Apache Software Foundation understand how we work.
+This set of Frequently Asked Questions are intended to help newcomers to
+The Apache Software Foundation understand how we work.
 
 *Index of Questions*
 
-{toc}
-
-Note, there are not too many questions and answers here right now, this is a very new project. Please ask any new questions on mailto:dev@community.apache.org (subscribe with mailto:dev-subscribe@community.apache.org first).
+* [About The Apache Software Foundation](#NewbieFAQ-AboutTheApacheSoftwareFoundation)
+   * [What projects can I find in The Apache Software Foundation?](#NewbieFAQ-WhatprojectscanIfindinTheApacheSoftwareFoundation?)
+   * [How are projects managed in The Apache Software Foundation](#NewbieFAQ-HowareprojectsmanagedinTheApacheSoftwareFoundation)
+   * [How do I learn about the way Apache Projects Work?](#NewbieFAQ-HowdoIlearnaboutthewayApacheProjectsWork?)
+   * [How do I ask a question about the ASF in general?](#NewbieFAQ-HowdoIaskaquestionabouttheASFingeneral?)
+   * [How do I get user support for an ASF project?](#NewbieFAQ-HowdoIgetusersupportforanASFproject?)
+* [Getting Involved with Apache projects](#NewbieFAQ-GettingInvolvedwithApacheprojects)
+   * [How do I choose an Apache project to work on?](#NewbieFAQ-HowdoIchooseanApacheprojecttoworkon?)
+   * [How do I get involved with an Apache project?](#NewbieFAQ-HowdoIgetinvolvedwithanApacheproject?)
+   * [Is there a Code of Conduct for Apache projects?](#NewbieFAQ-IsthereaCodeofConductforApacheprojects?)
+   * [About the Apache Mentoring Programme](#NewbieFAQ-AbouttheApacheMentoringProgramme)
+      * [What is the Apache Mentoring Programme](#NewbieFAQ-WhatistheApacheMentoringProgramme)
+      * [How do I Apply to the Mentor Programme?](#NewbieFAQ-HowdoIApplytotheMentorProgramme?)
+
+Note, there are not too many questions and answers here right now, this is
+a very new project. Please ask any new questions on
+mailto:dev@community.apache.org (subscribe with
+mailto:dev-subscribe@community.apache.org first).
 
+<a name="NewbieFAQ-AboutTheApacheSoftwareFoundation"></a>
 # About The Apache Software Foundation
 
+<a name="NewbieFAQ-WhatprojectscanIfindinTheApacheSoftwareFoundation?"></a>
 ## What projects can I find in The Apache Software Foundation?
 
-There are a great many projects in The Apache Software Foundation. We have four classes of project:
+There are a great many projects in The Apache Software Foundation. We have
+four classes of project:
 
- * [Top Level Projects](http://www.apache.org) - these are projects with healthy communities and active development
- * [Incubating Projects](http://incubator.apache.org) - these are projects that have still to build a sustianble community, but have active development
- * [Labs](http://labs.apache.org) - these are experiments being carried out by existing committers
- * [Attic](http://attic.apache.org) - these are end-of-life projects that are no longer receiving active development, but may still be useful
+ *
+[Top Level Projects](http://www.apache.org) - these are projects with
+healthy communities and active development
+ *
+[Incubating Projects](http://incubator.apache.org) - these are projects that
+have still to build a sustianble community, but have active development
+ *
+[Labs](http://labs.apache.org) - these are experiments being carried out by
+existing committers
+ *
+[Attic](http://attic.apache.org) - these are end-of-life projects that are
+no longer receiving active development, but may still be useful
 
+<a name="NewbieFAQ-HowareprojectsmanagedinTheApacheSoftwareFoundation"></a>
 ## How are projects managed in The Apache Software Foundation
 
-Apache projects all believe that if we look after the community then good code will emerge from that community. That is, when people with similar needs come together they will work out a way of solving their common problems. It is for this very reason that we created the Community Development project (where you are right now), the ASF has grown to be very large and, from the outside, can look too mature for newcomers and novices. However, these communities seek to be flat in structure. No single person in that community has more influence than the next, a newcomer with a good idea has just as much input and influence as the original creator of the project.
-
-We do have a system that we call meritocracy that allows those who have demonstrated commitment and understanding to the community to earn certain privileges, such as being able to make changes directly to documentation and programme code. However, these privileges simply streamline the process, they do not (in most cases) give additional powers over the project.
+Apache projects all believe that if we look after the community then good
+code will emerge from that community. That is, when people with similar
+needs come together they will work out a way of solving their common
+problems. It is for this very reason that we created the Community
+Development project (where you are right now), the ASF has grown to be very
+large and, from the outside, can look too mature for newcomers and novices.
+However, these communities seek to be flat in structure. No single person
+in that community has more influence than the next, a newcomer with a good
+idea has just as much input and influence as the original creator of the
+project.
+
+We do have a system that we call meritocracy that allows those who have
+demonstrated commitment and understanding to the community to earn certain
+privileges, such as being able to make changes directly to documentation
+and programme code. However, these privileges simply streamline the
+process, they do not (in most cases) give additional powers over the
+project.
 
-In summary, Apache Projects work because people like you participate constructively within them. 
+In summary, Apache Projects work because people like you participate
+constructively within them. 
 
-To learn more about &quot;The Apache Way&quot; see the foundations [How It Works](http://apache.org/foundation/how-it-works.html) pages.
+To learn more about "The Apache Way" see the foundations
+[How It Works](http://apache.org/foundation/how-it-works.html) pages.
 
+<a name="NewbieFAQ-HowdoIlearnaboutthewayApacheProjectsWork?"></a>
 ## How do I learn about the way Apache Projects Work?
 
-You should consider applying to the [Apache Mentor Programme](mentoringprogramme.html). We will help you find a mentor within the project of your choice. They will take you through a semi-formal mentoring programme] that will ensure you quickly find your feet. There is no cost other than a promise to commit some of your time to the goals you agree with your mentor.
+You should consider applying to the
+[Apache Mentor Programme](mentoringprogramme.html). We will help you find a
+mentor within the project of your choice. They will take you through a
+semi-formal mentoring programme] that will ensure you quickly find your
+feet. There is no cost other than a promise to commit some of your time to
+the goals you agree with your mentor.
 
+<a name="NewbieFAQ-HowdoIaskaquestionabouttheASFingeneral?"></a>
 ## How do I ask a question about the ASF in general?
 
-The Community Development Project is here for this very purpose. Check out the resources on this site first, if you don&#39;t find the answer send a mail to mailto:dev@community.apache.org (subscribe first by sending a mail to mailto:dev-subscribe@community.apache.org)
+The Community Development Project is here for this very purpose. Check out
+the resources on this site first, if you don't find the answer send a mail
+to mailto:dev@community.apache.org (subscribe first by sending a mail to
+mailto:dev-subscribe@community.apache.org)
 
+<a name="NewbieFAQ-HowdoIgetusersupportforanASFproject?"></a>
 ## How do I get user support for an ASF project?
 
-Everyone active in ASF projects is here as a volunteer, nobody is paid to provide support here. So the first thing to realise is that you need to be careful not to waste peoples time, so do your homework. Generally, if people can see that you have tried to solve your problem they are more likely to help. So, before asking a question do the following:
+Everyone active in ASF projects is here as a volunteer, nobody is paid to
+provide support here. So the first thing to realise is that you need to be
+careful not to waste peoples time, so do your homework. Generally, if
+people can see that you have tried to solve your problem they are more
+likely to help. So, before asking a question do the following:
 
 * search the project documentation
 * search the project user lists
 * search the issue tracker for any related known issues
 * search the web in general
 
-If you don&#39;t find a solution send a concise, but detailed, request for support to the appropriate user mailing list (you will usually need to subscribe first). Indicate that you have read the appropriate documentation and explain what you have tried, what you expect to happen and what actually happens.
-
-Be patient waiting for a response, give it at least three working days before you send a second message. People are busy, they will deal with your request when they can. If you need urgent help it is best not to rely on the community support channels and find someone willing to support you for a fee.
-
-It is worth noting that people are more willing to help those who contribute back to the project in some way. If you hit a problem that was not documented then it is likely others will too. A good idea is to send a patch to the project to improve its documentation. This means that those who follow in your footsteps get an answer in the first step above and you start to build merit in the community that will result in further help in the future.
-
-A second way of contributing is to provide user support to others as your expertise grows. Again, earning merit in this way will help ensure you get the support you need in the future.
+If you don't find a solution send a concise, but detailed, request for
+support to the appropriate user mailing list (you will usually need to
+subscribe first). Indicate that you have read the appropriate documentation
+and explain what you have tried, what you expect to happen and what
+actually happens.
+
+Be patient waiting for a response, give it at least three working days
+before you send a second message. People are busy, they will deal with your
+request when they can. If you need urgent help it is best not to rely on
+the community support channels and find someone willing to support you for
+a fee.
+
+It is worth noting that people are more willing to help those who
+contribute back to the project in some way. If you hit a problem that was
+not documented then it is likely others will too. A good idea is to send a
+patch to the project to improve its documentation. This means that those
+who follow in your footsteps get an answer in the first step above and you
+start to build merit in the community that will result in further help in
+the future.
+
+A second way of contributing is to provide user support to others as your
+expertise grows. Again, earning merit in this way will help ensure you get
+the support you need in the future.
 
 
 If you are visible within the community
 
+<a name="NewbieFAQ-GettingInvolvedwithApacheprojects"></a>
 # Getting Involved with Apache projects
 
+<a name="NewbieFAQ-HowdoIchooseanApacheprojecttoworkon?"></a>
 ## How do I choose an Apache project to work on?
 
-The key to working on projects at Apache (and any open source for that matter) is to have a personal reason for being involved. You might be trying to solve a day job issue, you might be looking to learn a new technology or you might simply want to do somethiung fun in your free time. The key is that you must *want* to get involved. It is also important that you have appropriate skills to be able to help the project.
-
-Our [projects](http://projects.apache.org/) provides a useful index of projects which allows you to view projects alphabetically, by category or by language. When you view a projects detail page in this list you will find details of their mailing lists, issue tracker and other resoutrces.
-
-In the projects issue tracker you will find details of bugs and feature requests the project would like to work with, this should give you some inspiration about how you might be able to help the project community. If you see an issue you would like to tackle its time to join the projects mailing list and get started.
+The key to working on projects at Apache (and any open source for that
+matter) is to have a personal reason for being involved. You might be
+trying to solve a day job issue, you might be looking to learn a new
+technology or you might simply want to do somethiung fun in your free time.
+The key is that you must *want* to get involved. It is also important that
+you have appropriate skills to be able to help the project.
+
+Our
+[projects](http://projects.apache.org/) provides a useful index of projects
+which allows you to view projects alphabetically, by category or by
+language. When you view a projects detail page in this list you will find
+details of their mailing lists, issue tracker and other resoutrces.
+
+In the projects issue tracker you will find details of bugs and feature
+requests the project would like to work with, this should give you some
+inspiration about how you might be able to help the project community. If
+you see an issue you would like to tackle its time to join the projects
+mailing list and get started.
 
+<a name="NewbieFAQ-HowdoIgetinvolvedwithanApacheproject?"></a>
 ## How do I get involved with an Apache project?
 
-You can certainly improve your programming skills by watching the commit lists, receiving code reviews and participating in discussion. Howeverm this learning opportunity is a healthy side effect of open source activities rather than a goal in itself. Nobody in an Apache project is going to spend time teaching you programming 101, technical writing or testing (to pick just a few skills we need). You need to know the basics and be willing to research the rest.
-
-Our mentoring programme, see below, is designed to help you understand how to get guidance with respect to how to take your first steps in an open source project. You will also find our [get involved](http://apache.org/foundation/getinvolved.html) page a uaseful starting point.
+You can certainly improve your programming skills by watching the commit
+lists, receiving code reviews and participating in discussion. Howeverm
+this learning opportunity is a healthy side effect of open source
+activities rather than a goal in itself. Nobody in an Apache project is
+going to spend time teaching you programming 101, technical writing or
+testing (to pick just a few skills we need). You need to know the basics
+and be willing to research the rest.
+
+Our mentoring programme, see below, is designed to help you understand how
+to get guidance with respect to how to take your first steps in an open
+source project. You will also find our
+[get involved](http://apache.org/foundation/getinvolved.html) page a uaseful
+starting point.
 
+<a name="NewbieFAQ-IsthereaCodeofConductforApacheprojects?"></a>
 ## Is there a Code of Conduct for Apache projects?
 
-Here at Apache projects are free to define their own code of conduct. However, it is common for new projects to learn from the lessons of the older projects. The Apache Incubator project has a wiki page for collecting [common elements of Apache project Codes of Conduct](http://incubator.apache.org/guides/community.html).
-
-The Incubator document has some really useful for both the newbie and the old hands (we all fall into bad habits occasionally). The section on ASF Mottos is especially useful as a reminder of the way things are in most ASF projects. This section includes such gems as:
+Here at Apache projects are free to define their own code of conduct.
+However, it is common for new projects to learn from the lessons of the
+older projects. The Apache Incubator project has a wiki page for collecting
+[common elements of Apache project Codes of
+Conduct|http://incubator.apache.org/guides/community.html].
+
+The Incubator document has some really useful for both the newbie and the
+old hands (we all fall into bad habits occasionally). The section on ASF
+Mottos is especially useful as a reminder of the way things are in most ASF
+projects. This section includes such gems as:
 
 * Put community before code. 
 * Let they that do the work make the decisions. 
-* If it didn&#39;t happen on a mailing list, it didn&#39;t happen. 
-* Don&#39;t feed the trolls. 
+* If it didn't happen on a mailing list, it didn't happen. 
+* Don't feed the trolls. 
 
+<a name="NewbieFAQ-AbouttheApacheMentoringProgramme"></a>
 ## About the Apache Mentoring Programme
 
+<a name="NewbieFAQ-WhatistheApacheMentoringProgramme"></a>
 ### What is the Apache Mentoring Programme
 
-Many projects in the ASF are able to provide mentors for newcomers. In fact, most projects are happy to assist newcomers to their projects as part of their normal operations. However, some people are looking for more structure. The Mentor Programme of the The Apache Software Foundation provides additional support and structure for people looking to make an initial contribution to an ASF project.
+Many projects in the ASF are able to provide mentors for newcomers. In
+fact, most projects are happy to assist newcomers to their projects as part
+of their normal operations. However, some people are looking for more
+structure. The Mentor Programme of the The Apache Software Foundation
+provides additional support and structure for people looking to make an
+initial contribution to an ASF project.
 
-For more information see our [mentoring page](mentoringprogramme.html).
+For more information see our
+[mentoring page](mentoringprogramme.html).
 
+<a name="NewbieFAQ-HowdoIApplytotheMentorProgramme?"></a>
 ### How do I Apply to the Mentor Programme?
 
-Take a look at our [mentoring page](mentoringprogramme.html). If you are planning on working on an Apache project as part of your formal education you should also read [mentoring in formal education|mentorProgrammeFormalEducation].
-
-From the [mentoring page](mentoringprogramme.html) you will see that you need to complete an [application|mentorProgrammeapplication]. This gives us enough background information to enable us to approach your chosen project community and for you to work with prospective mentors in defining your mentored activity.
-        
\ No newline at end of file
+Take a look at our
+[mentoring page](mentoringprogramme.html). If you are planning on working on an
+Apache project as part of your formal education you should also read
+[mentoring in formal education|mentorProgrammeFormalEducation].
+
+From the
+[mentoring page](mentoringprogramme.html) you will see that you need to complete
+an
+[application|mentorProgrammeapplication]. This gives us enough background
+information to enable us to approach your chosen project community and for
+you to work with prospective mentors in defining your mentored activity.
\ No newline at end of file

Modified: comdev/site/trunk/content/newcommitter.mdtext
URL: http://svn.apache.org/viewvc/comdev/site/trunk/content/newcommitter.mdtext?rev=1037091&r1=1037090&r2=1037091&view=diff
==============================================================================
--- comdev/site/trunk/content/newcommitter.mdtext (original)
+++ comdev/site/trunk/content/newcommitter.mdtext Sat Nov 20 00:14:10 2010
@@ -1,32 +1,55 @@
 Title: NewCommitter
-Identifying potential new commiters, calling a vote for their recognition as a committer and processing the relevant documents is something that the whole community can contribute to.
-
-Each project has different approches to managing new committers, this page describes a common process found in many Apache projects. It also provides drafts for the various communications that are necessary.
+Identifying potential new commiters, calling a vote for their recognition
+as a committer and processing the relevant documents is something that the
+whole community can contribute to.
+
+Each project has different approches to managing new committers, this page
+describes a common process found in many Apache projects. It also provides
+drafts for the various communications that are necessary.
 
+<a name="NewCommitter-Guidelinesforassessingnewcandidatesforcommittership"></a>
 # Guidelines for assessing new candidates for committership
 
-When voting, all PMC members need to make up your own mind, perhaps search mailing lists and Jira, etc. The following are some tips that we developed. Also consider the Apache Forrest [committer fuidelines](http://forrest.apache.org/committed.html)
+When voting, all PMC members need to make up your own mind, perhaps search
+mailing lists and Jira, etc. The following are some tips that we developed.
+Also consider the Apache Forrest
+[committer fuidelines](http://forrest.apache.org/committed.html)
 
+<a name="NewCommitter-Abilitytoworkco-operativelywithpeers."></a>
 ## Ability to work co-operatively with peers. 
-How do we evaluate?  By the interactions they have through mail. By how they respond to criticism. By how they participate in decision-making process.
+How do we evaluate?  By the interactions they have through mail. By how
+they respond to criticism. By how they participate in decision-making
+process.
 
+<a name="NewCommitter-Abilitytobeamentor."></a>
 ## Ability to be a mentor.
-How do we evaluate?  By the interactions they have through mail. By how clear they are and how willing they are to point at appropriate background materials (or event create them).
+How do we evaluate?  By the interactions they have through mail. By how
+clear they are and how willing they are to point at appropriate background
+materials (or event create them).
 
+<a name="NewCommitter-Community"></a>
 ## Community
 How do we evaluate?  By the interactions they have through mail.
 
+<a name="NewCommitter-Committment"></a>
 ## Committment
-How do we evaluate?  By time, by sticking through tough issues, by helping on not-so-fun tasks as well.
+How do we evaluate?  By time, by sticking through tough issues, by helping
+on not-so-fun tasks as well.
 
+<a name="NewCommitter-Personalskill/ability"></a>
 ## Personal skill/ability
-# How do we evaluate?  A solid general understanding of the project.  Quality of discussion in mail.  Patches easy to apply with only
+# How do we evaluate?  A solid general understanding of the project. 
+Quality of discussion in mail.	Patches easy to apply with only
 a cursory review.
 
+<a name="NewCommitter-NewCommitterProcess"></a>
 # New Committer Process
 
-This section describes a typical Apache projects process for handling the voting of a new committer. Templates mentioned in the process appear at later in this document.
+This section describes a typical Apache projects process for handling the
+voting of a new committer. Templates mentioned in the process appear at
+later in this document.
 
+<a name="NewCommitter-Summary"></a>
 ## Summary
 
 # Call a vote: templates/committerVote.txt
@@ -34,70 +57,94 @@ This section describes a typical Apache 
 
 If they accept, then do:
 
-# Accept the committer - note this assumes the committer is also to be a PMC member (templates/committerAccept.txt)
+# Accept the committer - note this assumes the committer is also to be a
+PMC member (templates/committerAccept.txt)
 # wait until we see that receipt of CLA is recorded
 # Create the committer account (template/committerCreate.txt)
 ## now wait until root says it is done
 ## chair to enable their svn access
 ## add committer to the appropriate groups in Jira and CWiki
 # Notify the committer of completion (template/committerDone.txt)
-# chair send email to board@ asking for acknowledgement of new PMC member (templates/email-member-ack.txt)
+# chair send email to board@ asking for acknowledgement of new PMC member
+(templates/email-member-ack.txt)
 # Announce the new committer (template/committerAnnounce.txt)
 
+<a name="NewCommitter-Discussion"></a>
 ## Discussion
 
 We do the vote on the private mailing list to enable a frank discussion.
 
-Start a separate Vote thread for each new person. This makes it much easier to review the mail archives.
+Start a separate Vote thread for each new person. This makes it much easier
+to review the mail archives.
 
-In most cases, we will be inviting people to go straight from developer to PMC member. However, there may be extraordinary cases where we want
-limited work-related commit access. This will be resolved during the vote discussion. 
+In most cases, we will be inviting people to go straight from developer to
+PMC member. However, there may be extraordinary cases where we want
+limited work-related commit access. This will be resolved during the vote
+discussion. 
 
-We need to be sure that they are committed people that we can work with. They will be our peers. We will have already observed that they are
+We need to be sure that they are committed people that we can work with.
+They will be our peers. We will have already observed that they are
 committed to the project and graceful toward users and other developers.
 
-Don&#39;t wait too long before proposing and don&#39;t be too hasty. There is a trade-off and something about timeliness. A point is reached where it
-becomes obvious that we should invite them. This encourages them and keeps them enthusiastic. If we leave it too long, then we risk them becoming disillusioned.
+Don't wait too long before proposing and don't be too hasty. There is a
+trade-off and something about timeliness. A point is reached where it
+becomes obvious that we should invite them. This encourages them and keeps
+them enthusiastic. If we leave it too long, then we risk them becoming
+disillusioned.
 
-On the PMC list we can each say exactly what we feel about each person, with no holds barred. Keep the discussion concise. The praise part can
+On the PMC list we can each say exactly what we feel about each person,
+with no holds barred. Keep the discussion concise. The praise part can
 be done later in public.
 
-See the end of this document for some guidelines to help you to assess a candidate.
+See the end of this document for some guidelines to help you to assess a
+candidate.
 
 Let the Vote thread run for one week.
 
-A positive result is achieved by Consensus Approval i.e. at least 3 +1 votes and no vetoes.
+A positive result is achieved by Consensus Approval i.e. at least 3 +1
+votes and no vetoes.
 
-Any veto must be accompanied by reasoning and be prepared to defend it. Other members can attempt to encourage them to change.
+Any veto must be accompanied by reasoning and be prepared to defend it.
+Other members can attempt to encourage them to change.
 
-New PMC members can be either quiet or active as they choose. If we find that certain people lapse and don&#39;t ever contribute, then we can take steps to retire them.
+New PMC members can be either quiet or active as they choose. If we find
+that certain people lapse and don't ever contribute, then we can take steps
+to retire them.
 
-After a positive result, we give them a chance to decline in private. They can post a reply to the PMC mailing list.
+After a positive result, we give them a chance to decline in private. They
+can post a reply to the PMC mailing list.
 
-After we reach a decision on the PMC list, and after the steps above, we will announce it on the dev list. We can then each follow up with
+After we reach a decision on the PMC list, and after the steps above, we
+will announce it on the dev list. We can then each follow up with
 our praise in public.
 
-Other notes about the process are available on the main [Apache site](http://www.apache.org/dev/pmc.html#newcommitter)
+Other notes about the process are available on the main
+[Apache site](http://www.apache.org/dev/pmc.html#newcommitter)
 
+<a name="NewCommitter-EmailTemplates"></a>
 # Email Templates
 
 <DIV class="code panel" style="border-style: solid;border-width: 1px;"><DIV class="codeHeader panelHeader" style="border-bottom-width: 1px;border-bottom-style: solid;"><B>Committer Vote Template|borderStyle=solid</B></DIV><DIV class="codeContent panelContent">
     This is the email to commence a vote for a new PMC member.
-    We do this on the [PROJECT] Private mailing list, so as to enable
+    We do this on the
+[PROJECT] Private mailing list, so as to enable
     a frank discussion.
     
     ------------------------------------------------------------
     To: private@[PROJECT].a.o
-    Subject: [Vote] new PMC member: Joe Bloggs
+    Subject:
+[Vote] new PMC member: Joe Bloggs
+    
     
-     [ add the reasons behind your nomination here ]
+[ add the reasons behind your nomination here ]
     
     Voting ends one week from today, i.e. midnight UTC on YYYY-MM-DD
-    http://www.timeanddate.com/counters/customcounter.html?year=YYYY&amp;month=MM&amp;day=DD
+    http://www.timeanddate.com/counters/customcounter.html?year=YYYY&month=MM&day=DD
     
     See voting guidelines at
     https://svn.apache.org/repos/private/pmc/forrest/pmc-member-vote.txt
-    (yes, this links to the Apache Forrest Guidelines, we don&#39;t have our own yet)
+    (yes, this links to the Apache Forrest Guidelines, we don't have our own
+yet)
     
     ------------------------------------------------------------
 
@@ -109,10 +156,13 @@ Other notes about the process are availa
     ------------------------------------------------------------
     To: JoeBloggs@foo.net
     Cc: private@[PROJECT].a.o
-    Subject: invitation to become [PROJECT] committer: Joe Bloggs #####
+    Subject: invitation to become
+[PROJECT] committer: Joe Bloggs #####
     
-    Hello #####, the Apache [PROJECT] Project Management Committee
-    would like to invite you to become a [PROJECT] committer and member
+    Hello #####, the Apache
+[PROJECT] Project Management Committee
+    would like to invite you to become a
+[PROJECT] committer and member
     of the PMC. We value your contributions and are aware that
     you are committed to the project.
     
@@ -134,7 +184,8 @@ Other notes about the process are availa
     on the dev@[PROJECT].a.o list after the account is established.
     
     Yours,
-    The Apache [PROJECT] PMC
+    The Apache
+[PROJECT] PMC
     
     ------------------------------------------------------------------------
 
@@ -145,10 +196,12 @@ Other notes about the process are availa
     ------------------------------------------------------------------------
     To: JoeBloggs@foo.net
     Cc: private@[PROJECT].a.o
-    Subject: Re: invitation to become [PROJECT] committer
+    Subject: Re: invitation to become
+[PROJECT] committer
     
     Welcome. Here are the next steps. After that we will make
-    an announcement to the [PROJECT]-dev list.
+    an announcement to the
+[PROJECT]-dev list.
     
     You need to send a Contributor License Agreement to the ASF.
     Normally you would send an Individual CLA. If you also make
@@ -166,8 +219,10 @@ Other notes about the process are availa
     We will arrange for your Apache user account when the CLA has 
     been recorded.
     
-    After that is done, please make followup replies to the [PROJECT]-dev list.
-    We generally discuss everything there and keep this private@[PROJECT].a.o list
+    After that is done, please make followup replies to the
+[PROJECT]-dev list.
+    We generally discuss everything there and keep this private@[PROJECT].a.o
+list
     for occasional matters which must be private.
     
     The developer section of the website describes the roles
@@ -185,7 +240,8 @@ Other notes about the process are availa
     http://forrest.apache.org/guidelines.html
     
     Yours,
-    The Apache [PROJECT] PMC
+    The Apache
+[PROJECT] PMC
     
     ------------------------------------------------------------------------
 
@@ -200,7 +256,7 @@ Other notes about the process are availa
     The PMC needs to monitor iclas.txt to be sure that the CLA
     is properly received before sending this email. See above.
     
-    Don&#39;t forget to add their name/email in the email headers
+    Don't forget to add their name/email in the email headers
     and add the date/Message-Id of the PMC vote summary.
     
     If the new member is already a committer, then just need
@@ -211,11 +267,13 @@ Other notes about the process are availa
     Cc: private@[PROJECT].a.o, ###JoeBloggs@foo.net
     Subject: account request: ###Joe Bloggs
     
-    Full name:                ...
-    Preferred userid:         ... [please provide acceptable alternates!]
+    Full name:		  ...
+    Preferred userid:	  ...
+[please provide acceptable alternates!]
     Forwarding email address: ...
     
-    Requested UNIX groups: [PROJECT]
+    Requested UNIX groups:
+[PROJECT]
     
     The receipt of the ICLA was recorded yesterday.
     
@@ -226,7 +284,8 @@ Other notes about the process are availa
 
 
 <DIV class="code panel" style="border-style: solid;border-width: 1px;"><DIV class="codeHeader panelHeader" style="border-bottom-width: 1px;border-bottom-style: solid;"><B>Committer Announce Template|borderStyle=solid</B></DIV><DIV class="codeContent panelContent">
-    This is the email to announce to [PROJECT]-dev after the
+    This is the email to announce to
+[PROJECT]-dev after the
     followup acceptance.
     
     Replace the Joe Blogs in the subject, the ### in the body.
@@ -235,7 +294,8 @@ Other notes about the process are availa
     To: dev@[PROJECT].a.o
     Subject: new committer and PMC member: ###Joe Bloggs
     
-    The Project Management Committee (PMC) for Apache [PROJECT]
+    The Project Management Committee (PMC) for Apache
+[PROJECT]
     has asked #### ####### to become a committer and
     member of the PMC, and we are pleased to announce that
     they have accepted.
@@ -251,29 +311,36 @@ Other notes about the process are availa
 
 <DIV class="code panel" style="border-style: solid;border-width: 1px;"><DIV class="codeHeader panelHeader" style="border-bottom-width: 1px;border-bottom-style: solid;"><B>Board Template|borderStyle=solid</B></DIV><DIV class="codeContent panelContent">
     This is the email to end a vote for a new PMC member.
-    We do this on the [PROJECT] Private mailing list as that 
+    We do this on the
+[PROJECT] Private mailing list as that 
     is where the vote is held..
     
     ------------------------------------------------------------
     To: private@[PROJECT].a.o
-    Subject: [RESULT] [Vote] new PMC member: Joe Bloggs
+    Subject:
+[RESULT]
+[Vote] new PMC member: Joe Bloggs
     
     The vote has now closed. The results are:
     
     Binding Votes:
     
-    +1 [TOTAL BINDING +1 VOTES]
-     0 [TOTAL BINDING +0/-0 VOTES]
-    -1 [TOTAL BINDING -1 VOTES]
+    +1
+[TOTAL BINDING +1 VOTES]
+     0
+[TOTAL BINDING +0/-0 VOTES]
+    -1
+[TOTAL BINDING -1 VOTES]
     
     
     [If three binding +1 and no binding -1]
     
-    The vote passes, we now need lazy consensus approval from the IPMC. This email
+    The vote passes, we now need lazy consensus approval from the IPMC. This
+email
     calls for that consensus.
     
     Consensus period ends 72 hours from now, i.e. XYZ UTC on YYYY-MM-DD
-    http://www.timeanddate.com/counters/customcounter.html?year=YYYY&amp;month=MM&amp;day=DD&amp;hour=0&amp;min=0&amp;sec=0&amp;p0=0
+    http://www.timeanddate.com/counters/customcounter.html?year=YYYY&month=MM&day=DD&hour=0&min=0&sec=0&p0=0
     
     ------------------------------------------------------------
 
@@ -286,38 +353,39 @@ Other notes about the process are availa
     Subject: account request: ###Joe Bloggs
     
     ####, as you know, the ASF Infrastructure has set up your
-    committer account as the username &#39;####&#39;.
+    committer account as the username '####'.
     
     Please follow the instructions to set up your SSH,
     svn password, svn configuration, mail forwarding, etc.
     http://www.apache.org/dev/#committers
     
-    Please subscribe to the [PROJECT] Project Management 
+    Please subscribe to the
+[PROJECT] Project Management 
     Committee mailing list private@[PROJECT].apache.org.
     
     You have commit access to specific sections of the
     ASF repository, as follows:
     
-      [PROJECT] has various resources at:
+     
+[PROJECT] has various resources at:
       https://svn.apache.org/repos/asf/[PROJECT]
     
-      The general &quot;committers&quot; at:
+      The general "committers" at:
       https://svn.apache.org/repos/private/committers
     
     As per the documentation mentioned above, you need
-    to &#39;svn switch&quot; previous checkouts to now use https.
+    to 'svn switch" previous checkouts to now use https.
     
     If you have any questions during this phase, then please
     see the following resources:
     
-    Apache developer&#39;s pages: http://www.apache.org/dev/
+    Apache developer's pages: http://www.apache.org/dev/
     
-    Naturally, if you don&#39;t understand anything be sure to 
-    ask us on the [PROJECT] dev mailing list. Documentation is 
+    Naturally, if you don't understand anything be sure to 
+    ask us on the
+[PROJECT] dev mailing list. Documentation is 
     maintained by volunteers and hence can be out-of-date and 
     incomplete.
     
     One of us will announce you to the dev list soon.
 
-
-        
\ No newline at end of file

Added: comdev/site/trunk/content/use-the-comdev-issue-tracker-for-gsoc-tasks.mdtext
URL: http://svn.apache.org/viewvc/comdev/site/trunk/content/use-the-comdev-issue-tracker-for-gsoc-tasks.mdtext?rev=1037091&view=auto
==============================================================================
--- comdev/site/trunk/content/use-the-comdev-issue-tracker-for-gsoc-tasks.mdtext (added)
+++ comdev/site/trunk/content/use-the-comdev-issue-tracker-for-gsoc-tasks.mdtext Sat Nov 20 00:14:10 2010
@@ -0,0 +1,19 @@
+Title: use the Comdev Issue Tracker For GSoC Tasks
+If you project does not use the ASFs JIRA for issue tracking you can use
+the Community Development project to record your GSoC tasks. 
+
+* Add tasks to the
+[Comdev project](https://issues.apache.org/jira/browse/COMDEV)
+* Ensure you add the labels "*gsoc*" and "*mentor*"
+* Ensure your title has "PROJECT_NAME:" at the start (you'll see why in a
+moment)
+* Your issues will then appear in the
+[list of
+projects|https://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12314021]
+* To create a list of just your projects make a copy of the filter at the
+above URL, narrow down to the comdev project and filter for "PROJECT_NAME:"
+(e.g.
+[Subversion
+tasks|https://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12314115])
+
+You can then link to this from your own site and access XML, RSS feeds.



Mime
View raw message