cc:ed to incubator, but please reply to the discuss list...
Bob Basques wrote:
All,
I have a question about a possible way to get some smaller projects into
the system without the requirements of going full bore (as I perceive it
now) I'm not really targeting any project per se at this
This is an interesting idea. I think it would have to be a case where
an existing OSGeo project (I think what you're calling the Super
project) expects this smaller project to have an important future as a
viable OSGeo project. The PSC of the sponsoring project (say
Mapserver, Mapguide or
Hi Bob; you will find that a few of the open source projects nurture new
talent this way.
The GeoTools library has the facilities in place to allow new developers
to come online and start an unsupported module with the support of the
community. Each module in GeoTools is an entire project
An other thought on this might be a some kind of OSGeo contrib project
that is more focused on collecting projects likes Bob's into a common
repository with the hope that making these public might allow some of
them to spin-off into full blown OSGeo projects if there is enough
interest and
Frank,
Your last point would seem to work both ways. I see the idea as a way of
solidifying project integration aspects vs making them into the gooey stuff
inside of the Shell. :c)
bobb
Frank Warmerdam [EMAIL PROTECTED] wrote:
cc:ed to incubator, but please reply to the discuss
For young projects that are not ready for incubation we have previously
set up:
http://wiki.osgeo.org/wiki/OSGeo_Labs
For the rest of this topic, I think we should go back to the principles
of OSGeo and what makes it effective.
OSGeo (like Ubuntu) promotes the best of breed GeoFOSS software.
Right, I don't disagree with this. I am just saying that there are a lot
of good ideas and one man projects that will never have a large
community to support them because of marketing,
communications,visibility issues, not technical reasons, but that
doesn't mean we should throw the code away.
