I wrote up some quick documentation on OpenID as a provider. Feel free to
modify it, especially for inaccurately used terminology. It's also likely a
good time to start bikeshed discussions on the urls, as I think it'll end
up taking a while to lock that down.
After the discussion last week, I want to scope out a release policy so
that we'll all know what to expect.
* A major release will be made every six months.
* An LTS release will be made every two years. There will be a one-year
overlap in LTS support. For example, 1.19 is supported until May 2015.
1.23 will be released the year before that so that people will have 1.23
available as an LTS to move to and a year to make the transition.
* Releases notes will continue to be the basis for seeing what has
changed. Because of the nature of a volunteer-driven project, it isn't
possible to say with any certainty what *will* happen in the next 6-12
* To mitigate the problem of release notes, we will publish a list of
new features in the upcoming LTS relative to the last LTS six months
before it comes out. This means that about the time when 1.22 comes
out, we'll have an announcement for 1.19 users letting them know what
changes they can expect in 1.23.
* Point releases will be made periodically. Frequency TBD. Every point
release will include updated i18n files as well as any bug fixes. No
new features will be back-ported to point releases.
There is no path to peace. Peace is the path.
-- Mahatma Gandhi, "Non-Violence in Peace and War"
Just yesterday I managed to get https://gerrit.wikimedia.org/r/#/c/49776/ merged. Based heavily on Tim's work on the IcuCollation, it allows one to *finally* get articles to be correctly sorted on category pages for 67 languages based in latin, greek and cyrillic alphabets.
I also created https://bugzilla.wikimedia.org/show_bug.cgi?id=45443 to track the process of getting this deployed to Wikimedia wikis. The process is already underway for uk.wiki and pl.wiki; if anybody technical wishes to get it on their wiki first, please create a sub-bug and start a community discussion/vote - I can provide a testwiki in your language :)
Eventually, I'd like this to be deployed on all wikis in those 67 languages. I'll start poking people about this (and will drop a mail to -ambassadors) once wmf11 is deployed and the change goes live on a few wikis.
This is your weekly preview of higher-risk or general "you should be
aware of" items for the slew of deployments coming in the near term.
== Next week ==
* Monday March 4: first deploy of -wmf11 to production WMF cluster
** General MediaWiki deploy schedule for reference:
* Wednesday March 6th: Wikidata Clients to all Wikipedias
== Near Term (Planned, may change) ==
* March 13th: Scribunto (Lua) to all Wikis
* March 27th: Wikidata phase II to Hungarian, Hebrew, Italian Wikipedias
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |
We updated Gerrit this morning to 2.5.2-1506-g278aa9a. This is a
minor update to fix a couple of issues we spotted in the previous
upgrade. Downtime was less than 5 minutes.
As always, please let me know or file a bug if you're having any
Seems my previous updates on this may not have made it to this list, so
here's another update:
The wikitech dump was rather large and had a lot of revisions (60k
revisions), even though it has a fairly small number of pages (1,600
pages). The dump was about 6.1GB. The vast majority of these revisions are
from the Server Admin log.
Importing this is taking quite a bit longer than anticipated. Until the
import is complete, the wikitech documentation is still available at
http://wikitech-old.wikimedia.org. When the import finishes, I'll be
re-logging any !log messages from the channel that were missed.
Until this happens, the !log messages can be found in the IRC channel logs:
Off list: mind sharing that pad with me? :)
Sent from my phone, please excuse brevity.
On Feb 28, 2013 5:31 PM, "Matthew Flaschen" <mflaschen(a)wikimedia.org> wrote:
> On 02/28/2013 05:35 PM, Faidon Liambotis wrote:
> > I've been in quite important meetings with 15+ attendants where Etherpad
> > Lite has been used exclusively -- so, clearly not for purposes that are
> > testing or staging. So, Labs is the wrong place to have this. Can you
> > coordinate with us (operations team) to move the service into a
> > production environment?
> Agreed. We use this to track deploys for instance.
> Matt Flaschen
> Wikitech-l mailing list
as Gry in #wikipedia recently mentioned, there is no IRC channel for
general wikimedia developer purposes - project wide and language wide.
There are subchannels for certain projects, but no general channel for
wikimedia devs of all kinds from all projects.
I suppose we could use #wikimedia-dev as a general channel for all
developers no matter of project or programming language. What do you
Bellow is a message written by Gry who doesn't want to be part of this
------- from gry@irc://irc.freenode.net/#wikipedia ---------
Could we make an IRC channel dedicated to development of software for
wikimedia projects (bots, js tools like twinkle, irc bots, etc)? Some
people who work on some software for few wikimedia projects would
likely benefit if they had a place to discuss its implementation,
other than just ask #wikipedia (the largest channel of all). As the
questions may get more tricky at times, a smaller, more
development-minded channel could be a tad more effective at actually
helping (regardless of what project they're from, be that wikipedia or
wikibooks or something else).
There currently is #wikimedia-dev which actually is a place for
#mediawiki devs to meet, but they're not too happy with two channels
either  and it could be possible to discuss a take over. Or
otherwise a new channel named, say, #wikimedia-devel.
 http://bots.wmflabs.org/~wm-bot/logs/%23mediawiki/20130123.txt from 12:59
The Etherpad Lite server at http://etherpad.wmflabs.org/pad has been surprisingly popular of late, which has revealed an issue in our version. I think the issue has been fixed in the latest version of Etherpad Lite, so I'm going to hastily schedule a deployment in two hours' time. Please be aware that if you're editing a pad at that time, you may lose work.
In all the upgrade should take no longer than an hour, and I'll ping the list when it's done with.
As absurd as this is for me to be sending out a warning about taking down a labs service, this seems appropriately courteous especially given the amount of use this instance has been getting.