+1. I think, for the purpose of migrating, something trac/svn would be suitable, and we can look at git down the road if the requirement evolves. Any objections to this? If none, then it's either googlecode or osgeo. I would prefer osgeo, but we need SAC hands to help out, or someone can sign up for SAC and do it themselves. Any interested volunteers?
..Tom > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of > Dominic Lowe > Sent: Tuesday, 12 July 2011 04:09 > To: [email protected] > Subject: Re: [Community] Future of gispython.org repositories > > That sounds good to me. > > Dom > > On 11 Jul 2011 18:52, <[email protected]> wrote: > > > > On Mon, Jul 11, 2011 at 9:57 AM, Dominic Lowe > <[email protected]> wrote: > > On 11/07/11 16:49, ... > > Dom, Tom: > > How about this for a schedule: > > 7/22: new home picked and initialized > 7/22-7/29: svnsync to new home (example > > http://code.google.com/p/support/wiki/SubversionFAQ#How_do_I_i > mport_an_existing_Subversion_repository?), > dump owslib component tickets from Trac db to an SQL file. > 7/29: redirect OWSLib wiki traffic to new home > > -- > Sean > > > _______________________________________________ > Community mailing list > [email protected]... > > -- > Scanned by iCritical. > > > _______________________________________________ Community mailing list [email protected] http://lists.gispython.org/mailman/listinfo/community
