There are a number of ways that you can get involved with the OpenDS project, including:
See the OpenDS Governance Model for more information about the ways in which individuals may participate in the project.
There are several mailing lists in use for this project. Most of them are open to anyone that wants to subscribe, although some of them may be restricted to specific subsets of users. See the Project Mailing Lists page to see a complete list and for information about subscribing. Note that you can subscribe to mailing lists in digest mode to keep the number of messages down.
Some of the mailing lists that we provide are:
The OpenDS issue tracker is available online at https://opends.dev.java.net/servlets/ProjectIssues. You can use it to submit new bug reports or feature requests for the OpenDS server, or to browse the list of issues that have already been filed. Anyone can query the issue tracker, although it will be necessary to have at least the User role in the project to file new requests.
Note that we have imported our feature request list for this project into the issue tracking system so that we can keep track of them and make sure that they are included in the appropriate release. If you're interested in what we have planned for the server, then the issue tracker is a good place to find out.
If you want to participate in the project by reviewing or updating the documentation or by making code changes, then you will first need to complete and submit the Sun Contributor Agreement as outlined in the OpenDS Governance Model. Once this agreement has been accepted, you can forward the confirmation to firstname.lastname@example.org to request the Contributor role. An OpenDS committer will be assigned to work with you. Individuals who have been given the Contributor role will not initially be allowed to commit changes directly into the repository, but active Contributors may be granted the Committer role over time.
After obtaining the contributor role query the issue tracker to find tasks in need of an owner. "Bite size" issues are good starting points for developers interested in getting involved. These issues should be relatively straightforward to resolve and should not require in-depth knowledge of the OpenDS codebase. To retrieve the current set of bite size issues use the keyword "bite_size". "Self contained" tasks are more substantial than bite size tasks though are more self-contained than general issues. After successfully resolving a few bite size tasks find an interesting self contained issue by entering the keyword "self_contained".
See the OpenDS Governance Model for more details about the roles that individuals may have in the OpenDS project.