Author: svn-site-role
Date: Wed Oct 23 22:11:57 2024
New Revision: 1921513
Log:
Site checkin for project Apache Maven Site
Modified:
maven/website/content/guides/development/guide-committer-school.html
Modified: maven/website/content/guides/development/guide-committer-school.html
==============================================================================
--- maven/website/content/guides/development/guide-committer-school.html
(original)
+++ maven/website/content/guides/development/guide-committer-school.html Wed
Oct 23 22:11:57 2024
@@ -176,41 +176,7 @@
<p>The simplest way to get your patches noticed is to submit them to the JIRA
issue that they fix.</p>
<p>Remember that the Maven project is run by volunteers in their spare time,
so very often we may not notice your patch for a few days. </p>
<p>If you are certain that your patch is a good patch, and a week has passed
with no comments on JIRA, then you should send <i>one and only one</i> email to
the <a class="externalLink"
href="mailto:[email protected]";>[email protected]</a> mailing list to
see if your patch can get noticed.</p>
-<p><b>Note:</b> you need to be fairly confident that your patch is a good
patch, because if you keep on pestering the Maven developers looking to have
non-good patches applied, your merit will become negative and people will be
less inclined to help you get your patches applied... also this is why you
should send one and <i>only one</i> email about your patch on any specific JIRA
issue.</p></section><section>
-<h1>Stephen, Arnaud & Barrie's school for potential Maven committers</h1>
-<p>To help people who are interested in becoming Maven committers fulfill
their goals, myself, Arnaud Heritier and Barrie Treloar (along with any other
current Maven committers who decide to help) will be running an assignment
based class to help people become committers. </p>
-<p>To register for the class you need to complete the following steps:</p>
-<ol style="list-style-type: decimal">
-<li>Read the <a class="externalLink"
href="http://www.apache.org/licenses/icla.txt";>Apache Individual Contributor
License Agreement</a>. When you graduate from the class you will be required to
sign this in order to become a committer.</li>
-<li>Subscribe to the <a class="externalLink"
href="mailto:[email protected]";>[email protected]</a> mailing list.</li>
-<li>Send an email to the list with the Subject line: <code>[Committer School]
I would like to become a committer</code> and the Message body:
-<div class="verbatim">
-<pre>I am interested in the following areas:
- _______, _______ and ______
-If anyone knows any issues that I could take a look at I would be very much
appreciated
-
-Thanks</pre></div></li></ol>
-<p>Once you have registered your class assignments are basically to find JIRA
issues that you want to fix. The issues can be in any part of Maven, but it is
best to start with the areas you have the most interest in. Once you have found
a JIRA issue that you are interested in fixing, the process will work a little
something like this:</p>
-<ol style="list-style-type: decimal">
-<li>Make sure that nobody else is working on the issue and that the issue is
one that should be fixed by sending an email to the list with a Subject line
something like: <code>[Committer School] Should I fix MNG-4612?</code> The
Message body should be something like:
-<div class="verbatim">
-<pre>I have had a look at MNG-4612 and I think this is a real issue because...
-
-I think I can fix it like so....
-
-Is that the correct way to go about fixing it and is it a real issue at all
-
-Thanks</pre></div></li>
-<li>Wait a couple of days. Arnaud, Barrie and I will do our best to respond
quickly to all such emails, but please keep in mind that we are doing this in
our spare time.</li>
-<li>If you get the all clear, develop your patch and upload it to the JIRA,
after it is uploaded, send an email to the list with a subject line something
like: <code>[Committer School] Patch for review: MNG-4612</code> The Message
body should be something like:
-<div class="verbatim">
-<pre>I have tested that this is a good patch and I would appreciate if a
committer could review and apply
-
-Thanks</pre></div></li></ol>
-<p>Keep in mind that the Committer School is just a way for us to identify
people who are committed to developing patches with a view to eventually
becoming committers. </p>
-<p>When we have enough evidence that we think we can get you accepted as a
committer we will nominate you and hopefully your nomination will be
accepted.</p>
-<p>Personally, if I see somebody averaging a good patch a week for 2-3 months
and being active helping out on the <a class="externalLink"
href="mailto:[email protected]";>[email protected]</a> and <a
class="externalLink"
href="mailto:[email protected]";>[email protected]</a> mailing lists
then I think I could make a strong case for such a person being given commit
access.</p>
-<p>So if you think you have the right stuff and want to become a Maven
committer... class enrollment is open!</p></section>
+<p><b>Note:</b> you need to be fairly confident that your patch is a good
patch, because if you keep on pestering the Maven developers looking to have
non-good patches applied, your merit will become negative and people will be
less inclined to help you get your patches applied... also this is why you
should send one and <i>only one</i> email about your patch on any specific JIRA
issue.</p></section>
</main>
</div>
</div>
