On 11 February 2012 03:51, Sumana Harihareswara <sumanah(a)wikimedia.org> wrote:
We had a meeting today to lay out some of the open
questions and the
answers. Really raw notes are at
https://www.mediawiki.org/wiki/Talk:Git/Conversion/issues#Topics_for_Chad.2…
It was so long that the email and blog post are going to happen early
next week instead. But here are some key points:
* Please stop creating new extensions in Subversion, right now. It
makes Chad's migration work more error-prone. If you want to create a
new extension in git, ask Chad and he'll help you.
Since you already are suggesting people to start git repositories, we
should prepare the i18n support right now.
Translatewiki.net is not
ready to handle random git repositories all over the world (nor it
necessarily wants to do that). MediaWIki has had very good i18n and
l10n including extensions - I don't want to lose that. So we need to
plan it now, not when we have hundreds of extensions migrated to git
and every one doing the things differently.
If our commit access is restricted (committing updated translations,
but also fixing i18n issues) we cannot do our job properly, which
means that we will start dropping support for stuff that doesn't
handle i18n adequately.
Which reminds me, does LocalisationUpdate support git? Or Extension Distributor?
* As far as Chad knows, none of the gerrit bugs listed
in
https://labsconsole.wikimedia.org/wiki/Gerrit_bugs_that_matter are bad
enough to block the migration. What, *specifically*, do people hate
about gerrit? He needs to know specifics to make decisions that might
delay the migration.
I read through almost all of the commit mails. If I need to spend any
more time on it or do more clicking around my head will probably
explode. This means that I want commit emails with links to review
tool, review tool should load fast, display all diffs inline (not
hidden behind links or anything) and I should be able to filter
commits by path or author. In addition I want to be able to tag
commits (for l10n team to review or keeping list of commits I want to
deploy to the live site). Any failure to meet these requirements is
highly likely to be a blocker for me. Oh and something that signs that
this commit has followups that fixes problems in it.
* Chad is trying to get the real git repo up and
running ASAP so people
can start doing their real work there. He and RobLa believe we should
encourage people to consider SVN indefinitely slushed. If you are going
to do large things, they prefer you start doing them in git.
We have been in a slush most of this year already and it has affected
the work of our team. We have already started to ignore the slush and
will probably do it again. On the other hand we probably will migrate
our extensions to git among the first ones.
Are extensions used by WMF forced to have the gated trunk model?
How much space do the git repos require? Right now we spend under 500M
to support the i18n of three branches of mediawiki and all extensions.
-Niklas
--
Niklas Laxström