When I think that a version committed by myself r90650 (marked as new)
is fully obsolete and
already replaced in my other commit r90684 (marked as fixed)
in order to save code reviewers' time,
here are my questions:
1. shall I revert the 90650 from SVN ?
2. how exactly, and what would be meaingful comment ?
3. or can I do anything else which is of help in this case?
I need to ask here, because I could not find clear instructions or
for such cases on
Sorry, now correctly cross posted.
-------- Original Message --------
Subject: WMF XML dump title case problem
Date: Sun, 26 Jun 2011 17:07:19 +0200
From: Emmanuel Engelhart <emmanuel(a)engelhart.org>
To: Mailing list for Wikimedia CH <wikimediach-l(a)lists.wikimedia.org>,
Titles should be stored in the table "page" with a first letter uppercased.
Unfortunately, it seems that we have XML dumps (and consequently
mwdumper generated SQL) containing titles with a first letter lowercased.
$bzip2 -d -c mywiktionary-20110617-pages-articles.xml.bz2 | grep
"<title>"| grep tationery | more
Is that a bug?
-----BEGIN PGP SIGNED MESSAGE-----
We are proud to announce the first stable release of the 1.17 series.
Selected changes since MediaWiki 1.16 that may be of interest:
* A new installer has been introduced. It has a wizard-style interface
which is translated into many languages. Many shortcomings in the old
installer were addressed with this rewrite. Note that it is no longer
required for the config directory to be made writable by the webserver.
Instead the generated LocalSettings.php file is offered as a download,
which you must then upload to the wiki's base directory.
* ResourceLoader, a new framework for delivering client-side resources
now delivered through the new entry point script "load.php", instead of
as static files served directly by the web server. This allows
minification, compression and client-side caching to be used more
effectively, which should provide a net performance improvement for
* Category sorting has been improved.
* Sorting is now case insensitive.
* Sub-categories, pages and files can now be paged separately.
* When several pages are given the same sort key, they sort by their
names instead of randomly.
* The lowest supported version of PHP is now 5.2.3. If necessary, please
upgrade PHP prior to upgrading MediaWiki.
* Oracle Database support has been improved, and is now ready for beta
testing. If you work in an environment where Oracle is readily
available, and you can't get access to MySQL, this may be a useful
alternative for you. Please try it out and let us know if it works for
you. Oracle support is not yet recommended for use in production.
For more information about what's new in the MediaWiki 1.17 branch, see:
Frequently asked questions about upgrading:
Changes since 1.17.0rc1:
* Fixed syntax error in generated LocalSettings.php when a non-default
user rights profile is chosen.
* (bug 29399) Fixed PostgreSQL installation when the DB user for
installation is the same as the one for web access.
* (bug 29233) Fixed failover for DB slave servers. When a DB slave
went down, an error was immediately shown to the user, instead of
trying another slave. Was broken since 1.17 beta 1.
* (bug 29278) Fixed PHP fatal error when attempting to add text to a
page via a redirect.
* (bug 29408) Fixed uploads of files with MIME types that aren't
detected by MediaWiki.
Full release notes:
Patch to previous version (1.17.0rc1):
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----
I was wondering if anyone knew if there is a list of the codes that
follow the page names in the mediawiki IRC update stream. For example
the "MB" in the following example:
20:43 <@rc-pmtpa> [[2007–08 A-League]] MB
Cydebot * (+3) Robot - Speedily moving category 2008 in Australian
football (soccer) to [[:Category:2008 in Australian association
football]] per [[WP:CFDS|CFDS]].
I'm trying to identify bots for this visualization of the updates .
Any tips or pointers would be appreciated.
I’m pleased to announce the following promotions and role changes in
engineering, effective immediately.
* Rob Lanphier is the Director of Platform Engineering.
* Tomasz Finc is the Director of Mobile and Special Projects.
* Alolita Sharma is the acting Director of Features Engineering.
Alolita has gracefully agreed to take on this role, for which we’re
kicking off a full search process.
* Mark Bergsma is now the Lead Operations Architect, reporting to CT.
* Tim Starling is now the Lead Platform Architect, reporting to Rob.
I’ll explain a bit more what these roles mean below, but first, please
join me in congratulating Rob, Tomasz, Alolita, Mark and Tim! :-)
Let me also take this opportunity to thank Danese Cooper for helping
to build and professionalize the Wikimedia Foundation engineering
organization as Wikimedia’s CTO. She also set these changes in
motion, and our overall strategy is one that we’ve begun developing
and socializing together in the last few months.
Here’s how these roles fit together. The engineering department is
principally structured into four sub-departments, each headed by a
director who is the functional manager of all people within that
* Technical Operations - CT Woo: Keep Wikimedia Foundation sites and
services running, increase uptime and performance, support code
deployments, and ensure recoverability of data and services.
* Platform Engineering - Rob Lanphier: Maintain and support the
MediaWiki platform; ensure reliability, maintainability, and
performance of our software; lead the release management process; grow
and nurture the developer community and ecosystem.
* Features Engineering - Alolita Sharma (Acting): Advance Wikimedia’s
strategic priorities by focusing resources on specific feature
projects such as the visual editor, or interventions designed to
increase editor retention.
* Mobile and Special Projects - Tomasz Finc: Advance Wikimedia’s
mobile platform and ensure that mobile devices are fully considered
across the engineering development process; execute projects with
strong overlapping requirements (e.g. offline delivery of Wikimedia
We’re also recognizing the importance of architectural engineering
leadership in the development of a mature engineering organization
(which also represents an additional career path for our distinguished
engineers beyond “become a manager”). The three architects - Tim, Mark
and Brion - will work together as follows:
* Brion Vibber, as Lead Software Architect, has key architectural
responsibility for getting MediaWiki ready to be the world’s leading
tool for mass collaboration, by enabling the development of new
technologies like the visual editor (his current priority), real-time
collaboration, improved discussion systems, etc. This also includes
architectural leadership to support bottom-up feature development.
Brion reports directly to me.
* Mark Bergsma, as Lead Operations Architect, is responsible for
creating and communicating the vision and roadmap for the
infrastructure needed to run all Wikimedia projects, for ensuring the
design/implementation of our operating environment is reliable,
scalable, supportable, secure and cost-effective, and for driving
cross-functional alignment, especially with other engineering
* Tim Starling, as Lead Platform Architect, is responsible for the
performance, stability, security and architectural cleanliness of the
MediaWiki platform. Tim is leading potentially transformative
engineering projects like the HipHop support in MediaWiki. He’s also a
key mentor to all MediaWiki developers and is keeping us honest while
we’re pursuing our feature dreams.
In addition, we’re considering the shape of product and project
management outside the Director-level leadership in the department.
Currently, Howie Fung (Senior Product Manager) and Dario Taraborelli
(Senior Research Analyst) are continuing to support our feature
development projects to ensure that 1) development is aligned with
strategic priorities, 2) we’re focusing the development on the needs
of the user, 3) we’re making data-driven decisions and working
effectively with the global wiki research community, 4) we’re engaging
with the Wikimedia editor and reader community on complex feature
I’m taking on the role of VP of Engineering and Product Development,
on an interim basis for now. We’re not going to immediately hire
either for that role or a CTO role. Thanks to Mark, Tim and Brion, we
have very strong architectural leadership in the department. Moreover,
we’ve got more than enough disruptive change as an engineering
organization to absorb for now, so we’ve decided that it doesn’t make
sense to immediately bring in a new person to lead the department.
We may decide that it’ll make sense for me to continue in this role,
or that it’ll make sense to bring in a new person 6-12 months from
now, possibly in conjunction with further structural change.
What this means, simply put, is that I’ll be organizing and supporting
the work of the engineering department as a whole, with the directors,
the product managers, Brion and Dario reporting to me, and that’ll be
how we’ll be set up for the near future. My interest is to grow a
strong, visible leadership team that’ll be on the lists and wikis and
highly responsive to the community. I’ll be suspending most of my
non-engineering-related work for the time being.
I’ll be posting more about process improvements, further discussions
about intra-departmental structure, and so forth, in coming weeks.
I’ll also be sharing an updated org chart soon for those who care
about those kinds of things. ;-)
All the best,
Deputy Director, Wikimedia Foundation
Support Free Knowledge: http://wikimediafoundation.org/wiki/Donate
A quick glance at
http://toolserver.org/~robla/crstats/crstats.118all.html late last week
showed we were making awesome progress. Today, it looks like we can
easily drop below 1000 revisions.
Robla is out this week: it would be nice to have a big surprise for him
when he returns.
Please keep up the great work. Given our progress last week, I'm hoping
that we can get below 500 revisions by this Friday.