Ted Husted wrote:
On Jakarta, we have a sample letter that can be sent to Contributors when we are ready to nominate them as Committers. It occurred to me that we should also have a follow-up letter welcome them as a Committer. This would be a good place to insert some of points that have come up over Reorg and Community lately.
Please see the updated page at <http://jakarta.apache.org/site/roles.html> for a sample "Dear (new) Committer" letter.
The letter refers to a "Newbie Committer FAQ". I did not link in the newbie FAQ, since I thought it warranted a second by a current member of the Jakarta PMC.
The proposed Newbie FAQ can be viewed at <http://jakarta.apache.org/site/newbie.html>.
It also occurs to me that something the incubator project can do is provide a template set of guidelines and procedures for the projects. In the way of guidelines, we have a draft set that includes several "clarifications" , in case anyone in the incubator project is interested in this idea.
<http://jakarta.apache.org/site/proposal.html>
> Release Plan > A release plan is used to keep all volunteers aware of > when a release is desired, who will be the Release Manager, > when the repository will be frozen to create a release, and > other assorted information to keep volunteers from tripping > over each other. Lazy majority decides each issue in a > release plan, or lazy consensus if the issue involves a > product change.
Under the current wording there is no obligation of a sub-project to notify its PMC of a release. Based on all of the reorg traffic it seems to me that a release is a sufficiently significant even that there should be something in the procedures that requires explicit notification of a release to the responsible PMC.
Cheers, Steve.
-Ted.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
Stephen J. McConnell
OSM SARL digital products for a global economy mailto:[EMAIL PROTECTED] http://www.osm.net
