Rob Laphier writes:
> For testing reasons, I think this would be a great thing to have.
> Don't read "I think this would be great" to mean that this is a high
> priority thing, since I can't promise this won't get stalled behind
> other priorities
Given that Chad has pointed out the un-cached nature of the gitweb
links, though, this sounds like the thing to do.
Since it sounds like the WMF is at least willing to provide the
infrastructure (Git, Jenkins and Swift), can those of us outside the WMF
who want to make this happen work with Chad, Antoine, and Ben to figure
out how we can handle the nitty-gritty work that needs to be done?
It sounds like some knowledge transfer (which I hope would be minimally
invasive) and the already-existing infrastructure would be a all that is
required from the WMF to make this happen. The rest (changes for
Jenkins) could be done by volunteers.
Human evil is not a problem. It is a mystery. It cannot be solved.
-- When Atheism Becomes a Religion, Chris Hedges
Please join me in welcoming Srikanth Lakshmanan as outreach coordinator/QA
engineer (contractor) in WMF’s Internationalization (i18n) / Localization
(L10n) engineering team. As the team’s technical liaison, Srikanth will be
actively reaching out and working with our language communities to get
feedback on new i18n/L10n features being planned or rolled out to Wikimedia
Srikanth hails from Chennai, India. He has been a Wikipedian since 2006 and
identifies himself as a wikignome (User:Logicwiki). Srikanth has provided
language support for Tamil Wiki projects and loves to file bugs (and
occasionally fix them) when he sees languages are not properly supported.
Srikanth has recently revived his blogging habit at logic10.tumblr.com. His
other interests include cycling, travelling in buses, playing table tennis
(aka ping pong). Srikanth is excited to be able to contribute his tiny bit
in making a sum of all human knowledge more accessible and helping build a
more multilingual web! Check out some of his work on Tamil scripts and
Srikanth can be reached on email at slakshmanan(a)wikimedia.org or as
@srikanthlogic on our irc channels including #mediawiki, #wikimedia-dev and
Welcome Srikanth! It is great to have you on the i18n engineering team!
Director of Engineering
As you might know, we have been making significant improvements to the beta
cluster in labs. I wanted to point out two developments of the last few
days that I think are important milestones.
First, the TimedMediaHandler extension that we've been testing in the beta
commons wiki for quite some time has moved off of the the beta cluster and
is now being installed on test2wiki in preparation for a production
deployment. Much work has gone into TMH, and this move would not have been
possible without the extensive improvements to beta commons to support TMH
development and testing.
Second, there is a working, testable version of the new Article Feedback
Tool Version 5 on the beta enwiki right now. This is the first major
user-facing extension under development to be deployed to the beta cluster.
The beta cluster will give us a much more sophisticated test and
development environment for such extensions (and their combinations) in the
very near future.
Versions of Mediawiki core and extensions are deployed to the beta cluster
directly from our git repository. This process should be automated in
the very near future. An issue with the shared file system GlusterFS has
prevented any easy or convenient automated deployment, but our GlusterFS
system is being upgraded to the latest version (pretty much any minute now)
which should make deployment directly from git much more convenient.
Thanks to Antoine Musso, Faidon Liambotis, Jan Gerber, Michael Dale, and
Matthias Mullie for all your work and all your help. The labs beta cluster
is becoming an important part our software development environment.
 http://en.wikipedia.beta.wmflabs.org/wiki/Main_Page for example