I sincerely hope to get back into doing more with Habari soon, and to save that part of the discussion, as someone who's never touched Git, all I can say is if a decision is made to switch to it, which I can't say I'm adverse to, only that we give anyone like myself ample time to find _some_ project to cut our teeth on before we have to convert our many checkouts over to it. Maybe someone sets up simple project with the sole purpose of writing a tutorial for those like me we barely grok Subversion as it is.
I've sat in on several Barcamp discussions on Git, and everyone who's drank the kool-aid say the same thing, once you go Git, you never go back. I agree with the point of Owen that it would need to be under our own control and interface with Trac/something like Trac (is there such a thing?). Anyway, also as someone who's not committed a line of code in quite some time, I don't think my opinion whether to switch or not should carry much weight. I would sincerely like to hear from those who do and how a switch may or may not affect their participation. I'd hate to switch to something else trying to garner more participation only to loose those that have put so much hard work to this point because they are adverse to Git. </¢2> ~miklb On Dec 11, 4:25 pm, Owen Winkler <[email protected]> wrote: > Yeah, weird for me to be starting this fight but... > > After reading the ongoing battle over on wp-hackers, I'm curious what > the pain would be to switch entirely over to Git for core and extras SCM. > > The one requirement I have is that all the code lives centrally (heh, > the irony of "distributed" SCM) on the hp.o server, not in some > third-party hosted service. > > So, could the people who are most enamored with the idea of using Git > please explain to the rest of us crotchety old svn users what the actual > differences would be for using git for SCM? > > I'm not talking about the "oh, your merges will be so much easier" crap, > I'm talking about actual potential pain points for the switch. For > example: No solid/stable Tortoise-like client for Windows. Need to > reconfigure our server-side stuff (like Trac) to handle it. > > It will be useful to compare those things to what people stuck in svn > will actually care about in order to make a decision about what to do > and how to mitigate the damage. > > Owen -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/habari-dev
