OpenJDK Community Bylaws: Second Public Draft
mark.reinhold at oracle.com
mark.reinhold at oracle.com
Thu Jun 2 22:06:39 PDT 2011
2011/5/31 16:35 -0700, philip.race at oracle.com:
>> A Member of a Group has write access to the Group’s web content and
>> file repositories.
> Does this imply that Contributors must rely on Group members to do pushes?
> Seems a backward step from where we are now, where with appropriate approval
> from group members, any contributor can push.
No, any Committer can push to a Group's web content. That's actually a
bug in the current infrastructure.
> But there's also the subtlety that ..
>> Groups do not have code repositories of their own but they may
>> sponsor Projects, which do
> so maybe that first sentence should have said the group's PROJECT repositories
If you mean a Project's code repositories, then a Contributor must be a
Committer to that Project in order to push changesets into those repos.
It's not that hard to make a Contributor into a Committer -- it's just
> There are so many roles : eg contributor/openjdk member/group
> Author and committer are project based. It would seem that being a
> committer and author for the JDK 7 project doesn't automatically roll
> over to JDK7 updates, JDK 8, or JDK 9 which seems overly onerous.
It's actually not onerous. When a Project is created the newly-chosen
Project Lead is, at first, the only Committer, and as such has the
opportunity to "vote" an appropriate set of Contributors into the
Committer role for that Project.
> I'm unclear how groups roles relate to these roles.
In general there's no specific connection between being a Member of some
Group and being an Author, Committer, or Reviewer for a Project, even if
that Project is sponsored by that Group.
In practice there will, of course, often be a lot of overlap in some
cases, but there's no reason to formalize it in the Bylaws.
>> Every OpenJDK Membership is subject to automatic Expiration after one
>> year, but will be renewed upon request. A request for renewal must be
>> received within one year of expiration.
> So contributor membership and group membership do not expire ? Only
> OpenJDK membership?
> How do you expect the renewal to work in practice
> ? Will there be some kind of reminder ?
There will be some kind of automated system to send reminders and process
>> An individual may be nominated to a new or newly-empty
>> appointed seat by any Governing Board member, and is
>> approved by a Simple Majority of the Governing Board.
> I don't understand how that is supposed to work since the
> appointed positions are defined to be appointed by either
> IBM or Oracle.
Good catch -- of course Board members can't nominate or vote upon
appointed seats. I suspect that paragraph is a leftover from a (much)
earlier draft. I'll remove it.
Thanks for your comments!
More information about the gb-discuss