community-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From n...@apache.org
Subject svn commit: r1035965 - in /comdev/site/trunk: content/ lib/ templates/
Date Wed, 17 Nov 2010 09:59:04 GMT
Author: nick
Date: Wed Nov 17 09:59:04 2010
New Revision: 1035965

URL: http://svn.apache.org/viewvc?rev=1035965&view=rev
Log:
Use export_site.pl to do a first pass of converting the site. Some tweaking is still required though

Added:
    comdev/site/trunk/content/boardreport.mdtext
    comdev/site/trunk/content/comdevboardreports.mdtext
    comdev/site/trunk/content/comdevboardresolution.mdtext
    comdev/site/trunk/content/contactpoints.mdtext
    comdev/site/trunk/content/gsoc.mdtext
    comdev/site/trunk/content/index.mdtext
    comdev/site/trunk/content/mentoringprogramme.mdtext
    comdev/site/trunk/content/newbiefaq.mdtext
    comdev/site/trunk/content/newcommitter.mdtext
    comdev/site/trunk/templates/standard_markdown.html
Modified:
    comdev/site/trunk/content/localmentors.mdtext
    comdev/site/trunk/lib/path.pm
    comdev/site/trunk/templates/standard.html

Added: comdev/site/trunk/content/boardreport.mdtext
URL: http://svn.apache.org/viewvc/comdev/site/trunk/content/boardreport.mdtext?rev=1035965&view=auto
==============================================================================
--- comdev/site/trunk/content/boardreport.mdtext (added)
+++ comdev/site/trunk/content/boardreport.mdtext Wed Nov 17 09:59:04 2010
@@ -0,0 +1,55 @@
+Title: BoardReport
+All projects report to the board once a quarter. The ASF Board meets on the third Wednesday of every month and thus projects due 
+to report need to have their reports ready no later than the second Wednesday of that month. This allows the board to pre-approve 
+reports where possible, thus making for a much shorter board meeting.
+
+Reports need not be exhaustive, unless you are asking for assistance. Neither do they need any technical information since the 
+board are only interested in project health. At the end of this page there is a template for board reports. First we'll describe 
+how some projects manage their board report during the quarter, however, like most things in the ASF projects are free to manage 
+this process in any way they desire.
+
+ * Create a template of the report in project SVN or Wiki space (see below for draft template)
+ * Record relevant details on the report as they occur
+ * Review objectives for the community and act upon them
+ * Recieve reminder from "marvin" that the board report is due (usually on the first of the month)
+ * Update board report ready for submission
+ * Post mail to developer list asking for a review of the draft report
+ * Incorporate feedback from community
+ * PMC chair submits board report via board.at.apache.org with subject of "\[REPORT\](report\.html) project name" (copy to project private or dev list as appropriate)
+
+<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 Report Template|borderStyle=solid</B></DIV><DIV class="codeContent panelContent">
+    Status report for the Apache FOO project - MONTH YEAR
+    
+    Project Status
+    --------------
+    
+    A sentence or two describing the current status of the project. Most importantly, highlight any issues that require board 
+    attention. This is the projects opportunity to ask for assistance from the board should there be any sticky issues that need 
+    addressing.
+    
+    Community
+    ---------
+    
+    A slightly more detailed look at the project community. It should still be brief, issues to think about include:
+    
+    * Is the project community active? 
+    * Is the user community growing/shrinking? 
+    * Are there any legal, infrastructure, cross-project or personal issues that need to be addressed?
+    * Are issues on the user/developer list being addressed?
+    * Have any new committers been voted in? Any changes in the PMC?
+    
+    Community Objectives
+    --------------------
+    
+    This section indicates what the community considers to be its highest priorities for the coming quarter. This is only intended 
+    as a record of likley actions to address any issues the community may have. The project should not feel limited to (or by) 
+    these objectives.
+    
+    * What are the projects main plans and expectations for the community in the next period?
+    
+    Releases
+    --------
+    
+    Have there been any releases from the project in the last quarter? If not when is the next one likely to be made?
+
+        
\ No newline at end of file

