On 03:32 Wed 14 Dec , 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. >
This reads fine to me. However, this page: http://openjdk.java.net/projects/jdk7u/groundrules.html refers to a further role of 'maintainer'. How does this fit into the author/committer/reviewer structure: Maintainers jdk7u-osx forest: Paul Hohensee. jdk7u-osx forest - AWT, 2D and Swing: Artem Ananiev. Other forests: Edvard Wendelin and Dalibor Topic. I'm not sure of the value of additional reviewers (like myself) on this project if changesets require reviews by both the project lead and technical lead anyway. -- Andrew :) Free Java Software Engineer Red Hat, Inc. (http://www.redhat.com) Support Free Java! Contribute to GNU Classpath and IcedTea http://www.gnu.org/software/classpath http://icedtea.classpath.org PGP Key: 248BDC07 (https://keys.indymedia.org/) Fingerprint = EC5A 1F5E C0AD 1D15 8F1F 8F91 3B96 A578 248B DC07
signature.asc
Description: Digital signature
