On 25.10.2013 10:31, Benny Malengier
Looks like things got better recently:
Also, it feels like sf is generally steering towards git as the main
scenario. Their docs and screenshots now have git as the primary
choice (see http://sourceforge.net/create/
for instance). So if we want to follow their stewardship, it feels
like we should switch! :-)
Absolutely agreed. We must provide full support to translators and
new contributors, and ensure our wiki docs are up-to-date when we
If we switch, I promise to give such support a priority. Probably we
should get back to irc hangouts during the transition time...
Here's an example of another sf project's transition guide:
It's very good for read-only scenario, but its problem is that
sometime you get into "Transaction out of date" git-svn hell trying
to dcommit when multiple people commit on multiple branches and the
mirror hasn't yet picked everything up. Still, it's so much better
than SVN that I am not going back.
The basic scenario (check-out, work, check-in) is all the same
everywhere anyhow... We'll just have to update the procedures.
The really difficult unknown here is which is going to be more
reliable as a service, sf SVN or sf git. But it feels like it will
only get better with git with time. I did a reality check with
google(sourceforge git support sucks), and I am not afraid :-)
The sf attitude about the conversion seems helpful and reassuring,
see their response in http://sourceforge.net/apps/trac/sourceforge/ticket/24534
, so I propose we go along this route (try to convert, see if it
looks good, then switch) after the release...