+100 :D. For those not familiar there is also a SVN API for github so that make integration with existing systems pretty easy.
I have a mirror on Github of Geonetwork already because many of our projects are Geonetwork with modifications and I found maintenance was virtually impossible with SVN. Github makes it not easy but much easier and at least possible.
In addition most projects I am following are moving to Github. Geotools, uDig, Mapfish, Spring, Scala, Geoserver, OpenLayers etc…
In fact the Pull request stuff has made adding patches from external developers much easier for me in uDig and Mapfish print.
Ok, I will talk to you tuesday.
Jesse
On Fri, Mar 16, 2012 at 9:25 PM, heikki <tropicano@anonymised.com31…> wrote:
hello,
I propose we leave the SVN / Sourceforge misery and move to a more grown-up version control on GitHub.
When you’re doing a bit of a large commit, with additions, deletes and updates mixed !, and maybe more than a handful of files or more than 100K, chances are it doesn’t work, you need to kill your process, “perform a clean-up” (grrrrr), in all, it can literally take hours and dozens of separate commits to do what should have been a single, atomic action.
A rose is a rose by any other name … “subversion”, it’s a contraction of “sub-standard” and “perversion”. There !
Let’s discuss this on IRC come Tuesday and act.
regards
Heikki
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork