PS: Regarding git, if you're afraid of Gerrit but
have no problem with
using a third party for hosting (Google Code in this case), you could
also try GitHub which tends to be a very friendly introduction to Git
for most people I know. Especially the concept of "pull request" is very
well thought trough there. And as a bonus, there is no dependency on
GitHub since, contrary to SVN, everybody has the entire repository so
you can work offline and maybe even one day host it elsewhere.
I'm worried about how I see *many* people suggesting to use GitHub so
eagerly. I said this before the Git migration and I will say it again.
GitHub and other sites have serious drawbacks:
* Awareness: After Git migration I barely know what is happening in
our Git repositories. Working elsewhere means you are very likely
fully isolated from the rest of the development unless you do lots and
lots of communication.
* Lack of synergy benefits: WMF offers more than just repositories:
code review, mailing lists, wikis and my favorite - i18n and l10n
support via
translatewiki.net. We at twn can easily support the
hundreds of extensions in the WMF repo because of standardization of
file location, file structure and commit access. Projects using GitHub
will have harder time getting into twn - if they even think of asking
for that.
I haven't yet seen a flee of extensions away from WMF to GitHub and
other places, but I see many other projects have started or moved
there.
I invite you to
* Tell people the benefits of using WMF repositories
* Remove any barriers of using WMF repositories
* Think of ways to how we can stay up to date with all the interesting
development that is happening and communicate back to them how awesome
they are
-Niklas
--
Niklas Laxström