Added: comdev/site/trunk/content/comdevboardreports.mdtext
URL: http://svn.apache.org/viewvc/comdev/site/trunk/content/comdevboardreports.mdtext?rev=1035965&view=auto
==============================================================================
--- comdev/site/trunk/content/comdevboardreports.mdtext (added)
+++ comdev/site/trunk/content/comdevboardreports.mdtext Wed Nov 17 09:59:04 2010
@@ -0,0 +1,217 @@
+Title: ComDevBoardReports
+This page contains records of the Apache Community Development Project board reports. The official record of these reports is the minutes of the appropriate board meeting, they are provided here for convenience.
+
+# Draft report for next meeting
+
+The following report is *incomplete* and *draft* only. It is being prepared for the next submission to the board. Submitted reports can be found further down the page.
+
+{panel:title=DRAFT February 2011|borderStyle=solid|titleBGColor=#F7D6C1|bgColor=#FFFFCE}
+
+Status report for the Apache Community Development Project
+
+Project Status
+--------------
+
+The Community Development is progressing well, although a little more slowly than some whould have hoped.
+
+No issues require board attention at this time.
+
+Community
+---------
+
+
+
+Objectives for next period
+--------------------------
+
+
+{panel}
+
+# Submitted Reports
+
+{panel:title=November 2010|borderStyle=solid|titleBGColor=#F7D6C1|bgColor=#FFFFCE}
+
+Status report for the Apache Community Development Project
+
+Project Status
+--------------
+
+The Community Development is progressing well, although a little more slowly than some whould have hoped.
+
+The planned mentoring project has still not been formally launched. Largely due to the loss of the labels module in JIRA which was previously used by projects to indicate issues appropriate for mentoring. An alernative will be put into place very soon.
+
+Work on a project to provide hosting for Apache related software projects is progressing. Legal documents have all been signed, draft usage guidelines and a FAQ are available and PMCs have been ocntacted to reserve projects names.
+
+We have taken ownership of party@ mailing list (no changes in usage are proposed)
+
+Google Summer of Code completed - thanks to all involved. It is noticable that once again we have failed to generate any press (we never produced a press release for press@)
+
+We applied for the Google Code-In (Google&#39;s contest to introduce pre-university students to the many kinds of contributions that make open source software development possible) but were, unfortunately, unsuccessful.
+
+Ross Gardler has spoken at a reasonably large number of events around Europe addressing two key themes - The Apache Way and Innovation at the ASF.
+
+No issues require board attention at this time.
+
+Community
+---------
+
+An increasing number of volunteers are becoming engaged with Community Development PMC and contact from external participants is increasing (although still low).
+
+
+Objectives for next period
+--------------------------
+
+- Gain support from at least 5 PMCs for the mentoring programme
+- Formally launch mentoring programme
+- Launch hosting facilities for apache related projects
+
+{panel}
+
+{panel:title=August 2010|borderStyle=solid|titleBGColor=#F7D6C1|bgColor=#FFFFCE}
+
+Status report for the Apache Community Development Project
+
+Project Status
+--------------
+
+The Community Development Project is starting to ramp up again after the Google Summer of Code efforts. We have merged the 
+women@a.o list into the dev@community.a.o and are commencing work on rolling out the mentoring program.
+
+No issues require board attention at this time.
+
+Community
+---------
+
+The women@a.o mailing list has been closed and an autoresponder inviting people to post to dev@community.a.o has been set up. The vote to merge the women@a.o list was passed unaminously. One, previously unknown, community member voted -1 (non-binding). However, the owners of the women@.a.o list reassured the ComDev PMC that the list had been largely unsuccesful in meeting the  defined objectives and welcomed the opportunity to work with the ComDev PMC in ensuring that the successes of women in the ASF are duly recognised. 
+
+The local mentors program and local speakers program both continue to grow. We now have 53 local mentors, and 27 local speakers. If discussions on them on foundation-wide lists is anything to go by, they continue to be of use!
+
+Interest is growing in the mentoring programme with a number of enquiries to the development list. Ross Gardler reports that there will be between 10 and 40 students approaching the ASF for mentoring as part of their formal education in September. The draft process is already [defined](http://community.apache.org/mentoringprogramme.html) and will be refined during August in consulation with interested PMCs.
+
+There was one appeal from a GSoC student that failed in the mid-term evaluation. This was examined by both Google and the ASF admins. It was felt the mentors decision was fair and that our selection process was not at fault. A minor tweak relating to the communication of our expectations to the students has been implemented. Full details can be reviewed at http://markmail.org/thread/dsn6v2dagrm5nv7q
+
+Objectives for next period
+--------------------------
+
+* Gain support from at least 5 PMCs for the mentoring programme
+* Launch the mentoring programme in September (no press at this stage)
+{panel}
+
+{panel:title=June 2010|borderStyle=solid|titleBGColor=#F7D6C1|bgColor=#FFFFCE}
+Status report for the Apache Community Development Project
+
+No issues require board attention at this time.
+
+Apologies for not submitting last month.
+
+Website
+-------
+
+Documentation about mentoring has been moved from the wiki to the comdev
+website
+
+A beta site for finding local mentors and speakers has been set up at
+http://community.zones.apache.org/ This is reasonably well populated via
+members@ and we expect to start pushing it to the wider community@ soon.
+
+Google Summer of Code
+---------------------
+
+44 Students accepted, this will generate income of $22,000
+
+For the first time there were no major complaints about the selection
+process.
+
+Student work is underway.
+
+Mentoring Programme
+-------------------
+
+We had planned to roll out the mentoring programme after the GSoC
+selection process. However, this has not yet happened. Documentation is in
+place and a pilot is being run with a single student. However, we have not
+yet rolled it out across the ASF.
+
+A lack of volunteer time is the real block here, this is expected to be
+resolved in coming months (a day job project for one of the ComDev team
+relating to this activity commences in July)
+
+The Apache Way
+--------------
+
+Prompted by various discussions on members@ we started a community dev
+blog (http://blogs.apache.org/comdev/)
+
+This will be used to post useful pointers to existing resources and
+expertise.
+
+We are considering which activities discussed in the members@ threads can
+and should be implemented by comdev
+{panel}
+
+{panel:title=February 2010|borderStyle=solid|titleBGColor=#F7D6C1|bgColor=#FFFFCE}
+Status report for the Apache Community Development Project
+
+The community development project aims to help newcomers to The Apache
+Software Foundation take their first steps on their way to being a part of
+our community.
+
+Issues for board attention
+--------------------------
+
+GSoC invoicing process
+
+The ComDev PMC would like the board to evaluate the process for making
+claims for GSoC payments from Google. For the board&#39;s convenience, the
+process is currently:
+
+a) GSoC admin informs Google of total amount owing
+b) Google issue a PO
+c) GSoC admin liaises with ASF treasurer
+d) ASF issues an Invoice
+e) Google pays invoice
+
+At present the processes seems to get stuck at c). The GSoC admin is unaware
+of the issuing of an invoice for 2009 and we suspect other years may have
+been missed as well.
+
+This not only impacts ASF income but increases our costs since travel to the
+mentor summit is reimbursed through the same invoice.
+
+Main items to report
+--------------------
+
+- addition of Isabel Drost, Nick Birch, Noel J. Bergman and Kathey Marsden
+  to the Community Development PMC
+
+- documentation of proposed mentoring programme [1](1.html)
+
+- commencement of our first mentored participant [2](2.html)
+
+- two press interviews in response to word of mouth discovery of the project
+
+- GSoC has been officially announced and will be run this year with Noirin
+  Shirley as admin, Ross Gardler and Luciano Resende as co-admins
+
+- creation of a &quot;people near you&quot; webapp populated with people available for
+  presenting or meeting those interested in the ASF - this is not yet public
+  as we are awaiting the creation of a zone on which to host it
+
+Main items for next period
+--------------------------
+
+- Move documentation of GSoC from wiki.apache.org to community.apache.org
+
+- Launch of the &quot;people near you&quot; webapp
+
+- Launch of the ASF GSoC engagement
+
+- Preparation for the official launch of the ASF mentoring programme (which
+  will occur after GSoC has commenced)
+
+  [1](1.html) http://community.apache.org/mentoringprogramme.html
+  [2](2.html) https://issues.apache.org/jira/browse/COMDEV-11
+{panel}
+
+
+        
\ No newline at end of file

Added: comdev/site/trunk/content/comdevboardresolution.mdtext
URL: http://svn.apache.org/viewvc/comdev/site/trunk/content/comdevboardresolution.mdtext?rev=1035965&view=auto
==============================================================================
--- comdev/site/trunk/content/comdevboardresolution.mdtext (added)
+++ comdev/site/trunk/content/comdevboardresolution.mdtext Wed Nov 17 09:59:04 2010
@@ -0,0 +1,61 @@
+Title: ComDevBoardResolution
+The Apache Community Development Project was created in November 2009.
+
+
+<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 Resolution Creating the Apache Community Development Project|borderStyle=solid</B></DIV><DIV class="codeContent panelContent">
+           Establish the Apache Community Development Project
+    
+           WHEREAS, the Board of Directors deems it to be in the best
+           interests of the Foundation and consistent with the
+           Foundation&#39;s purpose to establish a Project Management
+           Committee charged with coordinating community development
+           efforts.
+    
+           NOW, THEREFORE, BE IT RESOLVED, that a Project Management
+           Committee (PMC), to be known as the &quot;Apache Community
+           Development Project&quot;, be and hereby is established
+           pursuant to Bylaws of the Foundation; and be it further
+    
+           RESOLVED, that the Apache Community Development Project
+           be and hereby is responsible for helping people become
+           involved with Apache projects; and be it further
+    
+           RESOLVED, that the office of Vice President, Apache Community
+           Development Project, be and hereby is created, the person
+           holding such office to serve at the direction of the Board
+           of Directors as the chair of the Community Development PMC,
+           and to have primary responsibility for management of the
+           projects within the scope of the Apache Community Development
+           project; and be it further
+    
+           RESOLVED, that the persons listed immediately below be and
+           hereby are appointed to serve as the initial members of the
+           Apache Community Development Project PMC:
+    
+            * Ross Gardler &lt;rgardler@apache.org&gt;
+            * Luciano Resende &lt;lresende@apache.org&gt;
+            * Santiago Gala &lt;sgala@apache.org&gt;
+            * Bertrand Delacretaz &lt;bdelacretaz@apache.org&gt;
+            * Ted Dunning &lt;tdunning@apache.org&gt;
+            * Noirin Shirley &lt;noirin@apache.org&gt;
+    
+           NOW, THEREFORE, BE IT FURTHER RESOLVED, that Ross Gardler
+           be appointed to the office of Vice President, Apache Community
+           Development Project, to serve in accordance with and
+           subject to the direction of the Board of Directors and
+           the Bylaws of the Foundation until death, resignation,
+           retirement, removal or disqualification, or until a successor
+           is appointed; and be it further
+    
+           RESOLVED, that the initial Apache Community Development PMC
+           be and hereby is tasked with the creation of a set of bylaws
+           intended to encourage open participation in the Apache
+           Community Development Project.
+    
+           Special order 3A, establish the Apache Community Development Project,
+           was approved by Unanimous Vote of the directors present.
+    
+           Furthermore, the board requested that this PMC take over the stewardship
+           of the community@ and women@ mailing lists.
+
+        
\ No newline at end of file

Added: comdev/site/trunk/content/contactpoints.mdtext
URL: http://svn.apache.org/viewvc/comdev/site/trunk/content/contactpoints.mdtext?rev=1035965&view=auto
==============================================================================
--- comdev/site/trunk/content/contactpoints.mdtext (added)
+++ comdev/site/trunk/content/contactpoints.mdtext Wed Nov 17 09:59:04 2010
@@ -0,0 +1,20 @@
+Title: ContactPoints
+If you need to contact the ASF about an official matter you should use the appropriate address below. These are publicly shareable email addresses that point to privately archived lists.  
+
+### Trademarks
+
+Any issues regarding trademarks, specific project names, or branding of the ASF and it&#39;s projects should go to trademarks@apache.org
+
+### Publicity and Marketing
+Any issues dealing with publicity, marketing, or any inquires from the press or analysts should go to press@apache.org.
+
+### Fundraising and Sponsorship
+Any issues dealing with fundraising, sponsorships, donations, or related finances should be sent to fundraising@apache.org
+
+### Legal
+Specific legal questions that may need to be private, and require a response from the ASF&#39;s legal counsel to to legal-internal@apache.org
+
+### Other
+
+For more information on these and other foundation lists see the [Mailing Lists](http://www.apache.org/foundation/mailinglists.html) page.
+        
\ No newline at end of file

Added: comdev/site/trunk/content/gsoc.mdtext
URL: http://svn.apache.org/viewvc/comdev/site/trunk/content/gsoc.mdtext?rev=1035965&view=auto
==============================================================================
--- comdev/site/trunk/content/gsoc.mdtext (added)
+++ comdev/site/trunk/content/gsoc.mdtext Wed Nov 17 09:59:04 2010
@@ -0,0 +1,90 @@
+Title: GSoC
+Google is sponsoring the [2010 Summer of Code](http://socghop.appspot.com/), the [The Apache Software Foundation|http://www.apache.org/] (ASF) is planning to participate again this year (mentoring organisations have not yet been accepted). This page is your entry point to the ASF GSoC programme.
+
+# Students: read this
+
+* Learn [about GSoC](http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#about_gsoc)
+* Decide if you are [eligible](http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#eligibility) for GSoC?
+* Review [Advice for Students](http://code.google.com/p/google-summer-of-code/wiki/AdviceforStudents) to make sure you really want to apply to GSoC.
+* Watch Philip Johnson&#39;s [GSoC video presentation](http://www.youtube.com/watch?v=vBRRR0BQyz0) for students.
+* Examine the list of [available ASF GSoC projects](https://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&amp;requestId=12314021)
+** Note that you can search the issue tracker for GSoC projects by filtering using the &quot;gsoc&quot; label, this allows you to narrow down the list to the projects you are interested in.
+
+### Applying for GSoC
+
+Student applications start on March 29th, 2010. However we encourage you to discuss you application with the project community before this date.
+
+In order to apply we ask that you create a list of deliverables, quantifiable results for the Apache community, a detailed description / design document, an approach, an approximate schedule and something of a background text. We also need you to let us know what other commitments you have for the period of GSoC, for example, do you have any exams or a part time job? In other words - sell yourselves, as if this was an actual job. 
+
+In drawing up your proposal you should work with your chosen projects community. One of our evaluation criteria is that you have already engaged with the community to ensure that you understand the needs of the project and the commitment you need to make to your mentors.
+
+Once open applications are made through the [GSoC site](http://socghop.appspot.com/)
+
+## Contacting the ASF
+
+The ASF is not just one project, it is a federation of projects, see the lists at http://apache.org/ and http://incubator.apache.org/. Each of our projects has its own community of users, contributors and committers. GSoC students will usually be interacting with just one of these communities. 
+
+Each of the proposed subjects (link to be provided if we are confirmed as a mentoring organisation) applies to a single ASF project. You will need to engage with that project community.
+
+# Prospective ASF mentors: read this
+
+We are looking for as many interesting projects as we can come up with. For more info about mentoring, please read our [guide to being a mentor](guide to being a mentor.html).
+
+Prospective mentors should join the code-awards@apache.org mailng list, this is where mentor specific issues are dealt with, and where announcements will be made. If you want to track the programme administration you should subscribe to dev@community.apache.org.
+
+Once the ASF is confirmed as a mentoring organisation mentors must register with the GSoC webapp, and request to become a mentor for the ASF organization. Make sure that the email address you use for that (it&#39;s often your @gmail.com address by default) is &#39;&#39;&#39;registered in committers/MailAlias.txt&#39;&#39;&#39; so that we can match it to your ASF account. You should also register your &#39;&#39;&#39;GSoC Link Id to committers/GSoCLinkId.txt&#39;&#39;&#39;.
+
+All ASF projects are invited to submit their ideas to their issue tracker, please be sure to add the labels &quot;gsoc&quot; and &quot;mentor&quot; so that we can automatically include them in our list of subjects. If your project does not use JIRA please contact dev@community.apache.org.  
+
+# ASF GSoC Timeline
+
+Below is a timeline of events for The Apache Software Foundations involvement in GSoC. Unless otherwise stated deadlines are 11:59 UTC on the date indicated.
+
+## Student Application and Selection
+
+||Date||Activity||
+|February 8|Program announced. Life is good.|
+|March 18-29|Would-be student participants discuss application ideas with mentoring organizations.|
+|March 29 19:00 UTC|Student application period opens.|
+|April 9 19:00 UTC|Student application deadline.|
+|April 10th|internal [ranking](mentee ranking process.html) starts|
+|April 13th|All mentors must be signed up and must have indicated students they want to be considered as mentees (see the pre-selection phase of the [ranking process](mentee ranking process.html) for details)|
+|April 17th|All mentors must have fully evaluated pre-selected student proposals (see the selectoin phase of the  [ranking process](mentee ranking process.html) for details)|
+|April 21st|Administrators must have completed the internal ranking process (see the re-evaluation phase of the [ranking](mentee ranking process.html) process)|
+|TBD|IRC admin meeting to resolve any outstanding duplicate accepted students - timing TBD, will be announced well in advance|
+|April 26 19:00 UTC|Accepted student proposals announced on the Google Summer of Code 2010 site.
+|circa. April 26th|ASF press release|
+
+## GSoc is underway
+
+|Community Bonding Period|Students get to know mentors, read documentation, get up to speed to begin working on their projects.|
+|May 23rd|ASF press release|
+|May 24|Students begin coding for their GSoC projects;
+Google begins issuing initial student payments provided tax forms are on file and students are in good standing with their communities.|
+|Interim Period:|Mentors give students a helping hand and guidance on their projects|
+|July 12 19:00 UTC|Mentors and students can begin submitting mid-term evaluations.|
+|July 16 19:00 UTC|Mid-term evaluations deadline;
+Google begins issuing mid-term student payments provided passing student survey is on file.|
+|Interim Period|Mentors give students a helping hand and guidance on their projects.|
+|August 9|Suggested &#39;pencils down&#39; date. Take a week to scrub code, write tests, improve documentation, etc.|
+|August 16 19:00 UTC|Firm &#39;pencils down&#39; date. Mentors, students and organization administrators can begin submitting final evaluations to Google.|
+|August 20 19:00 UTC|Final evaluation deadline
+Google begins issuing student and mentoring organization payments provided forms and evaluations are on file.|
+
+## Wind down
+
+|August 23|Final results of GSoC 2010 announced|
+|August 30|Students can begin submitting required code samples to Google|
+|circa. September 3rd|ASF press release|
+|October (date TBD)|Mentor Summit at Google: Representatives from each successfully participating organization are invited to Google to greet, collaborate and code. Our mission for the weekend: make the program even better, have fun and make new friends.|
+
+
+# Useful Links
+
+ * [Summer of Code home](http://socghop.appspot.com/)
+ * [2009 FAQs](http://code.google.com/opensource/gsoc/2009/faqs.html)
+ * [GS0C discussion list](http://groups.google.com/group/google-summer-of-code-discuss)
+ * [Python notes on expectations](http://wiki.python.org/moin/SummerOfCode/Expectations)
+ * #gsoc on Freenode
+
+        
\ No newline at end of file

Added: comdev/site/trunk/content/index.mdtext
URL: http://svn.apache.org/viewvc/comdev/site/trunk/content/index.mdtext?rev=1035965&view=auto
==============================================================================
--- comdev/site/trunk/content/index.mdtext (added)
+++ comdev/site/trunk/content/index.mdtext Wed Nov 17 09:59:04 2010
@@ -0,0 +1,40 @@
+Title: Index
+Welcome to the Community Development project site. Our aim here is to *help newcomers* to The Apache Software Foundation take their first steps on their way to being a *part of our community*. We do not focus on any specific projects here, we focus on the common structures and processes you will find in the majority of ASF projects. Our goal is to help you *understand how the ASF works* and give you the confidence to participate more directly.
+
+# Seeking assistance
+
+The first rule of engaging with an open source project, not just those here in the ASF, is to _research first, ask questions second_. Therefore, please review the materials we have on this site (which admittedly are thin on the ground at this early stage). If you don&#39;t find what you need then ask for assistance on our mailing list at mailto:dev@community.apache.org (first subscribe by sending a mail to mailto:dev-subscribe@community.apache.org).
+
+If you need to contact the ASF for to address an official matter you&#39;ll find a list of useful addresses in our [Contact Points](contactpoints.html) page.
+
+## Starting points
+
+This project is at a very early stage, other than the mailing list mentioned above we don&#39;t have many starting points for you, but here&#39;s a list of what we are creating - please have a look at what there is and feel free to ask questions so we know what parts to flesh out first.
+
+* [Google Summer of Code](gsoc.html)
+* [Mentoring Programme](mentoringprogramme.html)
+* [Mentoring in formal education](mentorprogrammeformaleducation.html)
+* [Local Mentors Programme](localmentors.html)
+* [Being a Mentor](guide to being a mentor.html)
+* [Newbie FAQ](newbiefaq.html)
+
+# First Contributions
+
+The second rule of engaging with open source projects, especially those in the ASF, is that *the more you give the more you get*. Most people assume that newcomers are unable to contribute, however, you will be surprised at how much you can help. Since we aim to be a place for newcomers to learn about the ASF as a whole and you are (probably) a newcomer *any feedback you can give or unanswered questions you can ask* will help us improve what we offer to those who come afterwards. 
+
+Feedback can be provided via the mailing list mailto:dev@community.apache.org (subscribe first with an email to mailto:dev-subscribe@community.apache.org)
+
+# Assisting with project management
+
+There are many visible contributions of value in an Apache projects (documentation, testing, coding user support, design etc.), but there are also plenty of &quot;back office&quot; tasks that are necessary to maintain a healthy project. This section describes some of the activities that you can help with. In most cases you will need to be a committer to carry out these activities, although non-committers can often act in supporting roles.
+
+ * [Board Reports](boardreport.html)
+ * [New Committer Handling](newcommitter.html)
+
+# Managing the Community Development project
+
+This sections simply links to documents important to the Apache Community Development project.
+
+ * [Original board resolution](comdevboardresolution.html) creating the ComDev project
+ * [Board Reports](comdevboardreports.html)
+        
\ No newline at end of file

Modified: comdev/site/trunk/content/localmentors.mdtext
URL: http://svn.apache.org/viewvc/comdev/site/trunk/content/localmentors.mdtext?rev=1035965&r1=1035964&r2=1035965&view=diff
==============================================================================
--- comdev/site/trunk/content/localmentors.mdtext (original)
+++ comdev/site/trunk/content/localmentors.mdtext Wed Nov 17 09:59:04 2010
@@ -3,20 +3,20 @@ The Local Mentors project aims to allow 
 
 # Why?
 
-When you're getting involved in a new open source project, it can be a little daunting. You engage in the mailing lists with people from all around the world. You solve bugs with people in different time zones. You develop patches with people from different languages and cultures. Perhaps you have a mentor ([Formal](mentoringprogramme.html) or informal) from your project, but the chances area, they're a thousand miles away.
+When you&#39;re getting involved in a new open source project, it can be a little daunting. You engage in the mailing lists with people from all around the world. You solve bugs with people in different time zones. You develop patches with people from different languages and cultures. Perhaps you have a mentor ([Formal](mentoringprogramme.html) or informal) from your project, but the chances area, they&#39;re a thousand miles away.
 
 This global reach is some of where open source derives its power from. However, for many people approaching it for the first time, it can present an odd challenge.
 
-No matter which project you're involved in, there may well be some things that you're finding a little different or difficult that are specific to where you are. Perhaps you'd like some tips on making the best use of the time zone difference between yourself and a couple of the main developers on the project? Perhaps English isn't your first language, and you'd like to double check some points of technical language that are leading to confusion? Perhaps you'd like to chat over some of the cultural differences that you've spotted? Or maybe you've just spent a lot of time communicating about open source electronically, and you'd really like to see a real face for once\!
+No matter which project you&#39;re involved in, there may well be some things that you&#39;re finding a little different or difficult that are specific to where you are. Perhaps you&#39;d like some tips on making the best use of the time zone difference between yourself and a couple of the main developers on the project? Perhaps English isn&#39;t your first language, and you&#39;d like to double check some points of technical language that are leading to confusion? Perhaps you&#39;d like to chat over some of the cultural differences that you&#39;ve spotted? Or maybe you&#39;ve just spent a lot of time communicating about open source electronically, and you&#39;d really like to see a real face for once\!
 
-That's where the local mentor project steps in. Find an existing Apache committer near you, head to a cafe or pub, grab a coffee or a beer, and have a chat. They probably won't know your project, but they'll hopefully know the rest\!
+That&#39;s where the local mentor project steps in. Find an existing Apache committer near you, head to a cafe or pub, grab a coffee or a beer, and have a chat. They probably won&#39;t know your project, but they&#39;ll hopefully know the rest\!
 
 
-# If you're looking for a local mentor
+# If you&#39;re looking for a local mentor
 
-First up, make sure a local mentor's the right thing for you. The Local Mentoring project has different aims to the [Formal Mentoring Program](mentoringprogramme.html). If you're after someone who knows your project, or someone who's available over a prolonged period of time, then the [Formal Mentoring Program|MentoringProgramme] is a better fit.
+First up, make sure a local mentor&#39;s the right thing for you. The Local Mentoring project has different aims to the [Formal Mentoring Program](mentoringprogramme.html). If you&#39;re after someone who knows your project, or someone who&#39;s available over a prolonged period of time, then the [Formal Mentoring Program|MentoringProgramme] is a better fit.
 
-However, if you'd like to meet up with someone to put a friendly face on the ASF, and discuss open source and Apache from where you are, hopefully in your own language, then this might be the right thing for you.
+However, if you&#39;d like to meet up with someone to put a friendly face on the ASF, and discuss open source and Apache from where you are, hopefully in your own language, then this might be the right thing for you.
 
   
   
@@ -26,37 +26,38 @@ To find a local mentor, please visit [ht
   
   
 
-Using [http://community.zones.apache.org/](http://community.zones.apache.org/), you simply need to enter your location, and search for Apache committers willing to act as local mentors near you. Drop them an email to introduce yourself. However, please remember that they will be giving up their time to meet and help you, so you'll almost certainly need to work to their location and availability\!
+Using [http://community.zones.apache.org/](http://community.zones.apache.org/), you simply need to enter your location, and search for Apache committers willing to act as local mentors near you. Drop them an email to introduce yourself. However, please remember that they will be giving up their time to meet and help you, so you&#39;ll almost certainly need to work to their location and availability\!
 
-While Apache has committers in almost all corners of the world, not all of them are currently part of the local mentoring program. As such, you might discover that you can't find anyone near you. In that case, either look for people near where you might visit in the future, or failing that, see if any other open source foundations or local groups have anything near you.
+While Apache has committers in almost all corners of the world, not all of them are currently part of the local mentoring program. As such, you might discover that you can&#39;t find anyone near you. In that case, either look for people near where you might visit in the future, or failing that, see if any other open source foundations or local groups have anything near you.
 
 # How existing Apache Committers can get involved
 
-If you think you could spare the odd hour everyone once in a while, to sit down over a beer or a coffee and chat about Open Source and the Apache Way, then we'd love you to get involved\! You're not signing up to a long-term mentoring relationship (see the [Formal Mentoring Program](mentoringprogramme.html) if you're interested in that though) Just every so often, helping out someone who lives near you.
+If you think you could spare the odd hour everyone once in a while, to sit down over a beer or a coffee and chat about Open Source and the Apache Way, then we&#39;d love you to get involved\! You&#39;re not signing up to a long-term mentoring relationship (see the [Formal Mentoring Program](mentoringprogramme.html) if you&#39;re interested in that though) Just every so often, helping out someone who lives near you.
 
-Firstly, you'll need a FOAF entry on people.apache.org. Take a look at [http://people.apache.org/foaf/](http://people.apache.org/foaf/) for instructions on setting this up if you haven't already done so. Next, ensure that you have listed your location - we need that to be able to let people search for you.
+Firstly, you&#39;ll need a FOAF entry on people.apache.org. Take a look at [http://people.apache.org/foaf/](http://people.apache.org/foaf/) for instructions on setting this up if you haven&#39;t already done so. Next, ensure that you have listed your location - we need that to be able to let people search for you.
 
-Now, if you haven't already done so, checkout the committers directory from svn:
+Now, if you haven&#39;t already done so, checkout the committers directory from svn:
 
     svn co https://svn.apache.org/repos/private/committers/
 
 
 Edit *local-outreach/CommunityDevelopment.rdf* and add yourself in as a helper. If your FOAF file is in svn and showing up on people.apache.org, add in:
 
-    <helper>
-    <foaf:Person rdf:resource="urn:org:apache:[your username].rdf" />
-    </helper>
+     &lt;helper&gt;
+       &lt;foaf:Person rdf:resource=&quot;urn:org:apache:[your username].rdf&quot; /&gt;
+     &lt;/helper&gt;
 
 If you have your FOAF file externally hosted, then the * rdf:resource * should point to the URL of the file.
 
-For an apache committer with username "foo", your entry would be one of:
+For an apache committer with username &quot;foo&quot;, your entry would be one of:
 
-    <helper>
-    <foaf:Person rdf:resource="urn:org:apache:foo.rdf" />
-    </helper>
-    <helper>
-    <foaf:Person rdf:resource="http://www.example.com/foaf/foo.rdf" />
-    </helper>
+     &lt;helper&gt;
+       &lt;foaf:Person rdf:resource=&quot;urn:org:apache:foo.rdf&quot; /&gt;
+     &lt;/helper&gt;
+     &lt;helper&gt;
+       &lt;foaf:Person rdf:resource=&quot;http://www.example.com/foaf/foo.rdf&quot; /&gt;
+     &lt;/helper&gt;
 
 
-Within 24 hours of committing your addition to *local-outreach/CommunityDevelopment.rdf*, you should appear in the web application\! Head over to [http://community.zones.apache.org/](http://community.zones.apache.org/) a day later a check you're listed properly
+Within 24 hours of committing your addition to *local-outreach/CommunityDevelopment.rdf*, you should appear in the web application\! Head over to [http://community.zones.apache.org/](http://community.zones.apache.org/) a day later a check you&#39;re listed properly
+        
\ No newline at end of file

Added: comdev/site/trunk/content/mentoringprogramme.mdtext
URL: http://svn.apache.org/viewvc/comdev/site/trunk/content/mentoringprogramme.mdtext?rev=1035965&view=auto
==============================================================================
--- comdev/site/trunk/content/mentoringprogramme.mdtext (added)
+++ comdev/site/trunk/content/mentoringprogramme.mdtext Wed Nov 17 09:59:04 2010
@@ -0,0 +1,134 @@
+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 &quot;teacher&quot;, 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 &#39;draft.&#39;
+
+# 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.
+
+# 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.
+
+## 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).
+
+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.
+
+# 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 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.
+
+## 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 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 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.
+
+## 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 
+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:
+
+* 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.
+
+## 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.
+
+## 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,
+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 
+order even though coding continues.
+
+## 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.
+
+Relevant certification is issued to both the mentor and mentee by the admin team.
+
+## Roles and Expectations
+
+### 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 
+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.
+
+### 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.
+
+### 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 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

Added: comdev/site/trunk/content/newbiefaq.mdtext
URL: http://svn.apache.org/viewvc/comdev/site/trunk/content/newbiefaq.mdtext?rev=1035965&view=auto
==============================================================================
--- comdev/site/trunk/content/newbiefaq.mdtext (added)
+++ comdev/site/trunk/content/newbiefaq.mdtext Wed Nov 17 09:59:04 2010
@@ -0,0 +1,99 @@
+Title: NewbieFAQ
+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
+
+## 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:
+
+ * [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
+
+## 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.
+
+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.
+
+## 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.
+
+## 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)
+
+## 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:
+
+* 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 are visible within the community
+
+# Getting Involved with Apache projects
+
+## 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.
+
+## 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.
+
+## 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:
+
+* 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. 
+
+## About the Apache Mentoring Programme
+
+### 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.
+
+For more information see our [mentoring page](mentoringprogramme.html).
+
+### 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

Added: comdev/site/trunk/content/newcommitter.mdtext
URL: http://svn.apache.org/viewvc/comdev/site/trunk/content/newcommitter.mdtext?rev=1035965&view=auto
==============================================================================
--- comdev/site/trunk/content/newcommitter.mdtext (added)
+++ comdev/site/trunk/content/newcommitter.mdtext Wed Nov 17 09:59:04 2010
@@ -0,0 +1,323 @@
+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.
+
+# 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)
+
+## 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.
+
+## 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).
+
+## Community
+How do we evaluate?  By the interactions they have through mail.
+
+## Committment
+How do we evaluate?  By time, by sticking through tough issues, by helping on not-so-fun tasks as well.
+
+## 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
+a cursory review.
+
+# 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.
+
+## Summary
+
+# Call a vote: templates/committerVote.txt
+# Invite the new committer: templates/committerInvite.txt
+
+If they accept, then do:
+
+# 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)
+# Announce the new committer (template/committerAnnounce.txt)
+
+## 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.
+
+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
+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.
+
+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.
+
+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.
+
+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.
+
+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
+our praise in public.
+
+Other notes about the process are available on the main [Apache site](http://www.apache.org/dev/pmc.html#newcommitter)
+
+# 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
+    a frank discussion.
+    
+    ------------------------------------------------------------
+    To: private@[PROJECT].a.o
+    Subject: [Vote] new PMC member: Joe Bloggs
+    
+     [ 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
+    
+    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)
+    
+    ------------------------------------------------------------
+
+
+<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 Invite Template|borderStyle=solid</B></DIV><DIV class="codeContent panelContent">
+    This is the invitation email, sent after a positive result 
+    from the vote for a new committer.
+    
+    ------------------------------------------------------------
+    To: JoeBloggs@foo.net
+    Cc: private@[PROJECT].a.o
+    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
+    of the PMC. We value your contributions and are aware that
+    you are committed to the project.
+    
+    Being a committer enables you to more easily make changes and so
+    not need to go via the patch submission process. This should
+    enable you to be more productive. Being also a PMC member enables
+    you to guide the direction of the project.
+    
+    While this does not mean that you need to participate any more
+    than you already do, it does tend to make one even more committed.
+    Hence you will probably find that you spend more time here.
+    
+    Of course, you can decline and instead remain as a developer,
+    contributing as you do now.
+    
+    This personal email is also providing a chance for you to decline
+    in private. Either way, please let us know in reply only to the
+    private@[PROJECT].a.o list. If you agree, then we will announce
+    on the dev@[PROJECT].a.o list after the account is established.
+    
+    Yours,
+    The Apache [PROJECT] PMC
+    
+    ------------------------------------------------------------------------
+
+
+<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 Accept Template|borderStyle=solid</B></DIV><DIV class="codeContent panelContent">
+    This is the followup email after they have accepted.
+    
+    ------------------------------------------------------------------------
+    To: JoeBloggs@foo.net
+    Cc: private@[PROJECT].a.o
+    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.
+    
+    You need to send a Contributor License Agreement to the ASF.
+    Normally you would send an Individual CLA. If you also make
+    contributions done in work time or using work resources then
+    see the Corporate CLA. Ask us if you have any issues.
+    http://www.apache.org/licenses/#clas
+    
+    You need to choose a preferred ASF user name and alternatives.
+    In order to ensure it is available you can view a list of taken ids at
+    http://www.apache.org/~jim/committers.html
+    
+    Please notify us when you have submitted the CLA and by what means 
+    you did so. This will enable us to monitor its progress.
+    
+    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
+    for occasional matters which must be private.
+    
+    The developer section of the website describes the roles
+    and provides other resources:
+    http://www.apache.org/foundation/how-it-works.html
+    http://www.apache.org/dev/
+    
+    The incubator also has some useful information for new committers
+    in incubating projects:
+    http://incubator.apache.org/guides/committer.html
+    http://incubator.apache.org/guides/ppmc.html
+    
+    In the absence of our own guidelines document we are currently 
+    using those developed at Apache Forrest:
+    http://forrest.apache.org/guidelines.html
+    
+    Yours,
+    The Apache [PROJECT] PMC
+    
+    ------------------------------------------------------------------------
+
+
+<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 Create Template|borderStyle=solid</B></DIV><DIV class="codeContent panelContent">
+    Account creation email for new committers.
+    
+    Follow the instructions at:
+    http://www.apache.org/dev/pmc.html#newcommitter
+    
+    Email is to be sent to root *after* the CLA is registered.
+    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
+    and add the date/Message-Id of the PMC vote summary.
+    
+    If the new member is already a committer, then just need
+    to ask root to add them to the UNIX groups.
+    
+    ------------------------ snip ------------------------------
+    To: root@apache.org
+    Cc: private@[PROJECT].a.o, ###JoeBloggs@foo.net
+    Subject: account request: ###Joe Bloggs
+    
+    Full name:                ...
+    Preferred userid:         ... [please provide acceptable alternates!]
+    Forwarding email address: ...
+    
+    Requested UNIX groups: [PROJECT]
+    
+    The receipt of the ICLA was recorded yesterday.
+    
+    The vote was conducted on the private@[PROJECT].a.o list
+    around YYYY-MM-DD ###
+    Message-Id: ###
+
+
+
+<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
+    followup acceptance.
+    
+    Replace the Joe Blogs in the subject, the ### in the body.
+    
+    ------------------------------------------------------------
+    To: dev@[PROJECT].a.o
+    Subject: new committer and PMC member: ###Joe Bloggs
+    
+    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.
+    
+    ### add specific details here ###
+    
+    Being a committer enables easier contribution to the
+    project since there is no need to go via the patch
+    submission process. This should enable better productivity.
+    Being a PMC member enables assistance with the management
+    and to guide the direction of the project.
+
+
+<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 
+    is where the vote is held..
+    
+    ------------------------------------------------------------
+    To: private@[PROJECT].a.o
+    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]
+    
+    
+    [If three binding +1 and no binding -1]
+    
+    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
+    
+    ------------------------------------------------------------
+
+
+<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 Done Template|borderStyle=solid</B></DIV><DIV class="codeContent panelContent">
+    After the committer account is established.
+    
+    ------------------------------------------------------------
+    To: private@[PROJECT].a.o, ###JoeBloggs@foo.net
+    Subject: account request: ###Joe Bloggs
+    
+    ####, as you know, the ASF Infrastructure has set up your
+    committer account as the username &#39;####&#39;.
+    
+    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 
+    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:
+      https://svn.apache.org/repos/asf/[PROJECT]
+    
+      The general &quot;committers&quot; 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.
+    
+    If you have any questions during this phase, then please
+    see the following resources:
+    
+    Apache developer&#39;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 
+    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

Modified: comdev/site/trunk/lib/path.pm
URL: http://svn.apache.org/viewvc/comdev/site/trunk/lib/path.pm?rev=1035965&r1=1035964&r2=1035965&view=diff
==============================================================================
--- comdev/site/trunk/lib/path.pm (original)
+++ comdev/site/trunk/lib/path.pm Wed Nov 17 09:59:04 2010
@@ -3,7 +3,7 @@ package path;
 # All our pages use the same view function
 our @patterns = (
     [qr!^/.*\.html$!,   normal_page => {} ],
-    [qr!^/.*\.mdtext$!, normal_page => { template=>"standard.html" } ],
+    [qr!^/.*\.mdtext$!, normal_page => { template=>"standard_markdown.html" } ],
 );
 
 # for specifying interdependencies between files

Modified: comdev/site/trunk/templates/standard.html
URL: http://svn.apache.org/viewvc/comdev/site/trunk/templates/standard.html?rev=1035965&r1=1035964&r2=1035965&view=diff
==============================================================================
--- comdev/site/trunk/templates/standard.html (original)
+++ comdev/site/trunk/templates/standard.html Wed Nov 17 09:59:04 2010
@@ -67,7 +67,7 @@
         </style>
 
         <LINK rel="SHORTCUT ICON" href="$images/favicon.ico">   
-        <TITLE>Apache Community Development - {% block title %}{{ headers.title }}{% endblock %}</TITLE>
+        <TITLE>Apache Community Development - {% block title %}{% endblock %}</TITLE>
     </head>
 
     <body onload="init()">
@@ -101,7 +101,7 @@
                   <DIV id="PageContent">        
                      <DIV class="pagecontent">
                          <DIV class="wiki-content">
-                          {% block content %}{{ content|markdown }}{% endblock %}
+                          {% block content %}{% endblock %}
                          </DIV>
                      </DIV>
                   </DIV>

Added: comdev/site/trunk/templates/standard_markdown.html
URL: http://svn.apache.org/viewvc/comdev/site/trunk/templates/standard_markdown.html?rev=1035965&view=auto
==============================================================================
--- comdev/site/trunk/templates/standard_markdown.html (added)
+++ comdev/site/trunk/templates/standard_markdown.html Wed Nov 17 09:59:04 2010
@@ -0,0 +1,3 @@
+{% extends "standard.html" %}
+{% block title %}{{ headers.title }}{% endblock %}
+{% block content %}{{ content|markdown }}{% endblock %}



Mime
View raw message