Hi Daniel,
More inline:
On Thu, Jul 26, 2012 at 6:53 AM, Daniel Kinzler daniel@brightbyte.de wrote:
as a follow up to Jeroens mail, I'd like to give a quick overview of things that need to happen before we can roll out phase I of Wikidata on the first Wikipedia (scheduled for "late summer"). As we are approaching feature completeness, it becomes increasingly urgent to have a plan for getting the code deployed. Here's a quick list of stuff we need:
- The most urgent bit is review of the Wikidata branch, which mainly means
introducing the ContentHandler facility into core, see below.
That's filed here: https://bugzilla.wikimedia.org/38622
Assuming Tim doesn't weigh in before we speak, I'll talk to him next week about this.
- The whole Wikibase code (3 extensions: repo, client and shared code in lib)
needs a review (the repo ist the least critical, since it will not be deployed on Wikipedias). It's fairly large and could use a good looking over by anyone who could spare a few minutes. If the code is unclear or confusing, also let us know.
A bug in Bugzilla per extension would be helpful (e.g. "Review the Wikibase repo extension for deployment"). Each bug should have a very brief explanation of what the role of that extension is and a link to the repo.
I imagine the same person will review them all, but we may decide to break it up, so separate bugs would probably be best.
I suggest to file any problem you find on bugzilla (in the misleadingly named WikidataRepo or WikidataClient extensions) - got a better idea?
Sounds reasonable.
- Before actual deployment, we need to test in a more-like-production
environment. Ideally, we would use a Beta-Labs project for this. What's the status of this, what's the procedure for testing a new extension there?
Let's get the core dependencies merged into master first.
About the Wikidata branch: [...] Things got a bit stuck for a bit over the last 4 weeks, because I was busy traveling to Wikimania and having a look at New York. I have picked up work on the branch last week, merged in the latest master and did some refactoring that Tim requested (moved several functions from ContentHandlers to Content).
It would be really helpful to get this review done soon, so we can code the extension against the actual current master. Also, several other projects, like Geodata, could benefit a lot from the ContentHandler stuff.
Thanks for that update. I've copied this info into bug 38622.
Note that if all else fails, the Wikidata branch could stay separate and only be deployed on the Wikidata repo wiki. The client Wikis (Wikipedias) don't need it.
That doesn't help us all that much. Even though we can theoretically deploy many MediaWiki versions now, in practical terms, we can only have 2 or 3 versions of MediaWiki on the production cluster at any given time due to the way APC caching works (currently, all Apache servers run all MediaWiki versions). So, we really need to get the Wikidata branch into master before deploying.
Please let us know what we can do support up the review process.
I've started an activity page here for the Wikidata deployment: http://www.mediawiki.org/wiki/Wikidata_deployment
I put the blockers list on that page. If you'd prefer to keep that list somewhere else (e.g. meta or Bugzilla) that's fine by me as long as it's somewhere we already generally use and have accounts. An updated and complete list of blockers along with a weekly update on the state of that list will help a ton in accelerating this, because that helps me check in with everyone in an organized way.
Thanks Rob