Engineering Community Team/March 2014 Quarterly Review

From MediaWiki.org
Jump to navigation Jump to search
Engineering Community Team Quarterly Review 03-2014.pdf

Review of the activity and plans of the Engineering Community team. For more details see our share of the Wikimedia Engineering goals, and our short term plans.

Summary[edit]

To be posted after the review on 2014-03-27.

Last Completed Quarter, October - December, 2013[edit]

Achievements[edit]

  • All this with one person less and a reorganization of the team’s way of working.

Lessons learned[edit]

  • Pairing works in a team of specialized individuals working remotely.
    • Better quality, less hesitation, steady motivation.
    • Good for special tasks, less for business-as-usual.
  • Monthly ECT Showcases contribute to short term planning and team collaboration.
  • Hiring for short contracts demanding community engagement doesn’t work.

Current Quarter, January - March, 2014[edit]

Highlights[edit]

Team overloaded[edit]

  • Only Technical communications is on target.
  • Technical collaboration tools, Documentation, and Outreach programs have good progress, are in the good track, but carry delays and/org have to sacrifice quality and analysis due to the amount and diversity of pending work.
  • The goal of Upstream collaboration could be barely started, crowdsourced to the community (who luckily answered fast).

Areas welcoming recruitment[edit]

  • Technical collaboration tools
    • IF we select Phabricator THEN Andre needs help migrating from Bugzilla, Gerrit, etc, and tuning the new infrastructure it to our needs.
    • We still need him as Bugmeister first.
  • Outreach programs
    • Quim is in execution mode; the result is less quality in his tasks, no capacity for analysis or mid term vision.
    • We need someone focusing in events, helping in programs.

Planning, April - June 2014[edit]

Big new shiny goals[edit]

  • Project Management tools plan ready for execution.
  • Architecture documentation DONE (Documentation is never done, but we can leave it in a decent state, not requiring full attention.)
  • Complete list of upstream projects with contacts.

… in addition to our goals on Google Summer of Code, FOSS Outreach Program for Women, Facebook Open Academy, and community metrics.

Bonus points[edit]

  • Data Hub (provisional name) master plan agreed, prototype available.
  • Plan for annual hackathons in India and the USA.

Questions[edit]

  • About the Data Hub, how far do we want to go promoting our API in 2014-15?
    • We need to match your expectations with our aspirations, and with resources available.
  • We keep wondering how the new Community Engagement team will affect us.

Meeting minutes[edit]