All, I think the git migration deserves its own thread on the devel list, so here is a start.
The full svn repo includes much more than just matplotlib: also course, htdocs, py4science, sample_data, sampledoc_tut, scipy06, toolkits, and users_guide. Before moving matplotlib, I think we should have a clear plan as to how these other parts are going to be handled. Will some or all remain as the active parts of the svn repo, with matplotlib somehow marked as invalid? Will some or all get their own github repos? My primary interest here is toolkits/basemap, but I am sure other good stuff is in there. Before the transition, it would be good to have a pointers to the simplest possible docs illustrating typical workflows after the transition; maybe one for present developers with svn access, and another for occasional contributors. Does it makes sense to retain the entire history in the new github repo, or would it be just as well to start from a later point so as to reduce the size? The entire history could still be available in a separate read-only repo, or fossilized in svn on sourceforge, or in my hg mirror. (Andrew's repo, at just under 200MB, is not prohibitively large by any means, but it is a bit hefty.) Eric ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
