[incubator] branch master updated: Clarify and update committer page

[jm...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

jmclean pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator.git


The following commit(s) were added to refs/heads/master by this push:
     new eeab239  Clarify and update committer page
     new fa3f0ab  Merge pull request #43 from justinmclean/master
eeab239 is described below

commit eeab23959ebb7db91264af8db097fbd7dcb3ab63
Author: Justin Mclean <jm...@apache.org>
AuthorDate: Sat Oct 12 11:42:26 2019 +1100

    Clarify and update committer page
---
 pages/guides/committer.ad | 93 +++++++++++++----------------------------------
 1 file changed, 26 insertions(+), 67 deletions(-)

diff --git a/pages/guides/committer.ad b/pages/guides/committer.ad
index 44030e6..265eeba 100644
--- a/pages/guides/committer.ad
+++ b/pages/guides/committer.ad
@@ -18,59 +18,40 @@ Apache Incubator PMC
 :toc:
 :imagesdir: ../images/
 
-The link:/policy/incubation.html#Committers[Roles and Responsibilities] document describes the general role of a
-committer on an incubating project. This page provides links to more information to help new committers get started.
+The link:/policy/incubation.html#Committers[Roles and Responsibilities] document describes the general role of a committer on an incubating project. This page provides links to more information to help new committers get started.
 
 == Mailing Lists
-Everything -- but *everything*-- inside the Apache world
-occurs or is reflected in email. As some people say, 'If it isn't
-in my email, it didn't happen.' Decisions only get made on public
-Apache mail lists -- not anywhere off list, such as IRC, IM, or private
-emails.
- Each project has a set of lists, which are typically called
-dev@*project*, user@*project*, and
-commits@*project*. A few link:http://www.apache.org/foundation/mailinglists.html[Apache-wide lists] cross all boundaries, including:
-
-- *committers*: sends important messages to all
-Apache committers; it's not used for discussions;
-- *community*: where all Apache committers can
-discuss things that are about Apache;
-- *infrastructure*: where the roots and the
-infrastructure team discuss and work on the Apache
-infrastructure needs;
-- *legal-discuss*: where Apache committers can
-ask questions that have a legal aspect;
-- *repository*: discussions about the Apache artifact repository;
-- *party*: where people plan how to have fun. :-)
+Everything inside the Apache world needs to occur asynchronously and be archived. Email is currently the best platform for this. As some people say, 'If it isn't on the mailing list, it didn't happen.' Decisions only get made on public Apache mail lists, not anywhere offlist, such as IRC, IM, or private emails. If decisions are being made elsewhere, they need to be brought back to the mailing list.
+
+Each project has a set of lists, which are typically called dev@*project*, user@*project* (or users@*project*), issues@*project* and commits@*project*. A few link:http://www.apache.org/foundation/mailinglists.html[Apache-wide lists] cross all boundaries, including:
+
+- *community*: where all Apache committers can discuss things that are about Apache;
+- *infrastructure*: where the infrastructure team discuss and work on the Apache infrastructure needs;
+- *legal-discuss*: where Apache committers can ask questions that have a legal aspect;
+- *builds*: discussions about the Apache continuous integration infrastructure;
+
+Mailing lists are also archived and searchable at server places, including link:https://lists.apache.org[Apache Pony Mail].
 
 === Action items for committers include:
 
--  Become familiar with Apache developer link:http://www.apache.org/dev/contrib-email-tips.html[Tips for email contributors].
-- Subscribe to the user, dev, and commits lists for your project.
+- Become familiar with Apache developer link:http://www.apache.org/dev/contrib-email-tips.html[Tips for email contributors].
+- Subscribe to the user, dev, issues and commits lists for your project.
 - Become aware of what else is going on in the Incubator by subscribing to the Incubator's general list.
 - Become aware of what else is going on at the ASF by subscribing to the link:http://www.apache.org/foundation/mailinglists.html#foundation-community[community], link:http://www.apache.org/foundation/mailinglists.html#foundation-infrastructure[infrastructure], and link:http://www.apache.org/foundation/mailinglists.html#foundation-legal[legal-discuss] Apache-wide lists.
 
-Apache also has private lists. For example, your project will
-probably have a private mail list named private@*project*.incubator.apache.org,
-which your Podling PMC will use for sensitive discussions. Never
-mix public and private mail lists in the same post -- see the
-section titled link:http://www.apache.org/foundation/how-it-works.html#management[Balancing confidentiality and public discussion]
-in link:http://www.apache.org/foundation/how-it-works.html[How it Works]. For example, never include both your dev and private
-lists in the same post. Posting to the dev list is sufficient
-because each member of your Podling PMC will also be on that
-list.
+Apache also has private lists. For example, your project will probably have a private mail list named private@*project*.apache.org, which your Podling PMC will use for sensitive discussions. Never
+mix public and private mail lists in the same post -- see the section titled link:http://www.apache.org/foundation/how-it-works.html#management[Balancing confidentiality and public discussion] in link:http://www.apache.org/foundation/how-it-works.html[How it Works]. For example, never include both your dev and private lists in the same post. Posting to the dev list is sufficient because each member of your Podling PMC will also be on that list.
 
 == Project Web Site
