The developers guide covers the process; 1. You read the developers guide so we have some confidence you won't break the build and know about test cases etc... 2. You submit a couple patches and get them past a module maintainer or project management committee member. You just submitted two and they seem sane. 3. A PMC member nominates you 4. We send an email to [EMAIL PROTECTED] 5. NEW! Ask you to sign the GeoTools Contributor Agreement
As for your bugs; I checked them on trunk: GEOT-1748 This bug sill existed on trunk GEOT-1742 Had been fixed already I will log-in to #geotools IRC if you have any questions about the developers guide. Jody >>> http://jira.codehaus.org/browse/GEOT-1742 >>> >>> I'd appreciate if somebody can fix them quickly. The fix is pretty >>> simple. >>> >>> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> Geotools-gt2-users mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users >> >> >> > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Geotools-gt2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
