Engineering Community Team/Meetings/2011-12-20

Notes for TL;DR meeting, 20 December 2011

List of projects

Wikimedia blog maintenance
Training documentation
Monthly report
Communication support
Engineering project documentation
Code review meistering
Bug Triage
- Individual dev assignment work
Bugzilla application management
Recruiting/hiring
Hackathons/events (January SF, Pune)
1.18 deployment & release support
Commit Access
Recruitment/encouragement
UCOSP
Dev community metrics

Who's doing what

Sumana -- commit access, recruitment/encouragement, code review meistering, help with training documentation, planning for January hackathon & Pune hackathon, UCOSP Guillaume - training doc, Wikimedia blog maintenance, engineering project doc Mark H - bugzilla admin, code review, bug triage, 1.18 release followup, patch review, 1.19 ramp up. Rob - Hiring, code review meistering Siebrand - not on call, Pune hackathon planning Claudia - not on call, Bugzilla database

Wikimedia blog maintenance

Guillaume added a long awaited feature to allow users in the “contributor” group to upload files. Not deployed to production yet. Working on a feature this week to link to and/or show the blog guidelines within the WordPress admin interface

Training documentation

Guillaume mostly worked on cleaning up the Code review guide, and is going to add to it tomorrow with the notes from the code review session from July 2011.

Maybe at end of week, look at CR guide to review, give comments Obviated by changes in Guillaume's schedule

Monthly report

Not much happening this week. Will start again next week and continue on the first week of January.

TODO: Sumana can ask people to add info to status pages before they leave for the year.

Communication support

stuffs

wmfstaff (not really part of Guillaume’s work)

find someone who wants to manage channel, give them IRC powers Andrew White may have signed up for that... G would like to have a role acct for it not very urgent

either backburner for Guillaume to work on in Jan or Sumana to push forward this week

Engineering project documentation

Guillaume did some cleanup on project pages & the MediaWiki roadmap/1.1x pages. RobLa made status more prominent in some project pages. Put it up at the top. The more up-to-date info you have at the top of the page, the more alive the page looks. Should be one of the first things people should read about a project, after the short description. transclusions? SwiftMedia SwiftMedia doesn’t have a summary at top of page to talk about more offline, maybe update the project page template to transclude statuses RobLa haranguing team to update statuses on their projects

Code review meistering

Mark to start sending out personal emails, after looking over what they have actually reviewed, instead of spamming everyone But 1.19 is the priority! Per the graph, we need to get back on this

Bug Triage

There is a security bug that’s looking for a release? When, not if. So, Mark to ensure other recent changes get into 1.18.1. Why so many new bugs last week? VE, android app new version... Mark looked at charts, & it looks like we are looking at exponential growth of incoming bugs What are the numbers looking like? we’re getting approx. 20 bugs a day, used to be half that.

Individual dev assignment work

Didn’t manage to do this last week -- I *think* because I became absorbed with bugs

Sumana & Mark to sprint today assignment should mean there is a plausible, credible plan that dev is working on this in the next month or so.

Bugzilla application management

Staying same, maybe pushing my patches upstream to Bugzilla? low-priority Bugzilla database to be down for 20 minutes on Wednesday.

Mark to publicize today DONE

Recruiting/hiring

[not public]

RobLa, post the blog post you wrote re MW Core! Today! DONE

Hackathons/events (January SF, Pune)

Sumana continues to prepare & recruit people

researched and discussed an anti-harassment policy for tech events

1.18 deployment & release support

Image rotation issue? Sam is continuing to work with rotatebot folks to make that work better. Backlog will naturally run its course anyway. We’ll start getting to where community won’t keep up with bot.... we have some ideas for what to do for longer-term fixes. Lesson learned in deploying this stuff. Community-developed feature we didn’t vet closely enough. There was research we could have done that we didn’t. We have been getting timid, put off deployment of some of this stuff, community-developed features, and this is why! when you consider all the stuff you have to do to make a high-quality release, lots of work. Learned & did better in VipsScaler, working with upstreams Security release - may be coming, low-priority

Commit Access

continuing - will build backlog during vacation

Sumana to schedule longer meetings in Jan to clean through queue

Recruitment/encouragement

Dev community metrics

[on hold]

Meta