Contributing to OpenDS

Yesterday, we accepted our first contribution to OpenDS from a non-Sun employee. Benjamin Damm from Brighton Consulting provided a fix for Issue #616, in which the MakeLDIF tool displayed the wrong line number if an error was found in a template file. This was one of the issues that we had specifically identified as relatively straightforward and self-contained, and would be a good starting point for someone wanting to get involved. We borrowed an idea from OpenSolaris and have designated several such issues as bite-sized bugs. The list of all bite-sized bugs in the OpenDS project can be found at https://opends.dev.java.net/issues/buglist.cgi?keywords=bite_size.

If you'd like to get involved in the OpenDS project by writing code, then we think that issues like these are a great way to get your feet wet. There are a combination of bugs, features, and enhancements in this list. Many of them would require Java code, but others involve things like creating or editing shell scripts/batch files, SMF profiles, or helping integrate with external monitoring frameworks, and some of these issues don't require any previous directory experience. Of course, there are many other areas in which people can contribute but for someone first starting out with OpenDS it's probably easiest to pick something simple in order to get used to the way that we've laid out the project and the processes that we have in place.

If you want to contribute to OpenDS, then the following checklist may be helpful:
  • If you're not already, become a member of the OpenDS project. You can do that by going to https://opends.dev.java.net/servlets/ProjectMembershipRequest and request the User role. There are other roles that appear on this page, but unfortunately we don't have much control over what shows up in the list. We don't use the Observer, Developer, or Content Developer roles in our project, so please don't request them, and you'll find it's pretty unlikely that we will give out the Project Owner role so please don't request it either.

  • You can subscribe to one or more of our e-mail mailing lists at https://opends.dev.java.net/servlets/ProjectMailingListList. If you're interested in helping develop OpenDS, then the lists you might find most useful include dev (general discussion among OpenDS developers), commits (notifications of commits made into our repository), and precommit-notification (requests to review and comment on code before it gets committed).

  • Check out and build OpenDS from our repository. You can find basic instructions for checking out the code and building it in HTML form in our documentation depot. This page also contains links to the OpenDS Source Guide in OpenDocument and PDF forms, which contains a lot more detailed information.

  • Read our Contribute to OpenDS page and our Governance Model to understand the processes that we have in place.

  • Sign and submit the Sun Contributor Agreement document, which is necessary before we will accept any contributed changes. Once you have completed this, then you can send a message to contribution-request@opends.dev.java.net to request the Contributor role in the project.

Of course, there are other ways of getting involved in the project that don't involve writing code, and many of them are explained on this page.

Comments:

You and your team have put together very good documentation, it really helped to get started quickly. I'm looking forward to contributing more.

Posted by Benjamin on October 13, 2006 at 12:28 PM CDT #

Post a Comment:
Comments are closed for this entry.
About

cn_equals_directory_manager

Search

Top Tags
Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today