Engineering Community Team/Meetings

ECT meetings

 * Quim: would like to work more as a team. We're working well as individuals at the moment, and it's working well overall, but we might be able to work even better together


 * Also, we ought to work more closely with liaisons, community advocacy and the communications team


 * And work more closely with "the community" (discussion about what this entails exactly)


 * monthly check-in: what did we do, and what would we like to do. (reuse monthly report?)
 * i.e. like quarterly review, but more lightweight and monthly. Also relates to Rob's wish of getting that monthly showcase of what was done
 * And liaisons / LCA / Comms could be invited to that monthly retrospective / sync-up
 * One public Google hangout per month; one week later office hour on IRC

Quarterly goals
https://www.mediawiki.org/wiki/Wikimedia_Engineering/2013-14_Goals#Wikimedia_Technical_Community

Guillaume:
 * Provide ongoing communications support (blog post reviews, activity pages, etc.)
 * Assemble and publish monthly reports
 * Revive tech news and try to assemble a team of volunteers
 * Experiment with "bug of the week" engagement on social media? (and other small experiments we discussed in SF: https://commons.wikimedia.org/wiki/File:Sustainability_tech_contributors.png )

Andre:
 * Make "guided bug report form" usable for Bugzilla newbies (inherit feedback from design team)
 * Provide a NEEDINFO flag in Bugzilla (understand why the code does not work currently)
 * Think about better Bugzilla taxonomy (products/components structure) and identify some initial non-controversial tasks
 * Get "bug of the week" started (kind of rebooting "Annoying little bugs")
 * Also see https://www.mediawiki.org/wiki/Bug_management/Task_list#Plans_for_Q4.2F2013 for full list of plans

Monthly goals
Guillaume (chronologically):
 * Publish the engineering report for September
 * Follow up on outstanding requests (e.g. blog post reviews)
 * Finish to assemble and publish the tech newsletter
 * Rest!
 * Catch up
 * Assemble and publish tech newsletter
 * Start drafting the engineering report for October
 * Plan the activities for the next month