On 11/17/2010 03:26 PM, Stefan Behnel wrote: > Dag Sverre Seljebotn, 17.11.2010 11:39: > >> On 11/17/2010 11:33 AM, Dag Sverre Seljebotn wrote: >> >>> On 11/17/2010 09:59 AM, Robert Bradshaw wrote: >>> >>>> So, I've been thinking about this, and one of the reasons we're using >>>> the current setup is that it requires very little administration from >>>> me, as I am essentially leaching of the sagemath.org infrastructure. >>>> Moving things to boxen would be a bit more administration on our part, >>>> but still not too bad, and I know William is a happy enough Cython >>>> user to be fine with continuing to host us :). However, I'm wondering >>>> if this would be a ripe occasion to making the leap to something like >>>> http://code.google.com. Currently, our infrastructure consists of >>>> >>>> 1. The web site >>>> 2. Trac >>>> 3. Wiki >>>> 4. Repositories >>>> 5. Buildbot >>>> 6. Mailing lists >>>> >>>> Currently we're hosting 1-5, and 6 is being hosted by codespeak.net >>>> (for cython-dev) and google (for cython-users). I think it may be >>>> worth considering moving 2-4 elsewhere, as there is little loss and >>>> they are the higher-maintenance (from an administrative point of view) >>>> items, and features such as code review tools would be nice to have as >>>> well. >>>> > I see the serious advantage of simplifying the access to bug tracker, wiki, > etc. for new users. > > However, regarding the "little loss", does anyone have experience in > migrating trac tickets to a different tracker? There's a lot of information > in the tracker that I don't want to loose, and I wouldn't like to look at > two trackers to figure out if a bug has been reported. >
+1, migrating the tracker in full automatically is a must, otherwise we can just as well stick to the old one. Of course, we can move the repositories before moving the tracker, it's not like they can become more disconnected than they already are (well, except that we may want to patch some URLs in the strings). I'm hoping we should be able to find scripts for this. All I can find in 5 minutes of Googling is the import APIs though. Both bitbucket and github has APIs, but we should look closer make sure we can both import and export tickets easily before moving the tracker IMO. I assume there's exporters for Trac and that some scripting can be done to move the content in not too many hours. > >> Forgetting about the git aspect for a moment, I'm strongly in favor of a >> DVCS-centered site. That is, +1 to bitbucket, github, gitorious, ++, and >> -1 to SourceForge, Google Code, etc. >> > I guess it's bitbucket then? Switching the VCS just because of a project > hosting site sounds like more trouble than I'm currently after. > I haven't really used bitbucket. Only one I know who tried it is Kurt; do you have an opinion? Did you switch to github only because you wanted to switch VCS, or because of the site also? Switching the repositories over is a no-brainer as it likely takes 15 minutes, but it'd be nice to know if the tracker is up to scratch etc. before thinking about 1)-3). Dag Sverre _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
