 |
Getting access to the OSS/J projects
We have a paired public/private project for each API.
In order to get access to the OSS/J projects, you must first open an account with java.net, then ask your company representative in OSS/J to send an e-mail to:
- the Spec Lead of the API you want to have access to
Please use this template for your email:
- email-subject: "[java.net]" [add | remove | modify] "user"
- java.net id:
- First name:
- Last name:
- Company:
- User's email:
- Project:
- Access role(s):
Java.net provides the following access role levels:
| Level | Name | Document
(web content) | Code
(cvs access) | Description |
|---|
| | | read | write | read | write | |
|---|
| 0 | none | | | | | do not need access to this sub-project. |
| 1 | observer | X | | X | | typical software developer who needs to sync up with the repository and reads documents but has not ownership of code. Can also submit issues. There is no need to grant this role for public subprojects. |
| 2 | content developer | X | X | X | | gives write access to documents but no direct read access to code in cvs repository. Code can be accessed through website only. |
| 3 | developer | X | X | X | X | selected trusted individuals involved with JSRs with a clear need to contribute code and a degree of ownership of code. Please note that it is also possible to submit patches to code owners if the code change is small and infrequent i.e. not everyone needs to have developer level access. |
This boils down to the OSS/J typical role grants:
- Typical code developer: 1 (or 0 for public projects)
- Typical manager or technical document owner: 1+2
- Typical code owner: 3
After reception of the request, the project owner will update the project with the user information and will reply to the requestor.
-- AntonioPlutino - 08 Jan 2007
|