-The Incubator link:sites.html[Podling Websites] guide documents how to get your project web site going.
+The Incubator link:sites.html[Podling Websites]  documents how to get your project web site going.
 
 == Committer Resources
 
-- The link:http://www.apache.org/dev/new-committers-guide.html[Guide for New Committers ]is a great place to start and points to additional committer-only resources.
+- The link:http://www.apache.org/dev/new-committers-guide.html[Guide for New Committers] is a great place to start and points to additional committer-only resources.
 - Browse the pages at link:http://www.apache.org/dev[http://www.apache.org/dev/] often.
 - Subscribe to the link:http://www.apache.org/foundation/mailinglists.html#foundation-infrastructure[infrastructure] list, then raise awareness on your project on what goes on behind the scenes.
 
-Be proactive about responding to infrastructure issues on your project mailing lists. Does the web server seem to be down? Is Jira or Subversion down? Check the link:http://www.apache.org/dev/#status[status of servers]
-and explain the reason to your project lists (as you can see, no need to alert the ASF infrastructure people).
+Be proactive about responding to infrastructure issues on your project mailing lists. Does the webserver seem to be down? Is Jira or Git down? Check the link:http://status.apache.org/[ASF status page] and explain the reason to your project list (as you can see, no need to alert the ASF infrastructure people).
 
 
 == Podling PMC (PPMC)
@@ -78,37 +59,15 @@ If you are a member of your PPMC, become familiar with the link:/policy/incubati
 
 == Orientating New Committers: Understanding Apache
 
-When a committer is elected by a typical top level project, the nominator
-and other PMC members educate the new committer about Apache. In the Incubator, this
-inductive must be performed by the Mentors. This process is one of the most important
-for the long term health of a project.
-
-Apache works on the principle that discussions should happen on the most open forum
-available. Unless the matter involves a sensitive matter (such as security or
-personal issues), it should be raised on an open mailing list (typically the podling dev list
-or the incubator general list). Use of the incubator private list should be reserved
-for official notifications and sensitive topics.
-
-Mentors need to take care. During the initial bootstrapping a habit may develop
-of emailing private list. It is important to break this habit as soon as the mailing
-lists are available.
-
-Netiquette about the correct use of *cc*'s may also be difficult to
-effectively impart. During the bootstrap process there are a number of occasions
-where *cc*'s are required. The typical usage is to copy in a private
-listing to indicate that the action has the lazy permission of the committee.
-*cc*'s are very commonly used to create inefficient ad-hoc mailing lists in
-the commercial world. Except for a small number of defined processes, *cc*'s
-are frowned upon at Apache. Mentor need to encourage questions to be asked first
-on the public lists of the project then raised (if necessary) to the general
-incubator list.
+When a committer is elected by a top level project, the nominator and other PMC members educate the new committer about Apache. In the Incubator, this is performed by the Mentors. This process is one of the most important for the long term health of a project.
 
-== Questions?
-If you have any questions, please ask on the Incubator's
-general mail list.
-Don't forget to check the information at:
+Apache works on the principle that discussions should happen on the most open forum available. Unless the matter involves a sensitive matter (such as security or personal issues), it should be raised on an open mailing list. Typically this will be the podling dev list or the incubator general list. Use of the private incubator list should be reserved for sensitive topics only.
 
+Mentors need to take care. During the initial bootstrapping a habit may develop of emailing private list. It is important to break this habit as soon as the mailing lists are available.
+
+Netiquette about the correct use of *cc*'s may also be difficult to impart effectively. During the bootstrap process, there are a number of occasions where *cc*'s are required. The typical usage is to copy in a private listing to indicate that the action has the lazy permission of the committee. *cc*'s are very commonly used to create inefficient ad-hoc mailing lists in the commercial world. Except for a small number of defined processes, *cc*'s are frowned upon at Apache. Mentors need t [...]
+
+== Questions?
+If you have any questions, please ask on the Incubator's general mail list. Don't forget to check the information at:
 - link:http://www.apache.org/dev[http://www.apache.org/dev/]
-** it is one of the most current resources for committers.
-- link:general.html#FAQ[Incubator General FAQ]
 


---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org