the project vision, etc.</li>
<li>Use POI a bit, look for gaps in the documentation and examples.</li>
<li>Join the mail lists and share your knowledge with others.</li>
- <li>Get <link href="http://jakarta.apache.org/site/cvsindex.html">CVS</link> and check out the POI source tree</li>
+ <li>Get <link href="http://jakarta.apache.org/site/cvsindex.html">Subversion</link> and check out the POI source tree</li>
<li>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.</li>
<li>Get used to building POI, you'll be doing it a lot, be one with the build, know its targets, etc.</li>
<li>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.</li>
</section>
<section><title>Submitting Patches</title>
<p>
- Create patches by getting the latest sources from CVS (the HEAD).
+ Create patches by getting the latest sources from Subversion.
Alter or add files as appropriate. Then, from the jakarta-poi directiory,
- type cvs diff -u > mypatch.patch. This will capture all of your changes
+ type svn diff > mypatch.patch. This will capture all of your changes
in a patch file of the appropriate format. Next, if you've added any
files, create an archive (tar.bz2 preferred as its the smallest) in a
path-preserving archive format, relative to your jakarta-poi directory.
- (Note: If you use <link href="http://www.wincvs.org/">WinCVS</link>, move to
- [Admin] -> [Command Line] Menu and type "cvs diff -u" at
- [Enter a cvs line command] input field ([Commandline Settings] Tab),
- while selecting the target directories or files, in order to create
- unified diffs.
- In other words, [Alt+A]+[Alt+C]+[Alt+C] and type "cvs diff -u".)
You'll attach both files in the next step.
</p>
<p>