Groups
Projects
AGroup is a collection ofParticipants who engage in openconversation about a common interest. That interest may be in thecreation, enhancement, or maintenance of a specific body of code orit may lie in other areas,e.g., quality ordocumentation.
Groups are meant to capture the slowly-evolving social structureof the Community. They are usually longer-lived thanProjects and therefore more difficult tocreate and dissolve. Generally speaking, a newGroup should be proposed only after it has become clear that anexisting nontrivial set of regular Participants who are alreadycollaborating together would benefit from its creation. These arenot meant to be lightweight "interest groups".
A Group may have web content, independent of any Project, whichis writable by all of the Group's Members. A Group also has one ormoremailing lists. A Groupdoes not have file repositories of its own but it may sponsorProjects, which do.
TheBylaws define several ways for theCommunity to expand via Groups. A step-by-step guide is providedhere for the following common cases:
This page is a summary and interpretation of theBylaws. If there is a conflict between this page andthe Bylaws then the Bylaws are considered authoritative.
AnyMember of a Group maynominate aContributor toMembership in that Group. Group membership is one route to becomingan OpenJDK Member.
As a rough guide, a Contributor should be regularly active in aGroup or its sponsored Projects for at least a year before beingnominated to be a Group Member.
Send a call-for-votes to the Group's OpenJDKmailing list. The voting method forapproval isLazy Consensus andonly currentGroup Members are eligible tovote.
To:<OpenJDK group mailing list>Subject: CFV: New<group name> Group Member:<full name>I hereby nominate<full name> to Membership in the<group name>Group.<contributor description>Votes are due by<deadline>.Only current Members of the<group name> Group [1] are eligibleto vote on this nomination. Votes must be cast in the open byreplying to this mailing listFor Lazy Consensus voting instructions, see [2].<nominator>[1] https://openjdk.org/census[2] https://openjdk.org/groups/#member-voteWhere the following substitutions are made in the message:
Group Members vote by replying to the proposal with the firstline of the message body in the following form:
Vote:<vote>where<vote> is one ofyes,veto, orabstain. A justification for the vote may beprovided on subsequent lines, and is required in order for aveto vote to be valid. Multiple votes areallowed but only the most recent vote will be counted. Votes mustbe cast in the open, on the mailing list to which thecall-for-votes was originally sent; votes sent as private replieswill not be counted.
The following is a minimum affirmative reply.
To:<OpenJDK group mailing list>Subject: Re: CFV: New<group name> Group Member:<full name>Vote: yesOnce all Group Members have voted or the deadline has passedthen the result must be announced to the mailing list where thecall-for-votes and voting took place. If the announcement isapproval then it must also be sent to theregistrar. The registrarwill contact the new Member to obtain additional information, ifnecessary, and will update the Census.
This is a typical announcement of approval:
To:<OpenJDK mailing list>CC: registrar at openjdk dot orgSubject: Result: New<group name> Group Member:<full name>The vote for<full name> [1] is now closed.Yes:<number of "yes" votes>Veto: 0Abstain:<number of "abstain" votes>According to the Bylaws definition of Lazy Consensus, this issufficient to approve the nomination.<nominator>[1] https://mail.openjdk.org/<reference to original CFV>Where the following substitutions are made in the message:
AnyOpenJDK Member maynominate anyGroup Member orProject Committer to be an OpenJDKMember. OpenJDK Members may vote on new Project proposals andparticipate in various Governing Board-related activities, such asvoting on revisions of the Bylaws, attending open meetings, andnominating and voting for At-Large members.
As a rough guide, a candidate should be a Member of at least oneGroup, or a Reviewer or Project Lead of at least one Project, andmake regular and significant contributions to that Group or Projectfor at least one year before being nominated to be an OpenJDKMember.
The nomination and voting process for new OpenJDK Members is thesame asabove, except that thevoting method isThree-VoteConsensus.
AnyOpenJDK Member maypropose the creation of a new Group.
It is strongly recommended that any proposal for a new Group bediscussed publicly before being sent to the Governing Board. Sendan e-mail describing the motivation, scope, goals, initial Lead,and suggested initial Members of the proposed Group to thegeneral discussion list.The proposing OpenJDK Member should be an active participant in anysubsequent discussion and should refine the proposal as necessaryin response to comments.
The header for the Group proposal e-mail is as follows:
To: discuss at openjdk dot orgSubject: Group Proposal:<group name>Where<group name> is the suggestedshort name of the Group as it would appear on the left side-bar ofthe mainOpenJDK page.
Send an e-mail to theOpenJDKLead containing the Group name, description, initial Lead nameand qualifications, and suggested initial Members. The OpenJDK Lead(or designate) will send a combined motion to create the Group andappoint its initial Lead to theGoverning Board. The voting method isSimple Majority and onlycurrentGoverning Board Members areeligible to vote.
The format for the combined motion is as follows:
To: gb-discuss at openjdk dot orgSubject: CFV: New Group:<group name>On behalf of<proposer> I hereby propose creation of the<group name> Group with<lead name> as the initial Lead.<group description><lead description><list of suggested initial members>Only current Governing Board Members[1] are eligible to vote onthis motion. Votes must be cast in the open by replying to thismailing list.For Simple Majority voting instructions, see [2].<OpenJDK Lead>[1] https://openjdk.org/census#gb[2] https://openjdk.org/groups/#new-group-voteWhere the following substitutions are made in the message:
The Bylaws specify separate votes on the creation of a new Groupand the appointment of its initial Lead. Any Board Member maytherefore request that the two motions be voted upon independently,though this is not expected to be the common case.
Governing Board Members vote by replying to the proposal withthe first line of the message body in the following form:
Vote:<vote>where<vote> is one ofyes,no, orabstain. A reason for the vote may be providedon subsequent lines but is not required, even for ano. Multiple votes are allowed but only themost recent vote will be counted. Votes must be cast in the open;votes sent as private replies will not be counted.
The following is a minimum affirmative reply:
To: gb-discuss at openjdk dot orgSubject: Re: CFV: New Group:<group name>Vote: yesOnce all Governing Board Members have voted or the deadline haspassed, the OpenJDK Lead will send results to theannouncement list. If theannouncements are of approval then they must also be sent to theregistrar.
This is a typical announcement of approval:
To: announce at openjdk dot orgCC: registrar at openjdk dot orgSubject: Result: New Group:<group name>Voting on the<group name> Group with initial Lead<lead name> [1]is now closed.Yes:<number of "yes" votes>No:<number of "no" votes>Abstain:<number of "abstain" votes>According to the Bylaws definition of Simple Majority, this issufficient to approve the new Group and its initial Lead.<OpenJDK Lead>[1] https://mail.openjdk.org/<reference to original CFV>Where the following substitutions are made in the message:
The registrar will send an e-mail questionnaire to the new GroupLead to collect any information necessary to launch the Group onOpenJDK. In addition to information for web pages and mailinglist(s) the Lead will be asked to select the initial Group Members.The registrar will issue registration invitations as necessary andwill update the Census.
AnyOpenJDK Member maynominate any OpenJDK Member who is a Member of a particularGroup to be thatGroup's new Lead.
As a rough guide, a candidate should be regularly active in theGroup for at least a year before being nominated to be the Lead.They should be recognized for their technical breadth andleadership skills.
Send a call-for-votes to the Group's OpenJDKmailing list. The voting method forapproval isSimple Majorityand only currentGroup Members areeligible to vote.
To:<OpenJDK group mailing list>Subject: CFV: New<group name> Group Lead:<full name>I hereby nominate<full name> to<group name> Group Lead [1].<Group/OpenJDK Member description>Votes are due by<deadline>.Only current Members of the<group name> Group [2] are eligible tovote on this nomination. Votes must be cast in the open byreplying to this mailing list.For Simple Majority voting instructions, see [3].<nominator>[1]: https://openjdk.org/bylaws#group-lead[2]: https://openjdk.org/census[3]: https://openjdk.org/groups#lead-voteWhere the following substitutions are made in the message:
Group Members vote by replying to the proposal with the firstline of the message body in the following form:
Vote:<vote>where<vote> is eitheryes,no, orabstain. A justification for the vote may beprovided on subsequent lines, and isnot required, even forano. Multiple votes are allowed but only themost recent vote will be counted. Votes must be cast in the open,on the mailing list to which the call-for-votes was originallysent; votes sent as private replies will not be counted.
The following is a minimum affirmative reply.
To:<OpenJDK group mailing list>Subject: Re: CFV: New<group name> Group Lead:<full name>Vote: yesOnce all Group Members have voted or the deadline has passedthen the result must be announced to the mailing list where thecall-for-votes and voting took place. If the announcement isapproval then it must also be sent to theOpenJDK Lead.
This is a typical announcement of approval:
To:<OpenJDK group mailing list>,<OpenJDK Lead>Subject: Result: New<group name> Group Lead:<full name>Voting for<group name> Group Lead<lead name> [1] is now closed.Yes:<number of "yes" votes>No:<number of "no" votes>Abstain:<number of "abstain" votes>According to the Bylaws definition of Simple Majority, this issufficient to approve the new Group Lead. The OpenJDK Lead willask the Governing Board to ratify this nomination.<nominator>[1] https://mail.openjdk.org/<reference to original CFV>Where the following substitutions are made in the message:
The nomination and voting process for the Governing Board toratify a the new Group Lead is the same asabove. Sending the results of approval to theOpenJDK Lead is sufficient totrigger the appropriate Governing Board vote. If the ratificationannouncement is of approval, it will be sent to the Group inaddition to theannouncement list.