This is an automated email from the ASF dual-hosted git repository. aheritier pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/maven-site.git
The following commit(s) were added to refs/heads/master by this push: new 416f0d6a doc: Remove Committer School 416f0d6a is described below commit 416f0d6a515d7c3aa8c3ea5d39c90c0b5422eb26 Author: Arnaud Héritier <aherit...@apache.org> AuthorDate: Thu Oct 24 00:08:12 2024 +0200 doc: Remove Committer School --- .../guides/development/guide-committer-school.apt | 61 ---------------------- 1 file changed, 61 deletions(-) diff --git a/content/apt/guides/development/guide-committer-school.apt b/content/apt/guides/development/guide-committer-school.apt index 6c6aa22c..c00d3a9a 100644 --- a/content/apt/guides/development/guide-committer-school.apt +++ b/content/apt/guides/development/guide-committer-school.apt @@ -94,64 +94,3 @@ How to get your patches noticed <<Note:>> 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 <only one> email about your patch on any specific JIRA issue. - -Stephen, Arnaud & Barrie's school for potential Maven committers - - 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. - - To register for the class you need to complete the following steps: - - [[1]] Read the {{{http://www.apache.org/licenses/icla.txt}Apache Individual Contributor License Agreement}}. When you graduate from the class you will be required to sign this in order to become a committer. - - [[1]] Subscribe to the {{{mailto:d...@maven.apache.org}d...@maven.apache.org}} mailing list. - - [[1]] Send an email to the list with the Subject line: <<<[Committer School] I would like to become a committer>>> and the Message body: - ---- -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 ---- - - [] - - 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: - - [[1]] 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: - <<<[Committer School] Should I fix MNG-4612?>>> - The Message body should be something like: - ---- -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 ---- - - [[1]] 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. - - [[1]] 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: - <<<[Committer School] Patch for review: MNG-4612>>> The Message body should be something like: - ---- -I have tested that this is a good patch and I would appreciate if a committer could review and apply - -Thanks ---- - - [] - - 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. - - 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. - - Personally, if I see somebody averaging a good patch a week for 2-3 months and being active helping out on the {{{mailto:us...@maven.apache.org}us...@maven.apache.org}} and {{{mailto:d...@maven.apache.org}d...@maven.apache.org}} mailing lists then I think I could make a strong case for such a person being given commit access. - - So if you think you have the right stuff and want to become a Maven committer... class enrollment is open! \ No newline at end of file