On 01/22/2011 07:06 AM, Darren Dale wrote: > On Sat, Jan 22, 2011 at 11:55 AM, Benjamin Root<ben...@ou...> wrote: >> On Sat, Jan 22, 2011 at 10:26 AM, Darren Dale<dsd...@gm...> wrote: >>> >>> On Sat, Jan 22, 2011 at 9:09 AM, Friedrich Romstedt >>> <fri...@gm...> wrote: >>>> Hi, >>>> >>>> I want to set up a git mirror for matplotlib, but I 1) have some minor >>>> problems and 2) want to know what others think about this. >>> >>> Late last year, I did some work to convert the svn repository to git. >>> The code to d the conversion is available at >>> https://github.com/darrendale/mpl2git . The resulting git repo is >>> available at https://github.com/darrendale/matplotlib . I have not >>> pursued the project further because there did not seem to be enough >>> interest in migrating from svn/sourceforge to git/github to justify >>> investing more of my time in the project. >>> >>>> I'm a native git user and I don't know how to use svn properly. >>> >>> I read that as "uninterested in learning how to use svn", and such >>> sentiment is probably a fact of life as many (most?) open source >>> projects move to DVC. In my opinion, matplotlib is likely to draw more >>> contributors if it lowers barriers to entry and uses a DVCS that is >>> growing in popularity, like git/github. >>> >>> Darren >>> >> >> In discussions with Ryan May on the prospect of switching over to git, it >> sounds like we have a "Bike Shed" problem where we (the main developers) >> agree that we agree that a bike shed should be built, but we can't agree on >> the color to paint it... > > In my view, the issue has nothing to do with bikeshedding. Agreed. We *did* agree to move to git, and the only problem was that most of us lack the expertise and time to be of much help in actually getting it done. I think there was a bit of a hangup over the question of migrating the bug tracking; but I suspect we could agree that this is a secondary question, and that any such migration, if desired, can be done at leisure *after* taking the primary step of switching the code repo. > >> I think the main source of the huge download size is the data that is coming >> from the basemap toolkit. I do not think that it would be a good thing to >> have everyone and their mother needing to do a 'git clone' on their computer >> and find they have to pull down 500+ MB of stuff to get matplotlib. It is >> because of this that a straight-forward migration from svn to matplotlib >> won't be possible. > > The git repo at https://github.com/darrendale/matplotlib does not > include anything from basemap. The key point being that you are converting matplotlib/trunk/matplotlib, not matplotlib/trunk; the latter is what includes py4science, toolkits (including basemap), sample_data, etc. I think this is the right approach. This doesn't all have to be perfect; it just has to be good enough. I suspect your conversion is good enough. If you are reasonably confident, then I think that if you go ahead and set up a github repo as the new official source tree, along with posting whatever notices are needed for anyone accessing the svn tree, the active developers will say "thank you!", and it will be done. The other person who has been most interested in the nuts and bolts of the conversion is Andrew Straw. Although he is evidently very short of mpl time these days, you might want to try to contact him directly to see if he has thought of anything you might have overlooked. I would like to be included in the group with git write access, unless there is a clear decision to restrict this group to a very small core of gatekeepers. Eric > >> What have been the proposed solutions to dealing with basemap's data? > > Separate repo? >