git-svn matplotlib mirror - matplotlib-devel - Matplotlib
git-svn matplotlib mirror Development matplotlib-devel Friedrich_Romstedt January 22, 2011, 2:09pm 1 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. I'm a native git user and I don't know how to use svn properly. So I try everything to avoid svn. Furthermore, I like git so much that I don't want to give it up when developing for matplotlib.
As is well-known, there *is* already a git mirror for mpl, using svnmerge.py, i.e., GitHub - astraw/matplotlib . Anyway, this repo seems to be not actively maintained for monthes. The last comit on branch trunk is from Nov 12, 2010. Yesterday I tried git-svn on the matplotlib sf repo, and it took quite a long time (already ~500 MB), but it stopped with some error message: RA layer request failed: REPORT of '/svnroot/matplotlib/!svn/vcc/default': SSL negotiation failed: Connection reset by peer ( https://matplotlib.svn.sourceforge.net ) at /usr/local/libexec/git-core/git-svn line 5061 I could imagine the sf server treated me as some DoS user.
I attach a part of the log of how I initialised the git repo (without the middle part), and also some tees of $git branch -a and $git log trunk | head -n 150. I realised that I used different options to git svn init (i.e., I used --std-layout) than stated on http://matplotlib.sourceforge.net/devel/coding_guide.html#using-git , but I cannot see why I should use --trunk=trunk/matplotlib --prefix=svn/. From the logs of $git svn fetch, it looks good.
If there is no feedback until today eve here in Germany (in ~6 hrs), I'll try again today evening to $git svn fetch some more of the repo. If there is positive feedback, I'll consider writing to the github guys to give me ~2 Gigs of storage for the mirror. If there is negative feedback, I'll consider giving the project up. Note, that it is inevitable for me to publish the mirror when Ben and I want to use it (for some project we have since a few monthes on mpl).
I would suggest to always put git changes *on top* of svn changes, so no use of $git merge trunk, but always $git rebase. This is the only way to make usable diffs which can go in into svn on sf as far as I can see. There is a general problem which will pertain all git users: Once the changes went via svn into the sf repo, they reappear on the github mirror, causing conflicts in the branches on github where they originally came from.
The solution to this would be clear, but I think there will be no way to get a consensus to switch from svn to git on mpl completely. Friedrich 01.git-svn-fetch.part.log (6.89 KB) 01.git-branch-a.log (1.3 KB) 02.git-log-trunk.part.log (5.53 KB) _Darren_Dale2 January 22, 2011, 4:26pm 2 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 ··· On Sat, Jan 22, 2011 at 9:09 AM, Friedrich Romstedt < [email protected] ...> wrote: Benjamin_Root1 January 22, 2011, 4:55pm 3 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… 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. What have been the proposed solutions to dealing with basemap’s data? Ben Root ··· On Sat, Jan 22, 2011 at 10:26 AM, Darren Dale <dsdale24@…714…> wrote: On Sat, Jan 22, 2011 at 9:09 AM, Friedrich Romstedt > > <friedrichromstedt@…716…> 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 _Darren_Dale2 January 22, 2011, 5:06pm 4 > 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. 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. What have been the proposed solutions to dealing with basemap's data? Separate repo? ··· On Sat, Jan 22, 2011 at 11:55 AM, Benjamin Root < [email protected] ...> wrote: On Sat, Jan 22, 2011 at 10:26 AM, Darren Dale < [email protected] ...> wrote: On Sat, Jan 22, 2011 at 9:09 AM, Friedrich Romstedt >> < [email protected] ...> wrote: Jason_Grout2 January 22, 2011, 6:54pm 5 +1.
There have been several times I've wanted to fix something in the documentation, and would have via github if it had been available. As it was, I sent an email to the list a
The rest of this page is on the live site.