I have only made good experiences with git and don't see how it is
less userfriendly than SVN. On the contrary, I would argue that it
allows more non-formal ways of playing with the code, forking and
branching to try out new ideas. If one wants to learn the commands as
an SVN user, http://git.or.cz/course/svn.html
might be a good start. In the light of Binaris' post that Mediawiki is
switching soon and that all projects need to be migrated until 2013 I
dont see the point of sticking with the old solution and letting
newcomers learn SVN when they will need git in the near future.
Also, using git-svn it is possible to retain the whole history, just
for fun and tests I have set up a repo here
which shows the feasibility of continuing the pywikipedia project with
git without losing any history. Of course we will not use github as
repo nor do we need to use that particular clone I created to proceed
-- indeed it might be smarter to use different git repos for the
different folders (pywikipedia, pywikiparser, spelling, threadedhttp)
and for the rewrite branch. However, even though git is a distributed
system, the import should be done only once and installed at an
authorative place (instead of having two systems in parallel). This is
mainly because multiple svn-to-git imports will not be merge-able. As
I said, this is just for fun and should be done properly later.
Whoever wants to play around with it can do a git clone
and then look at the result.
Also, install gitk it is a very powerful and just run gitk inside the
git folder and it will display the complete history. It should be
around 22 MB.
PS: if someone wants to try the import him/herself try out the following cmd
git svn clone http://svn.wikimedia.org/svnroot/pywikipedia/
On 16 February 2012 09:54, Bináris <wikiposta(a)gmail.com> wrote:
To git or not to git, that is no more the question.
The question has been simplified to when.
2012/2/16 Sumana Harihareswara <sumanah(a)wikimedia.org> on wikitech-l
If you develop MediaWiki core, or work on
extensions that the Wikimedia
Foundation deploys, you should prepare for your development workflow to
switch on the weekend of March 3rd. Instead of Subversion and the Code
Review tool at mediawiki.org
, we will be using Git and Gerrit.
If you work on an extension that the Wikimedia Foundation does not use,
or on a non-MediaWiki project hosted at svn.wikimedia.org
, you have more
time to decide. Talk it over with your community and decide whether you
would like to move to Git immediately, move to Git sometime over the
next several months, or move to another hosting provider sometime before
mid-2013. We would like to gradually migrate all projects currently on
Wikimedia's Subversion repository so that we can make all of
read-only by the middle of 2013, and thus only have to
support one source control infrastructure.
New workflow instructions, open issues, docs, etc.:
Pywikipedia-l mailing list