Page MenuHomePhabricator

Technical Collaboration quarterly goals for April - June 2016
Closed, ResolvedPublic

Description

Team quarterly goals

This is the first quarter where we start the quarterly goals process from scratch as Technical Collaboration team. We don't have Community-Relations-Support and Developer-Advocacy team goals anymore.

The canonical location of the Technical Collaboration team goals for April - June 2016 is https://meta.wikimedia.org/wiki/Technical_Collaboration/Goals. They are copied here for convenience:

Individual quarterly goals

Individual goals are documented in the table below.

OwnerGoals
@AklapperT129068: Improve code contribution guidelines for patch authors; T129067: Document a structured, standardized approach for reviewing code contributions
@CKoerner_WMFT125525: Update Discovery Team pages to be more consistent and organized T127296: Better promotion of smaller tech events (Tech Talks, Office Hours, Lightning Talks...) T128109: Investigate Maps Detail Level with Communities
@ElitreT96500: Q4 personal goal: Facilitate deployment of VisualEditor at Phase 6 wikis, T130533: Q4 personal goal: start building a volunteer, cross-wiki taskforce to help with the community side of VE work
@JohanT128790: Translation strategy – act and refine, T125961: Find out where to put not strictly technical news, T133510: First draft of timeline of WMF technical development
@KeeganT131883: Communication workflows between WMF Product teams and Wikimedia communities , T130241: Goal Q4: Document decision making in communities around software , T121260: Q4 Goal: Internal work on product design and development principles and process
@MoushiraT130010: Experiment with “user interaction” consultation , T122287: Community engagement around "Read more" as a stable feature on mobile and/or desktop, T113618: Start mediawiki (kind of multilingual) Hovercards RfC
@RfarrandT131914: Technical Collaboration participation in Wikimania , T132398: Developer Summit: Research Other Venues , T132107: Publish Lessons Learned from Wikimedia Hackathon 2016
@QgilT124019: Define the Technical Collaboration annual plan FY2016-17 - T130624: Wikimania session "Analyzing conflict and possible solutions around WMF software development" - T110170: Goal: Deploy Newsletter extension in Wikimedia
@QuiddityT130095: A plan for the top ten Community Wishlist tasks driven by volunteers - T123570: Cross-wiki notifications - announcements planning - T132624: Pre-Wikimania Hackathon 2016 Content Work
@Trizek-WMFT129088: Create an easy to maintain glossary to facilitate documentation translation (help pages and technical documentation) T113490: 10 tips for communicating with communities when developing software
@Whatamidoing-WMFT129387: Inform communities about the planned outage caused by the codfw server change

Calendar

  • 7 March: department goals. If we want one of our team goals to be promoted as a Community Engagement goal, we need to push it before this deadline
  • 16 March: team goals defined -- changes are still possible as part of the internal review
  • 1 April: latest date for publication of department goals
  • 5 July: Quarterly review slides due to Maggie by end of day
  • 6 July: @Qgil and @Keegan run through slides during Community Engagement directors meeting, finalize for sending to WMF executive team that day
  • 11 July: Community Engagement quarterly review. Quarterly review slides. Technical Collaboration starts in page 16, and there is more information in the Appendices (page 41).

Related Objects

StatusSubtypeAssignedTask
ResolvedQgil
ResolvedKeegan
ResolvedKeegan
DeclinedNone
ResolvedPginer-WMF
ResolvedKeegan
ResolvedKeegan
ResolvedKeegan
ResolvedJohan
Resolved Quiddity
Resolved Moushira
Resolved Rfarrand
ResolvedQgil
ResolvedJohan
ResolvedTrizek-WMF
ResolvedAklapper
Resolvedsiebrand
Resolved Rfarrand
Resolved Rfarrand
Resolved Quiddity
ResolvedQgil
ResolvedLadsgroup
ResolvedLadsgroup
ResolvedTrizek-WMF
ResolvedAklapper
OpenNone
ResolvedTrizek-WMF
DeclinedTrizek-WMF
Resolvedmatej_suchanek
ResolvedMvolz
OpenNone
ResolvedMvolz
ResolvedTrizek-WMF
ResolvedMvolz
ResolvedNone
ResolvedMvolz
ResolvedMvolz
ResolvedAca
ResolvedMvolz
ResolvedTiven2240
ResolvedMvolz
ResolvedNone
OpenNone
OpenNone
DeclinedTrizek-WMF
ResolvedMvolz
ResolvedNone
OpenNone
ResolvedMvolz
ResolvedBUG REPORT marcella
ResolvedMvolz
ResolvedMvolz
ResolvedNone
OpenMvolz
ResolvedAklapper
Resolved Quiddity

Event Timeline

Qgil triaged this task as High priority.Mar 1 2016, 10:00 AM

The team quarterly goals are all clear now. We still have to polish some individual goals, but this is the unofficial part of this task, and it is mostly done anyway. Lowering priority and moving the task to July (quarterly review).

Qgil raised the priority of this task from Low to High.Jun 29 2016, 9:15 AM
Qgil updated the task description. (Show Details)

T131914: Technical Collaboration participation in Wikimania , DONE

T132398: Developer Summit: Research Other Venues, technically DONE but the decision has not been finalized.

T132107: Publish Lessons Learned from Wikimedia Hackathon 2016, 1/4 DONE, will prioritize

@Keegan presented the Technical Collaboration part of the Community Engagement review on my behalf (I was on vacation). For what I have heard and read, everything went fine. I have linked to the slides from the description of this task and https://meta.wikimedia.org/wiki/Technical_Collaboration/Goals

In the next quarterly review I want to do better at capturing and evaluating the work we have done, and summarizing it in a digestible way for wider consumption. If you are interested in these improvement, please join me at T132499: Review KPIs, workflows, and scorecards of the Technical Collaboration team.

Thank you to everybody who contributed to Technical Collaboration's work during the past quarter!