Anyonecanedit.org

As a quick note to those candidates who have only been involved in Wikimedia since ’08, I urge you to withdraw early. I don’t doubt your sincerity, but you simply haven’t been involved long enough.

Out of the current list of candidates, I think there’s only 2 even worth seriously considering for the board. I’ll leave that to the readers to decide who I’m talking about.

From an e-mail I received today:

Hi

We understand that you’re interested in finding a life partner and have tried to register on BharatMatrimony. But for some reason you were unable to complete your registration.

BharatMatrimony gains thousands of new members every week, one of whom might be your perfect match, but you’ll never know if you don’t complete your registration and start using the site.

I really don’t know what to say.

Just as a brief update, the maintenance-work branch is progressing quite nicely. The vast majority of the commonly used scripts have been ported thus far, and Maintenance.php is a nice powerful class with a lot of stuff to make writing maintenance scripts quick and straightforward. My todo list has gotten down to this:

• Work on FiveUpgrade/TableCleanup-related scripts. A lot of this is massively obsolete and isn’t used. Biggest hurdle to porting the rest of this stuff. Maybe tweak FiveUpgrade/TableCleanup to subclass Maintenance and clean them up?
• Cleanup docs (both maintenance.txt and inline Doxygen stuff). Also would be nice to put the standard GPL v2 license headers on all the scripts for consistency.
• Get people to test these more! The vast majority work on my local install, but there’s a few I can’t test (no memcached for one) and it needs more testing outside of my environment.

Just to reiterate (because it’s been asked of me several times), commandLine.inc is NOT going away. Existing maintenance scripts that depend on it will continue to function as-is. It may not get all the new bells and whistles that newer scripts will get by subclassing Maintenance, but they will not break.