If you feel you have a solid understanding of the code, you might want to browse some of the open tickets and identify those which seem doable to you. That's really the best way to get started, IMO.
https://issues.apache.org/jira/browse/CASSANDRA The lack of comments does present a challenge to new developers, so you might do what you proposed and expand on those areas that are ambiguous or confusing. Just make sure you follow proper style: http://wiki.apache.org/cassandra/CodeStyle The wiki is a great resource for getting acquainted with the architecture: http://wiki.apache.org/cassandra Internals: http://wiki.apache.org/cassandra/ArchitectureInternals How to Contribute? http://wiki.apache.org/cassandra/HowToContribute -- Todd On Fri, Jun 25, 2010 at 10:58 AM, Marty Greenia <martygree...@gmail.com>wrote: > Hello Cassandra devs, > > I'm interested in becoming a contributor to the Cassandra project and was > looking for some areas in which to start on. > > I've been ramping up the code base, getting acquainted with the major > components, and I feel like there is a lack of commenting. Commenting the > code would be a good way for my to learn the system better, and I suspect > it > would also be useful for others interesting in the future. Would providing > some quality comments -- high-level descriptions for each class, more > detailed descriptions for large/ambiguous functions -- be a useful way to > start contributing? > > Thanks! > Marty >
