<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-15">
<META content="MSHTML 6.00.2800.1609" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Comic Sans MS">
<DIV>Frank,</DIV>
<DIV> </DIV>
<DIV>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)</DIV>
<DIV> </DIV>
<DIV>bobb</DIV>
<DIV> </DIV>
<DIV><BR><BR>>>> Frank Warmerdam <warmerdam@pobox.com> wrote:<BR></DIV>
<DIV style="PADDING-LEFT: 7px; MARGIN: 0px 0px 0px 15px; BORDER-LEFT: #050505 1px solid; BACKGROUND-COLOR: #f3f3f3">cc:ed to incubator, but please reply to the discuss list...<BR><BR>Bob Basques wrote:<BR>> All,<BR>> <BR>> I have a question about a possible way to get some smaller projects into <BR>> the system without the requirements of going full bore (as I perceive it <BR>> now) I'm not really targeting any project per se at this point, but . . .<BR>> <BR>> What about have a "Super" project that can act as a sponsor for a <BR>> smaller project. When I say smaller, I mean where there might only be <BR>> one, two or three developers. The end result being that the "Super" <BR>> project basically vouches for the smaller project in some fashion for it <BR>> to get some sort of OSGEO stamp applied to it. This could possibly be <BR>> a criteria where some of the established vetting is handled via a <BR>> voucher system, where other "Super" projects can add their credentials <BR>> to the mix over time.<BR>> <BR>> Just a thought, still a little muddled too, but it seems like there <BR>> might be something workable in the concept. Any other thoughts?<BR><BR>Bob,<BR><BR>Something like this approach has been taken for the MetaCRS project.<BR><BR> <A href="http://wiki.osgeo.org/wiki/MetaCRS">http://wiki.osgeo.org/wiki/MetaCRS</A><BR><BR>The MetaCRS effort is an attempt to have a single PSC run a sort of<BR>federation of related projects. In this case the coordinating theme<BR>is coordinate systems (reprojection, dictionaries, datum shifting,<BR>CRS description translation). But the components (CS-Map, PROJ.4,<BR>proj4js, and libgeotiff) are initially fairly independent activities with<BR>relatively few shared developers or direct cooperation.<BR><BR>In the case of MetaCRS there is an intent for them to grow somewhat<BR>closer, in particular in sharing coordinate system dictionaries.<BR><BR>Another approach would be for a smaller project to place itself under<BR>the administration of an existing official project that is somewhat related.<BR><BR>For instance, I could imagine a web framework like Chameleon that is MapServer<BR>oriented, might ask to be considered part of the MapServer project, and<BR>subject to it's PSC. I had contemplated doing this with libgeotiff within<BR>the GDAL project for a while, for instance.<BR><BR>We do need to be careful, I think, that we aren't just creating "shells"<BR>with no concept of community in order to get around the incubation process<BR>which is aimed at developing genuine well functioning communities around<BR>projects before giving them an OSGeo stamp of approval.<BR><BR>Best regards,<BR>-- <BR>---------------------------------------+--------------------------------------<BR>I set the clouds in motion - turn up | Frank Warmerdam, warmerdam@pobox.com<BR>light and sound - activate the windows | <A href="http://pobox.com/~warmerdam">http://pobox.com/~warmerdam</A><BR>and watch the world go round - Rush | Geospatial Programmer for Rent<BR><BR>_______________________________________________<BR>Discuss mailing list<BR>Discuss@lists.osgeo.org<BR><A href="http://lists.osgeo.org/mailman/listinfo/discuss">http://lists.osgeo.org/mailman/listinfo/discuss</A><BR></DIV></BODY></HTML>