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.
If speed is of the essence then perhaps we use something like googlecode
for now (therefore keeping SVN) with a view to OSGeo incubation over the
next few months?
Regards,
Dom
_______________________________________________
Community mailing list
[email protected]
http://lists.gispython.org/mailman/listinfo/community
--
Scanned by iCritical.
_______________________________________________
Community mailing list
[email protected]
http://lists.gispython.org/mailman/listinfo/community