You are viewing a plain text version of this content. The canonical link for it is here.
Posted to site-cvs@jakarta.apache.org by hu...@apache.org on 2002/10/27 17:08:45 UTC
cvs commit: jakarta-site2/xdocs/site newbie.xml roles.xml
husted 2002/10/27 08:08:44
Modified: xdocs/site roles.xml
Added: xdocs/site newbie.xml
Log:
Add sample acknowledgement letter for new Committers.
Add proposed Newbie Committer FAQ for discussion purposes, but do not link into site anywhere.
Revision Changes Path
1.8 +90 -39 jakarta-site2/xdocs/site/roles.xml
Index: roles.xml
===================================================================
RCS file: /home/cvs/jakarta-site2/xdocs/site/roles.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- roles.xml 28 May 2002 03:48:00 -0000 1.7
+++ roles.xml 27 Oct 2002 16:08:44 -0000 1.8
@@ -11,9 +11,9 @@
<section name="Roles & Responsibilities">
<p>
- The roles and responsibilities that people can assume in the project
- are based on merit. Everybody can help no matter what their role.
- Those who have been long term or valuable contributors to the project
+ The roles and responsibilities that people can assume in the project
+ are based on merit. Everybody can help no matter what their role.
+ Those who have been long term or valuable contributors to the project
obtain the right to vote and commit directly to the source repository.
</p>
@@ -31,7 +31,7 @@
When a user starts to contribute code or documentation patches, they
become a Contributor.
</p>
-
+
<h2>Contributors</h2>
<p>
@@ -56,49 +56,49 @@
In order for a Contributor to become a Committer, another Committer
can nominate that Contributor or the Contributor can ask for it.
</p>
-
+
<p>
Once a Contributor is nominated, all of the Committers for a subproject
will vote. If there are at least 3 positive votes and no negative
votes, the Contributor is converted into a Committer and given write
access to the source code repository for that subproject. This is an
- example offer letter that should be sent to the volunteer after
+ example offer letter that should be sent to the volunteer after
3 positive votes have been received:
</p>
<source><![CDATA[
Dear Contributor,
-The Jakarta project would like to offer you commit privileges.
-We have been impressed with your contributions up till now, and
-believe that your involvement will improve the quality of the
-libraries we produce.
-
-It is important that you realize that these commit privileges give
-you access to the specific Jakarta project repository for which you
-are involved with. They do not provide commit access to any other
-Apache based project. Those projects will have to grant you commit
+The Jakarta project would like to offer you commit privileges.
+We have been impressed with your contributions up till now, and
+believe that your involvement will improve the quality of the
+libraries we produce.
+
+It is important that you realize that these commit privileges give
+you access to the specific Jakarta project repository for which you
+are involved with. They do not provide commit access to any other
+Apache based project. Those projects will have to grant you commit
privileges themselves.
If you are interested in having commit privileges, please just let us
-know, and we will setup an account on apache.org. It would expedite
-the process if you could provide your preferred account name and
-possibly a public SSH key. This process could take a few days once
+know, and we will setup an account on apache.org. It would expedite
+the process if you could provide your preferred account name and
+possibly a public SSH key. This process could take a few days once
we get this information.
We all hope that you accept this invitation.
The Jakarta Project Management Committee.
]]></source>
-
+
<p>
Once there are 3 positive votes and the response to the above letter
has been received, someone from the project community who already has
- commit access should send email to: <strong>root at apache.org</strong>
- that the account should be created. The following information
+ commit access should send email to: <strong>root at apache.org</strong>
+ that the account should be created. The following information
must be included in the email:
</p>
-
+
<ul>
<li>
The name and email address of the new user.
@@ -109,7 +109,7 @@
(ie: jmsith)
</li>
<li>
- The project that the user should be given access to.
+ The project that the user should be given access to.
(ie: Jakarta Foo)
</li>
<li>
@@ -118,32 +118,83 @@
</li>
</ul>
+
+ <p>
+ Once the account has been requested, the new Committer should be sent an
+ acknowledgement that the account is being processed and that he or she is
+ now an official member of the Project. Here is an example acknowledgement
+ letter.
+ </p>
+
+ <source><![CDATA[
+Dear Committer,
+
+Thank you for accepting our invitation. Your account has been setup.
+The username and initial password are being sent under separate cover.
+
+If you have not already done so, please sure to submit the
+Contributor License Agreement to the Apache Software Foundation
+<http://jakarta.apache.org/site/agreement.html>.
+
+Once the Contributor License Agreement is submitted, please also send
+an email to asf at jaguNET.com with the following information
+(please cut and paste to return format):
+
+Name: {your name}
+Email: {your email address the ASF lists}
+Projects: {comma separated list of ASF projects to which you have commit access}
+Key: {a blank line followed by your key}
+
+For example:
+
+Name: Joe Foobar
+Email: joe@byteme.com
+Projects: Tomcat, httpd
+Key:
+adklajdAL()@ N*@U)U@()@@ @)U@
+
+If you already have a Contributor License Agreement file, please
+still send the email to update the ASF records as to your list of
+projects.
+
+Please sure to review the Newbie Comitter FAQ
+[:FIXME: Add link to newbie FAQ] and the other materials
+the website that describe your role as a Committer.
+
+We are honored that you have accepted our invitation and are
+sincerely grateful for your assistance. We look forward to working
+together.
+
+The Jakarta Project Management Committee.
+
+]]></source>
+
<p>
- The new committer should also send an email to <strong>asf at jaguNET.com</strong>
+ The new committer should also send an email to <strong>asf at jaguNET.com</strong>
with the following information (please cut and paste to return format):
</p>
<blockquote>
- Name: {your name} <br/>
- Email: {your email address on the ASF lists} <br/>
- Projects: {comma separated list of ASF projects to which you have commit access} <br/>
+ Name: {your name} <br/>
+ Email: {your email address on the ASF lists} <br/>
+ Projects: {comma separated list of ASF projects to which you have commit access} <br/>
Key: {a blank line followed by your key}
</blockquote>
<p>For example:</p>
<blockquote>
- Name: Joe Foobar <br/>
- Email: joe@byteme.com <br/>
- Projects: Tomcat, httpd <br/>
- Key: <br/>
+ Name: Joe Foobar <br/>
+ Email: joe@byteme.com <br/>
+ Projects: Tomcat, httpd <br/>
+ Key: <br/>
adklajdAL()@ N*@U)U@()@@ @)U@
</blockquote>
<p>
- Finally, a new committer should also submit a signed copy of the Contributor
- License Agreement to the ASF. See the <a href="agreement.html"><strong>Contributor
- License Agreement page</strong></a> for details.
+ Finally, a new committer should also submit a signed copy of the Contributor
+ License Agreement to the ASF. See the <a href="agreement.html"><strong>Contributor
+ License Agreement page</strong></a> for details.
</p>
<p>
@@ -161,7 +212,7 @@
on request. In other words, committers should be able to update the
main Jakarta website.
</p>
-
+
<p>
Note 2: If the module that the committer needs access to is a sub
module within a project (ie: jakarta-turbine-tdk or
@@ -182,18 +233,18 @@
A list of some of our current Committers can be found in our <a
href="./whoweare.html">Project Credits</a>.
</p>
-
+
<p>
<h2>Project Management Committee (PMC)</h2>
Committers who frequently participate with valuable contributions may
have their status promoted to that of a "<em>Project Management
Committee Member</em>". This committee is the official managing
- body of the Jakarta Project and is responsible for setting overall
- project direction. In order to become a Member, someone on
+ body of the Jakarta Project and is responsible for setting overall
+ project direction. In order to become a Member, someone on
the PMC must nominate the Committer. The individual may then be
approved with a 3/4 majority of the PMC.
</p>
-
+
<p>
To view the Project Management Committee bylaws, <a href="management.html">
click here</a>.</p>
1.1 jakarta-site2/xdocs/site/newbie.xml
Index: newbie.xml
===================================================================
<?xml version="1.0"?>
<document>
<properties>
<author email="husted@apache.org">Ted Husted</author>
<title>FAQs</title>
</properties>
<body>
<section name="Newbie Committer FAQ">
<ul>
<li>
<a href="#email">How do I setup my email account?</a>
</li>
<li>
<a href="#logon"></a>How do I login to the CVS?
</li>
<li>
<a href="#guidelines"></a>What are project guidelines?
</li>
<li>
<a href="#role">What are my responsibilities as a Committer?</a>
</li>
<li>
<a href="#legal"></a>Does being a Committer give me any legal status with the Foundation?
</li>
<li>
<a href="#resources"></a>Do Committers have access to internal resources?
</li>
<li>
<a href="#guides"></a>Where can I learn more about working at Apache and Jakarta?
</li>
</ul>
</section>
<section name="How do I setup my email account?" href="email">
<p>
You can use SSH and Pine or put a .forward file in your user directory [:FIXME: Need a brief howto here] to send the mail to another account.
</p>
</section>
<section name="How do I login to the CVS?" href="logon">
<p>
Follow the links regarding "Full Remote Access" at the bottom of the
<a href="cvsindex.html">CVS Repository page</a>.
</p>
</section>
<section name="What are project guidelines?" href="guidelines">
<p>
All projects are subject to the Apache Foundation
<a href="http://apache.org/foundation/bylaws.html">bylaws</a>
and the current policies of its Board.
In furtherance of the bylaws and ASF policies, each project and any of its subprojects may establish their own guidelines.
When a subproject does not establish their own guidelines, the project guidelines are in effect.
</p>
<p>
The current Jakarta project guidelines are maintained the
<a href="guidelines.html">website</a>
(Yes, this is all there is =:)
</p>
</section>
<section name="What are my responsibilities as a Committer?" href="role">
<p>
As an Apache volunteer, you have the right to set your own priorities and do the work that scratches your own itch.
As a Committer, you have a responsibility to the community to help create a product that will outlive the interest of any particular volunteer (including yourself).
</p>
<p>
A prime responsibility of the Committers is to decide when a branch of code is ready for release.
A release is not to taken lightly; each release must uphold the Apache tradition of superlative quality.
</p>
<p>
The project guidelines includes a section about
<a href="decisions.html">releases and decision-making</a>.
</p>
<p>
If Committers disagree about how development the main trunk should proceed, each Committer has the right to create a whiteboard branch in CVS and pursue another line of a development.
If the Committers decide a branch has come to represent the mainstream line of development, it can promoted to the main trunk.
</p>
<p>
For more about creating whiteboard branches, see the
<a href="http://x180.net/rules.html">Rules for Revolutionaries</a>.
</p>
<p>
The project guidelines include a section about
<a href="source.html">managing the code repository</a>.
</p>
<p>
All contributors must have a
<a href="http://jakarta.apache.org/site/agreement.html">Contributor License Agreement</a>
file, which details the responsibilities of the contributors.
When committing code submitted by another contributor, please verify that the author has submitted a license agreement.
</p>
</section>
<section name="Does being a Committer give me any legal status with the Foundation?" href="legal">
<p>
The Foundation encourages Committers to make the day-to-day decisions regarding the direction of a codebase, but the overall management of the codebase is delegated by the Foundation to Project Management Committee.
The PMC members have legal standing with the Foundation as the managers of the project.
In the event of a intellectual property dispute, the Foundation will defend the code, the PMC members, and any Committer who is also a
<a href="http://apache.org/foundation/members.html">Member</a> of the Apache Software Foundation.
</p>
<p>
Committers are encouraged to become PMC members or ASF members so that they may entitled to greater legal protection.
Subprojects are also encouraged to petition the ASF
<a href="http://apache.org/foundation/board/">Board</a>
and ask for full project status whenever they deem their community can stand its own.
Full project status gives Committers the opportunity to participate in their own PMC and become more involved in the greater Apache community.
</p>
<p>
[:FIXME: Incorporate background the
<a href="http://incubator.apache.org">incubator project</a>
once it is clearly defined.]
</p>
<p>
See the Apache Software Foundation
<a href="http://apache.org/foundation/">website</a>
for more about the Apache community and the goals of the Foundation.
</p>
</section>
<section name="Do Committers have access to internal resources?" href="resources">
<p>
All Apache accounts are subscribed to the Committer list, which is used primarily for security alerts and other dire messages.
The Committer list is not used for routine communication but is used only as a "red phone".
</p>
<p>
Other than that, Committers have write access and voting rights but use all the same resources as users and contributors.
There are no hidden resources.
Private communication between the Committers is strongly discouraged.
All communication regarding product support and development should take place the lists and CVS.
If a product decision does arise in a private communication, it should transcribed to the list so that there is a public record for the other contributors to follow.
</p>
<p>
the long-term management level, the PMCs and Apache Board do maintain private lists for sensitive discussions but do not conduct official business over these lists.
The business of the Jakarta PMC is conducted the
<a href="mail.html">General list</a>.
The business of the Apache foundation is conducted the
<a href="http://apache.org/foundation/mailinglists.html">Members list</a>.
</p>
</section>
<section name="Where can I learn more about working at Apache and Jakarta?" href="guides">
<p>
The Jakarta project guidelines are being (slowly) augmented by a series of
"<a href="guides.html">Apache Guides</a>".
These are still barely more than outlines, and much work still needs to done.
Feel free to jump in and contribute details whatever you learn along the way!
</p>
</section>
</body>
</document>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>