Read the rest of the website, understand what POI is and what it does,
the project vision, etc.
Use POI a bit, look for gaps in the documentation and examples.
-
Join the mail lists and share your knowledge with others.
+
Join the mailing lists and share your knowledge with others.
Get Subversion and check out the POI source tree
Documentation is always the best place to start contributing, maybe you found that if the documentation just told you how to do X then it would make more sense, modify the documentation.
+
Contribute examples - if there's something people are often asking about on the user list which isn't covered in the documentation or current examples, try writing an example of this and uploading it as a patch.
Get used to building POI, you'll be doing it a lot, be one with the build, know its targets, etc.
Write Unit Tests. Great way to understand POI. Look for classes that aren't tested, or aren't tested on a public/protected method level, start there.
Download the file format documentation from Microsoft -
OLE2 Binary File Formats or
OOXML XML File Formats
Submit patches (see below) of your contributions, modifications.
-
Fill out new features, see Bug database for suggestions.
+
Check the bug database for simple problem reports, and write a patch to fix the problem
+
Add in new features, see Bug database for suggestions.
+
The Nutch project also have a very useful guide on becoming a
+ new developer in their project. While it is written for their project,
+ a large part of it will apply to POI too. You can read it at
+ http://wiki.apache.org/nutch/Becoming_A_Nutch_Developer
Read the rest of the website, understand what POI is and what it does,
the project vision, etc.
Use POI a bit, look for gaps in the documentation and examples.
-
Join the mail lists and share your knowledge with others.
+
Join the mailing lists and share your knowledge with others.
Get Subversion and check out the POI source tree
Documentation is always the best place to start contributing, maybe you found that if the documentation just told you how to do X then it would make more sense, modify the documentation.
+
Contribute examples - if there's something people are often asking about on the user list which isn't covered in the documentation or current examples, try writing an example of this and uploading it as a patch.
Get used to building POI, you'll be doing it a lot, be one with the build, know its targets, etc.
Write Unit Tests. Great way to understand POI. Look for classes that aren't tested, or aren't tested on a public/protected method level, start there.
Download the file format documentation from Microsoft -
OLE2 Binary File Formats or
OOXML XML File Formats
Submit patches (see below) of your contributions, modifications.
-
Fill out new features, see Bug database for suggestions.
+
Check the bug database for simple problem reports, and write a patch to fix the problem
+
Add in new features, see Bug database for suggestions.
+
The Nutch project also have a very useful guide on becoming a
+ new developer in their project. While it is written for their project,
+ a large part of it will apply to POI too. You can read it at
+ http://wiki.apache.org/nutch/Becoming_A_Nutch_Developer