Hi Andrea / Jesse - catch up to your comments. What I would like out of this page is two fold: a) a checklist so that some (ie me) can to some geotools work on a schedule b) ensure we have written down what is needed (ie no new hurdles to jump when a developer is near a deadline) while at the same time not raising the bar so high that current module maintainers are discouraged
Andrea we have to ask for both since the two applications have very different needs - you can set the bar as high as uDig if you want but we will lose almost all our datastores (we need to sneak up on this requirement one step at a time). > Jesse Eichar ha scritto: > >> Just reviewed Jody's Supporting your module WIKI page. Makes sense >> to my befuddled state. Any one else have opinions? Seems to say >> that there are procedures for obtaining supported module status. I'd >> suggest other check it out since it will impact anyone trying to get >> a module into "supported" status. >> Here is the link: - http://docs.codehaus.org/display/GEOT/Supporting+your+module > Seems ok. Just don't understand why a plugin does not require the > "supported" item: > http://docs.codehaus.org/display/GEOT/Gold+Star+Quality+Assurance+Check > It does it is under the first checklist item "Visibility / Module Status" -- here it is in full. > > 1. The first step is to rate your module: > * Gold Star Quality Assurance Check > > <http://docs.codehaus.org/display/GEOT/Gold+Star+Quality+Assurance+Check> > 2. The second step is to ensure you meet the standard set for the > release: > * GeoTools 2.3 - just rate your module > * GeoTools 2.4 - three stars are required to be included > * GeoTools 2.5 - four stars are required > 3. Create a Module Matrix page: > * show project status > * list jira issues (from as many projects as possible) > > I'd would better have the plugin tested either on udig or geoserver > (that is, don't ask for both) and have the module be supported, where in > the case of a plugin should require minimal documentation (only for > things going beyond the implemented plugin API) and watching the user list. > I am confused Andrea - this page is the *definition* of a supported module ... Although I am tempted to toughen up the language a bit: "A supported module is a commitment from the PMC to the user community that this stuff will work (and we confident enough that we can fix it in a timely fashion)" Perhaps you mean in terms of bug fixes? Responding to bug reports within two weeks, make level of detail required known, and level of detail required for action known (ie make service availabl, provide unit test, support page with consulting rates) Andrea we can reword the requirement ... GeoServer and uDig are only mentioned for "plugins" * Used by GeoServer - functional, but requires additional configuration for use (example oracle) * Used by uDig - functional, with no configuration (example postgis) The interesting part being the "ease of use" ... - functional but requires additional configuration - function with no configuration GeoServer and uDig set different standards for ease of use; I was just using it as a quick example everyone would understand. > Cheers > Andrea > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Geotools-devel mailing list > Geotools-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geotools-devel > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
