On Jul 11, 2011, at 10:46 AM, Dominic Lowe wrote: > On 11/07/11 15:13, [email protected] wrote: >> >> >>> -----Original Message----- >>> From: [email protected] >>> [mailto:[email protected]] On Behalf Of >>> Sean Gillies >>> Sent: Saturday, 09 July 2011 16:07 >>> To: gispython.org community projects >>> Subject: [Community] Future of gispython.org repositories >>> Dear OWSLib developers: would you be >>> willing to take the project to Google Code or OSGeo (to keep >>> SVN) or to GitHub or Bitbucket (necessarily switching RCS) in >>> the next month or so? >>> >> I can't speak for Dom, but my pref would be OSGeo infrastructure to keep >> a similar infrastructure (I'll ask). OWSLib has (at least) to projects >> tied to it (pycsw, qgcsw) which both use svn:externals to pull in OWSLib >> trunk. Having said this, I would not be against other ideas. >> >> ..Tom > > I would be happy with joining up with OSGeo and I think it could be a good > thing for OWSLib - however my understanding is that the OSGeo incubation > process will be more demanding than signing up with googlecode or github. We > have to meet various acceptance criteria etc.
There's no need to incubate to move to OSGeo's infrastructure. You just need to find someone on the OSGeo System Administration Committee to help bootstrap your project migration. You can even join SAC yourself and make it happen. In my opinion, github's a better solution to allow wider friction-free contribution than OSGeo. Centralized source control is an evolutionary dead end. OSGeo taking on SVN/Trac in 2006 made much more sense then than it does now. Howard _______________________________________________ Community mailing list [email protected] http://lists.gispython.org/mailman/listinfo/community
