Hei David,
I am very glad that you are "pushing" us a bit.
Me and the others need to think in the next week[s] about all the
information you gave us. Could be that I have thought the rules are more
strikt than they actually are.
So what I would like to ask you is to send a reminder in 2 weeks -
As for human resources...
How many humans are involved in the following JUMP projects?
* JUMP (http://www.vividsolutions.com/JUMP/)
* Open Jump http://jump-pilot.sourceforge.net/
* jump Pilot http://jump-pilot.sourceforge.net/ (already merged?)
* Dee Jump https://wiki.deegree.org/deegreeWiki/deeJU
When we went through the process of establishing the Program Steering
Committee (PSC) required for the incubation process for the GRASS
community into OSGEO there were many of the same issues.
Perhaps talking to some of the key movers on the GRASS PSC. There is a
mentor opportunity that may exist.
It would probably be a great thing for JUMP to move into OSGeo. I
presume that this requires some level of consent from the owners of the
copyright in the code? Vivid Solutions currently has copyright over a
large part (all?) of the codebase. I don't know how they would feel
about turning th
Hei David,
I think Landon answered the question already sufficiently.
From my perspective as Co-Project leader and Co-Maintainer:
- I would like to see that OJ is an OSGEO project, but
- We simply lack any human resources to fulfill the formal requirements :(
I may note, that more or less all p
David,
We have a new user list for OpenJUMP:
[EMAIL PROTECTED]
We are trying to migrate our users to this new list.
Some of the requirements for an OSGeo project our outlines here:
http://www.osgeo.org/incubator/process/principles.html
I've been reluctant to push OpenJUMP as an OSGeo project
