We discussed providing you with geotools commit access on the IRC disscussion
today. (The logs should be posted at http://geotools.org soon).
It has been noted that your Legend code looks promising and with a little
cleanup it will be great to add it back into the geotools code base.
Before adding a person to be a committer, we would like to ensure the person
is committed to keeping a level of quality. These standards are written down
in our developer's guide. http://geotools.org/gt2docs/
If you are prepared to make a few code changes (as mentioned in my last code
review email) then we would like to add you as a committer.
These changes include:
1. Ensuring your code compiles with maven.
2. Using jalopy for code formatting (as per developer's guide configuration).
3. Ensuring javadocs are maintained.
4. Remove references to netbeans from code.
Before code will be added to a release, it will also need unit tests.
If you make the suggested changes 1-4, then send to geotools-devel, the
Project Management Committee will review code, then vote on inviting you to
become a geotools committer.
Jin, Ian Turon, I note you both work at Leeds. Do you know each other? It may
be worth looking each other up for a chat?
I hope you take up this offer. You have some good code that would be great to
add back into the geotools codebase.
Cameron Shorter http://cameron.shorter.net
Open Source Developer http://generguide.sourceforge.nethttp://mapbuilder.sourceforge.nethttp://geotools.org
Senior Software Engineer http://www.adi-limited.com