On 09/16/2010 10:30 PM, Pauli Virtanen wrote: > Thu, 16 Sep 2010 08:58:46 +0000, Pauli Virtanen wrote: >> The next things on the TODO list: >> >> - Update any links that point to http://svn.scipy.org/svn/numpy >> or talk about SVN. >> >> E.g. numpy.org needs updating. >> >> - Put up documentation on how to contribute to Numpy via Git. >> Gitwash-generated stuff could be added to the Numpy docs. >> >> - Decide if the `numpy-svn` email list is still needed. >> Github has RSS feeds for the repositories (but it can also send >> email to the list, if we want to keep the list alive). >> >> - Core devs: create accounts on github.com and ask for push >> permissions >> to the numpy repository. >> >> Or, just push your changes to your personal forks, and send pull >> requests -- I'm sure we have enough people to handle it also this >> way. >> >> - Trac integration -- our bug DB will still stay at projects.scipy.org >> but other Trac functionality can maybe be integrated. > > And a few more: > > - Buildbot and buildslaves. Maybe easiest by using Github's SVN > interface? > > http://github.com/blog/626-announcing-svn-support
That's what I was thinking too - but it seems that the svn support is somewhat flaky. I keep getting svn: REPORT of '/cournape/numpy.git/!svn/vcc/default': 200 OK (http://svn.github.com). May be due to some network configuration, I don't know. Would be good if someone else could check, cheers, David _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
