 |
Governance and Roles
Governance
Portal follows a simple governance structure. Decisions are based on consensus and made in public discussion on public mailing lists. Everyone is encouraged to voice their opinion on all decisions.
Roles
There are several ways to participate in the Portal project and community, and not all of them involve contributing source code to the project! Simply installing and using the Portal, participating on mailing lists, or filing bug reports or enhancement requests are all incredibly valuable forms of participation.
An overview of the roles for participation in the Portal project are listed in the table below.
| Project Role | Description |
|---|
| Observer | A user of the project that can browse project source coce, download binaries, open and track issues (defects and enhancements), and post to public forums. |
| Contributor | A user that has signed the Sun Contributor Agreement and contributes code to the project without commit access to the source repository. A Contributor may provide bug fixes, test cases, or feature enhancements. A Contributor works with a Developer to commit changes to the source repository. |
| Developer | A user that has signed the Sun Contributor Agreement, contributes code to the project, and has access to update content in the source repository. Commit access may be restricted to those portions of the repository in which the user needs to make changes. Developers work with Contributors to review and commit their changes as appropriate. |
| Content Developer | A user that has signed the Sun Contributor Agreement and contributes web content to the project. A Content Developer has access to update web content in the source repository. |
| Project Owner | A user that is reponsible for the project's overall mission, direction, methodology, and community make-up. |
Anonymous User
Even without a java.net account you can download, install, and use this project. You can browse the content of the project website, participate in the various mailing lists, and even check out the source code using an anonymous account (username is "guest" and the password is empty).
Observer
An Observer is an individual who uses this software, participates in the community, reports bugs, makes feature requests, and offers suggestions.
- Read-only view, does not change project resources.
- Read-only access to most project resources, web content, and source code.
- Subscribes and posts to project mailing lists.
To become an Observer join the project with the role Observer.
Contributor
A Contributor is an individual who contributes to the project but does not have commit access to the source repository. Contributions can be in the form of source code patches, new code, bug reports, web content, or articles. Each Contributor is required to sign and return the Sun Contributor Agreement (SCA) form.
- Contributes to the project, such as source code, new code, web content, or articles. * Read-only view, does not change project resources. * Read-only access to most project resources, web content, and source code.
- Subscribes and posts to project mailing lists.
To become a Contributor join the project with the role project.Contributor and sign and return the Sun Contributor Agreement form.
Developer
A Developer is an individual with commit access to the source repository. Developer access is granted to Contributors who have proven their abilities and commitment by making several high-quality contributions over a period of time. A Developer is required to sign and return the Sun Contributor Agreement (SCA) form.
Each request for a Developer role will be reviewed by all Project Owners and Developers, who will discuss this request internally and then issue a response. If your Developer request is denied, we will make a best effort to describe why the request was denied including a list of prerequisites that were not met.
- Write access to project resources, web content, and source code.
- Ability to grant a Contributor the Committer role.
- Subscribes and posts to project mailing lists.
To become a Developer join the project with the role project.Contributor, sign and return the Sun Contributor Agreement form, make a contribution, and ask the Developer for commit access. The Developer will seek consensus before granting you Developer access.
Content Developer
A Content Developer is an individual who contributes to the project's web content and has commit access to the source repository web content. Each Content Developer is required to sign and return the Sun Contributor Agreement (SCA) form.
- Contributes directly to project's web content.
- Gains write access to project's web content, announcements utility, documents and files utility, and tracking component.
- Subscribes and posts to project mailing lists.
To become a Content Developer join the project with the role Content Developer and sign and return the Sun Contributor Agreement form.
Project Owner
The project has few project owners. Each Project Owner is an individual who is responsible for the project's overall mission, direction, methodology, and community make-up
- Defines the project's overall mission, direction, methodology, and community make-up.
- Gains administrative access to all project functions.
- Grants members requested permissions on project.
- Administers all project mailing lists and is default moderator on all lists.
- Administers tracking component.
- Project Owner role supersedes any other roles you may hold on a project.
Role Privileges
| Privileges | Anonymous | Observer | Contributor | Content Developer | Developer | Project Owner |
|---|
| Read documentation | Y | Y | Y | Y | Y | Y |
| Read forums | Y | Y | Y | Y | Y | Y |
| Read bug reports | Y | Y | Y | Y | Y | Y |
| Download binaries | Y | Y | Y | Y | Y | Y |
| Browse code | Y | Y | Y | Y | Y | Y |
| Check out code | Y | Y | Y | Y | Y | Y |
| Post to forums | - | Y | Y | Y | Y | Y |
| File bug reports and other issues | - | Y | Y | Y | Y | Y |
| Submit patch for code review | - | - | Y | Y | Y | Y |
| Commit project web content | - | - | - | Y | Y | Y |
| Commit code | - | - | - | - | Y | Y |
| Management of contributed patches | - | - | - | - | Y | Y |
| Update project policies | - | - | - | - | - | Y |
| Ultimate authority over the project | - | - | - | - | - | Y |
|