> -----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 > > Hi all, > > My server that hosts the gispython.org site and services runs > on Ubuntu 6.06.1 LTS, which has reached its end of life. I'm > facing a fair amount of work in migrating my personal stuff, > and more in migrating the various code repositories and trac > instances that we've been sharing. I invite you to question > with me whether migrating the gispython.org Subversion repos > and Trac instances and databases is worth the effort. > > When Kai and I started collaborating in 2005, we agreed that > Sourceforge wasn't for us. There weren't any clear > alternatives at the time (this was before OSGeo and long > before Bitbucket and GitHub) and I was fired up to learn how > to deploy Subversion, so we set up our own development > infrastructure. Now, of course, there are many excellent > alternatives to Sourceforge with features that the > gispython.org infrastructure can't match. I'm thinking > specifically of GitHub's fork and merge buttons, and Gists. > Whether you agree with them or not, to an increasingly large > crowd of programmers, it doesn't count if it's not on GitHub > (or Bitbucket or Google Code if you will). The harder I look > at migrating the gispython.org stuff, the more I think that > all we get for the price of migration is just more obscurity, > marginalization, and eventual stagnation of the projects. > > Howard has taken the Spatialindex and Rtree projects to GitHub. > Shapely is already there. The various zgeo.* packages I > propose to either move to the Pleiades SVN or merge into > Plone's collective.geo. > The only other active and therefore seriously impacted > project is OWSLib. 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 _______________________________________________ Community mailing list [email protected] http://lists.gispython.org/mailman/listinfo/community
