I think the original idea of what a project becoming an OSGEO project would mean has turned out to be different in reality. I know that originally a major argument against a project joining was that the projects "identity" and branding would have to be sacrificed. But it turns out that is not really the case and projects in the foundation seem able to remain autonomous, and at the same time enjoy the benefits of being part of the foundation.
I think that argument was more or less the GeoServer argument. +1 from me. -Justin Andrea Aime wrote: > Hi all, > one of the points raised quite often at the Bolsena code > sprint was that GeoServer is not part of OSGEO, and the > thing is seen as odd and/or harmful for both entities. > > That is, people ask why GeoServer is not part of OSGEO > and think that there is some "bad" reason for it, that > OSGEO thinks GeoServer is not good or the opposite. > > Given our project control structure and the community > around the project I think it would be beneficial if > we joined. > > Without any rush, we can start the incubation and take > our time thorough it. Imho it would be good for the > GeoServer image, and also good for OSGEO as well. > > What do you think? > Cheers > Andrea > -- Justin Deoliveira OpenGeo - http://opengeo.org Enterprise support for open source geospatial. ------------------------------------------------------------------------------ _______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
