Projects

Projects

A Project is a collaborative effort to produce a specific artifact, which may be a body of code, or documentation, or some other material. A Project must be sponsored by one or more Groups. A Project may have web content, one or more file repositories, and one or more mailing lists.

The Bylaws define several ways for the Community to expand via Projects. A step-by-step guide is provided here for the following common cases:

• Becoming an Author
• Appointing a Contributor to be an Author
• Nominating a Contributor or Author to be a Committer
• Nominating a Committer to be a Reviewer
• Proposing a New Project

This page is a summary and interpretation of the Bylaws. If there is a conflict between this page and the Bylaws then the Bylaws are considered authoritative. Becoming an Author

Any Contributor may request the Author role by contacting the relevant Project Lead. References to at least two sponsored contributions to the Project are required. An Author receives the following privileges above those of a Contributor:

An OpenJDK username, which allows write access to the code-review server and other infrastructure services, and

The ability to create Git pull requests (PRs) which are associated with the Author's OpenJDK username.

An Author who is not a Committer still requires the assistance of a Committer to push PRs, but the Author role is nonetheless a step above being an unregistered Contributor.

Project Leads are encouraged to grant the Author role only to Contributors who appear likely to continue to contribute for some time so that they will eventually be nominated to the Committer role.

The following is the minimal message.

To: <OpenJDK Project Lead>
Subject: <project name> Author request for: <full name>

<contributor's e-mail>

<contributor's references>