>> 18. If you do not intend to host any portion of this project using the >> OSGeo infrastructure, why should you be considered a member project of >> the OSGeo Foundation? >> >> Do we want to make use of any osgeo infrastructure? Or are we happy with >> what we have now? If anything I might think the mailing list? I would be >> ok with svn except I don't like how the commits mailing list is set up >> and can't figure out who made a commit without opening the full email. > > Right, if we solve that switching svn would probably be the easiest. > > Switching a 800 users ml to another system can be painful, not sure > we want that. > > Another system that we could think switching may be jira to trac, > but I did not find any tool going in that direction (just the > opposite one) and we definitely don't want to switch over manually. > > As for the site, we could have a single page on OSGEO pointing to our > existing infrastructure. > > Finally, there is the file release system, which SF changes every other > day lately. Yet SF has this nice download counters and a distributed > delivery architecture. What can OSGEO offer in this respect?
Hi Guys: This is the kind of stuff we get to discuss with a mentor :-) >From previous experience none of this part matters too much; it is more in terms of if OSGeo needs to organize any hardware resources to support the project. Indeed I find the question a bit harshly worded. The inncubation process is a bit open ended; those questions are only to get the discussion going. As an example since the GeoServer community has a strong sense of brand (and a very pretty website) I expect a different discussion then MapServer (which rolled out a default sphinx style). Jody ------------------------------------------------------------------------------ _______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
