Hi Stefan, +0 I think joining OSGEO should be fine for OpenJUMP (more visibility, more developpers, more users...), but I'm not sure we have enough human resources to move on. As far as I'm concerned, I have'nt contributed for a while, but I'll keep helping when I can, whatever the decision is.
Thank you so much for all the work you and Sunburned Surveyor do to keep the project in good health. Michaël Stefan Steiniger a écrit : > Dear OJ user/developer. > > I send this email to the devel list, as here rather the core people > are listening and this is also a discussion list for us. > > Now, I have read all the docs required for an OSGEO incubation. I will > attach a rather lenghtly file where I added comments to the different > questions/criteria. > > A couple of things will require some work and mentorship but I think > it would be doable to join OSGEO, as the restrictions in terms of > managements seem not to be so tight (i.e. we are require to document > the managment processes, but it is actually not said what management > rules we should implement) > > Here is a list of the major things that need to be done (see also the > very end of the text file): > > ==================================================== > Summary - Major Issues with respect to human resources > ==================================================== > required: > -------- > . document (established) license policy > . code contributors need to agree to project's license policy (written > form?). > . do a Code Provenance Review - check of licenses in the source code > (Ohloh may help here) => problem: we probably can not "GPL" or "LGPL" > (i.e. relicense) source code that has been inherited from other > projects, without the author permission (such code needs to be > externalized into a library). > . found a Steering Comittee > . establish documentation on project management procedures for PSC > decisions, contributor guidelines, etc. (see Project Graduation > Checklist point B3) > . start documentation of project decisions > . define release rules and process (not sure if that is a requirement) > . provide marketing material (handout, feature-matrix) > > optional: > -------- > . wiki + webpage transfer to OSGEO > . introduce automated testing system (junit) > . certification of standards? > ================================================= > > The only thing I am personally struggling is the definition of release > rules and a development plan if that is required (as this would play > against our "I contribute when I like" idea) > > I am awaiting your coments and a OJ-Joins-OSEGEO decision (+1: yes, 0: > don't know, -1 too much work) from the regular contributors, i.e. at > least an oppinion from: > Larry, Michael, Peppe, Andreas, Paul, Landon, Martin. > > I also welcome oppinions from Jukka, Jon, Paolo, Eric, Geoff, Sascha, > Lat/Lon, Intevation, Erwan, Arnd, Edgar, Ugo + Steve (if listening > ;),... and who ever wants to > > my personal vote: 0 (influenced by the work that needs to be done, > listed above) > > cheers from sunny Calgary > Stefan > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > ------------------------------------------------------------------------ > > _______________________________________________ > Jump-pilot-devel mailing list > Jump-pilot-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
