Eric Firing wrote: > All, > > I think the git migration deserves its own thread on the devel list, so > here is a start. > To the uninitiated - a decision is being made that MPL is moving to git and github. We hope that this move will foster greater contributions from the community and a blurring of the line between MPL committers and users.
The decision process happened off-list to keep the flames and bike-shedding minimal. Several of the core developers were consulted and we all agreed that a move to a DVCS was desirable and inevitable. We did not unanimously agree that git was best, but it was preferred by most developers over mercurial/bitbucket, the other serious contender, and neither camp voiced strong objections to the other system. > 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. > This is a good point. My preferred option is that we jettison all the stuff that is not going to be shipped with MPL 1.0 from the git repo. (More correctly - we build a git repo without that stuff ever going in.) We can keep the old svn tree around and migrate the other projects to git as desired. I think this is what's present in http://github.com/astraw/matplotlib . Or am I missing something? Another issue is whether to use github's Issue's system over SourceForge's tracker. Personally, I'm in favor of moving the issue tracking to github, but I think we should take stock of how we use the tracker as see if github's features will support that. > 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. > I agree. I think the best learning material is from github. See http://help.github.com/ and http://learn.github.com/ , for example. To get to the "a ha" feeling, I highly recommend "Git from the bottom up" by John Wiegley, available from http://ftp.newartisans.com/pub/git.from.bottom.up.pdf . This latter is what it took for me to come to a real understanding of git. Git was designed from the data structures and plumbing up, and that the rest ("porcelain" in git parlance) came later and was less the focus of initial development. Hence, the history is that git had a rougher UI from the start and other DVCSs having nicer UIs but less stable and fast repository formats. (Understanding the git model of the universe was key to me becoming really fluent in git, but according to my office mate, it's absolutely not necessary to use git for daily tasks. ) > 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.) > I can see advantages either way, but I'm in favor keeping it. Tons of MPL is undercommented, and seeing the history is extremely useful when spelunking. -Andrew ------------------------------------------------------------------------------ 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
