TLDR meeting, 14 Feb 2012
Attending: Guillaume, Mark, Sumana, RobLa, Chris McMahon
List of projectsEdit
- 1.19 stuff: Code review meistering
- 1.19 stuff: deployment & release support
- SWIFT deployment support
- Bug Triage
- Individual developer assignment work (what bugs are assigned to whom)
- Bugzilla application management
- Wikimedia blog maintenance
- Training documentation
- Monthly report
- Communications support
- Engineering project documentation
- Hackathons/events (January SF, Pune, Berlin)
- Conferences in general
- Commit Access
- Dev community metrics
Who's doing what (this week)Edit
Chris: 1.19 deployment testing
Mark: 1.19 Deployment support, bug triage
Guillaume: communications support, engineering project documentation, 1.19 communications
RobLa: Recruiting/hiring, 1.19 deployment
Sumana: Commit access, volunteer recruiting and encouragement (including GSoC and UCOSP), hackathons and events/conferences in general, engineering project documentation (git),
1.19 stuff: Code review meisteringEdit
yes, some still needs to happen. Rev report is still useful https://www.mediawiki.org/wiki/ MediaWiki_roadmap/1.19/Revision_report We’re not too worried about what is in here. This will happen in daily 20% meetings. Rob & Mark.
1.19 stuff: deployment & release supportEdit
Last night: deployed to test2.
Still errors code 500. Not sure it’s useful to tell people to test it yet.
Chris: 1.19 test planning, starting work on test2. (Anything in need of investigation please add to http://www.mediawiki.org/wiki/MediaWiki_1.19/Feature_Test_Charters)
Messages*.php investigating discrepancies between 1.18 and 1.19, asking questions. (discovered misuse of $1, $2 etc. variables, arrays of different values and different lengths, but don’t know consequences of these) (i18n). Chris should talk to Siebrand and Niklas, the translation team, Mark suggests. RobLa notes that Sam Reed or nearly any of the developers, any of the frequent committers, would be able to give details on that.
Prioritywise, now that we have test2 up, the test2 stuff is probably more urgent right now. But this issue will affect the 1.19 deployment. Example: there is a namespace issue...
RobLa & Chris to talk more in IRC.
Chris adds that his first attempt to create a user on test2 this morning failed
Swift issues (below) delay deployment to next stage, since we need to fix them AND do debugging on test 2 issues.
Mark: ● Test2 testing ○ Some really awful CSS and blank pages seen already this AM ● Beginning watching village pumps and stuff on deployed wikis. ● Getting new 1.19 specific bugs (hopefully none) fixed.
- Doing all sorts of communications planning at:
https://www.mediawiki.org/wiki/MediaWiki_1.19/Communications now mostly done; updating translations as they come in. Real-time stuff will be handled by Rob & Tilman (Did this communication have any effect on getting more testing? We don’t know.)
SWIFT deployment supportEdit
Caused test2 issues; PediaPress/PDF creator stuff caused problems. Image corruption problem in Swift discovered by the PDF generation people. But they didn’t tell us. Invalidated our cache, slammed our servers. Burden fell on Ben & Aaron. We may end up reverting Swift!
(Collections was disabled for about 4 hours on Monday.)
None planned, focused on 1.19 rollout. But we’ll get a bunch of test2 reports to triage early this week, ASAP (hopefully), and we’ll get deployment-related comments & reports to triage. ○ We haven’t postponed the first deployment window yet. So RobLa wants to plan to do this very soon thereafter.
Mark to plan this.
Individual developer assignment work (what bugs are assigned to whom)Edit
Continuing to do this in 20% standups which seem really successful
Bugzilla application managementEdit
Ask Rusty Burchfield (gicode) to get something going with git integration?
Wikimedia blog maintenanceEdit
On hold last week and this week
On hold last week and this week
Sumana created a Tutorials category on mw.o bawolff interested in making a new tutorial
no events coming up in the coming months
The January report is (finally) out: https://www.mediawiki.org/wiki/ Wikimedia_engineering_report/2012/January
Please continue to add status updates to your project regularly to make the February report less painful: https://www.mediawiki.org/wiki/Wikimedia_Platform_Engineering
- blog posts writing & review (Open Advice, Ben’s swift post, 1.19 announcement)
- drafting the SOPA tech retrospective for Erik http://etherpad.wikimedia.org/
Engineering project documentationEdit
- reorganized and cleaned up the Roadmap page: https://www.mediawiki.org/wiki/Roadmap
- perennial project page maintenance
- Helping Chad write git blog post http://etherpad.wikimedia.org/Git-Feb13
Hackathons/events (January SF, Pune, Berlin)Edit
- Follow-up on Pune event (7-19 promising volunteers)
- Follow-up for San Francisco event (including posting SF hackathon postmortem)
- Possible Brazil event
- Planning for Wikidata / structured data part of Berlin event
= Conferences in generalEdit
- this week: sumana reaching out to people who are not part of the 1.19 team, to encourage
them to submit proposals, etc. Wikimania, Opensourcebridge, and Grace Hopper conference
Sumana responding on mailing lists, etc.
Dev community metricsEdit
Sumana will aim to work with Claudia this week to show her the existing spreadsheet & wishlist - ½ hour
Communicating with Gadgets creators: https://www.mediawiki.org/wiki/ Thread:Talk:MediaWiki_1.19/Reference_tooltips/reply_(10) but what communication fora do they already use? We could update Timo’s page re using RL and create a link to a place where they can talk to each other. Create a space on mediawiki.org, use a script to ID the most prolific editors of gadgets on various wikis, send them a notification (e-mail or gadget talk page) Create a Gadget Portal on MediaWiki, Gadget Village Pumps
- Sumana to draw up TL;DR team plan for March team visit
- Guillaume in SF from March 1st to March 14th. On vacation from March 15th until March 23rd