Draft JDK 7 Updates Project Role Nomination Process

[Kelly O'Hair]

I assume this will be put on http://openjdk.java.net/projects/jdk7u/ at some point?

Have you ever worked for the government? It reminds me of the IRS tax code. :^(

Shortly before my eyes glazed over 8^}, I had a few questions

Q. Specifically, what is the definition of "a significant contribution" (or "significant changeset") to this project?
     Who determines "significant"? Why not just 'any changeset'? Seems like any changeset is significant, or why change?

Q. How is the changeset contribution scoring done?
     If I contributed a change to jdk8, and someone else integrates that change into jdk7u, does that count?
     If I contribute changesets directly to Oracle internal non-open jdk7u4 repositories, does that count?
     Are the hundreds of changesets already in the repositories with my name on them count?
     If I send you a bottle of nice wine, can I increase my score card? ;^)

-kto

On Dec 13, 2011, at 6:32 PM, Dalibor Topic wrote:

> Hi everyone,
> 
> it's process time again. Now that we're past a significant milestone for the project,
> with the 7u2 release out of the door (wooohoo!), and with the Mac OS X port coming into 
> this Project, it's time to come up with a process that describes how Project Roles
> (Author, Committer, Reviewer) are acquired in the Project in accordance with the 
> Bylaws.
> 
> Here's a draft that I'll leave open for discussion until Friday, December 16th. Once 
> it's finalized, I'll start the votes for new Committers and Reviewers. I'll also post
> a list of new Authors.
> 
> Thus draft covers the Author role in significant detail, as that's the first step to take
> for new Contributors, goes into some detail of how to keep Committer and Reviewer roles
> with jdk8 and hsx in sync 'on demand', which have an upstream role for most of the changes 
> coming into this Project, and finally deals with how roles get propagated from integrated
> Projects, like the Mac OS X port, to allow their developers to continue to work in the
> same roles as before the integration.
> 
> JDK 7 Update Project Role Nomination Process
> ============================================
> 
> §1 - Author Role
> ----------------
> 
> Rule 0. Any Contributor may request the Author role in this Project by contacting the 
> Project Lead. An e-mail request should be sent directly to the Project Lead and the 
> Technical Lead. It should contain a short description of the Contributor's qualifications, 
> including past contributions to this Project. For more information see [0].
> 
> Rule 1. Project Lead is responsible for verifying that the requesting Contributor satisfies 
> the requirements of the Contributor role. [1] If the requirements are not satisfied, the 
> request is denied.
> 
> Rule 2. Project Lead is responsible for contacting the OpenJDK registrar with the request 
> to add the Contributor as an Author to the JDK 7 Updates Project. A template is provided 
> below:
> 
>  To: <registrar>
>  Subject: Author Role for <full name> in JDK 7 Updates Project
> 
>  I hereby grant <full name> the Author role in the JDK 7 Updates Project.
> 
> Rule 3. Once the Author role is reflected in the JDK 7 Updates Project in the OpenJDK Census [2],
> the Project Lead has the responsibility to inform the Contributor of their new role in this
> Project. A template is provided below:
> 
>  To: <Contributor>
>  Subject: Author role in JDK 7 Updates Project
> 
>  The OpenJDK Census at http://openjdk.java.net/census#jdk7u has been updated to reflect your 
>  Author role in the JDK 7 Updates Project. 
> 
> Rule 4. Project Lead has the responsibility to inform jdk7u-dev mailing list of new Authors in
> the JDK 7 Updates Project.
> 
> §2 - Committer Role
> -------------------
> 
> Rule 0. A Contributor should make at least eight significant contributions to this Project 
> before being nominated. 
> 
> Rule 1. Any Committer on this Project may nominate a Contributor to be a new Committer on 
> this Project. For more information see [3].
> 
> Rule 2. Any Contributor who satisfies the requirement in Rule 0 and has the Committer role
> in the JDK 8 Project or the HotSpot Express Project, may request the nomination for the 
> Committer role in JDK 7 Updates Project by contacting the Project Lead. An e-mail request 
> should be sent directly to the Project Lead and the Technical Lead.
> 
> §3 - Reviewer Role
> ------------------
> 
> Rule 0. A Committer should author and push at least 32 significant changesets into this
> Project's forests before being nominated to be a Reviewer. 
> 
> Rule 1. Any JDK 7 Update Project Reviewer may nominate any of the Project's Committers 
> to be a Project Reviewer of this Project. For more information see [4].
> 
> Rule 2. The Project Lead is automatically considered to be a Reviewer, and remains a Reviewer 
> after leaving the Project Lead role.
> 
> Rule 3. Any Committer who satisfies the requirement in Rule 0 and has the Reviewer role
> in the JDK 8 Project or the HotSpot Express Project, may request the nomination for the 
> Reviewer role in JDK 7 Updates Project by contacting the Project Lead. An e-mail request 
> should be sent directly to the Project Lead and the Technical Lead.
> 
> §4 - Integration of other Projects
> ----------------------------------
> 
> Rule 0. When another OpenJDK Project is integrated into JDK 7 Updates Project, the
> Project Lead should grant the Author role to the Contributors of the integrated Project 
> who don't already have an Author role in this Project.
> 
> Rule 1. Project Lead should nominate Committers of the integrated Project as Committers,
> unless the nominees already have that role in this Project.
> 
> Rule 2. Project Lead should nominate Reviewers of the integrated Project as Reviewers,
> unless the nominees already have that role in this Project.
> 
> Rule 3. Project Lead should nominate Project Lead of the integrated Project as Reviewer,
> unless the nominee already has that role in this Project.
> 
> [0] http://openjdk.java.net/projects/#project-author
> [1] http://openjdk.java.net/bylaws#contributor
> [2] http://openjdk.java.net/census
> [3] http://openjdk.java.net/projects/#project-committer
> 
> 
> cheers,
> dalibor topic
> -- 
> Oracle <http://www.oracle.com>
> Dalibor Topic | Java F/OSS Ambassador
> Phone: +494023646738 <tel:+494023646738> | Mobile: +491772664192 <tel:+491772664192>
> Oracle Java Platform Group
> 
> ORACLE Deutschland B.V. & Co. KG | Nagelsweg 55 | 20097 Hamburg
> 
> ORACLE Deutschland B.V. & Co. KG
> Hauptverwaltung: Riesstr. 25, D-80992 München
> Registergericht: Amtsgericht München, HRA 95603
> Geschäftsführer: Jürgen Kunz
> 
> Komplementärin: ORACLE Deutschland Verwaltung B.V.
> Hertogswetering 163/167, 3543 AS Utrecht, Niederlande
> Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697
> Geschäftsführer: Alexander van der Ven, Astrid Kepper, Val Maher
> 
> Green Oracle <http://www.oracle.com/commitment> Oracle is committed to developing practices and products that help protect the environment