Meeting Notes/2016-01-25 Core Fraction
Present: Wes, TPG - Arthur & Max.
Old business
editNext steps from last time:
- Joel to write up status of core / etc discussion from today (+ notes from today) DONE
- TPG+Wes to review write-up DONE
- Joel to send email DONE
- TPG+Wes to have "socialization" meeting to plan meetings with [affected] people [e.g. directors] 1-1 as needed to get buy-in or objections
- Grace: who are "people"? Kevin: people directly affected by core fraction decisions
- David: there are people who may dissagree and people who are not responding
- Grace: Who are these people? ^
- David: will identify at already-scheduled meeting Weds Jan 27
New business
editCheck quarterly goal and milestones and identify new Epics/Tasks. The scope of work for this project is currently defined in three different places
- https://phabricator.wikimedia.org/T122838
- https://www.mediawiki.org/wiki/Engineering_teams_can_communicate_their_capacity_for_core_vs_new_work
- https://www.mediawiki.org/wiki/Team_Practices_Group/Goals/FY2016Q3
These three different definitions don't exactly match. Joel/Kevin to clean up, including removing the temporary detailed work breakdown in the mediawiki page once its contents are covered in the Phab tickets.
Milestones
edit- A documented and agreed upon definition of ‘core work’ exists https://phabricator.wikimedia.org/T122839
- In progress (see Old Business). Socialization meeting this week will move this forward.
- Product-facing teams have agreed upon method for tracking core/strategic work https://phabricator.wikimedia.org/T122841
- What exactly is the amount of tracking we are doing this quarter?
- see next goal - 1 week of testing this quarter (Q3)
- No further work needed on this goal this week
- What exactly is the amount of tracking we are doing this quarter?
- Audience-facing product teams able to produce evidence-based data about the proportion of time spent on core vs. non-core work https://phabricator.wikimedia.org/T122842
- When is anyone going to actually want to see tracking data?
- Execs might want actual data from teams covering work starting July 1 2016, which they would report in October. So we would want to do pilots earlier (e.g. Apr-Jun). (and of course our goal calls for the first pilot by the end of March 2016)
- We should plan larger, deeper tests with more teams in Q4 to support that.
- No further work needed on this goal this week.
Next Steps This Week
edit- proceed with socialization meeting
- clean up Phab/Wiki pages for tracking this project