Meeting Notes/2016-01-20 Core Fraction

= Old business =
 * 1) Last week: "Should we offer a summary of this discussion, and link to these notes, in the current email threads?  (Earlier decision was: No, wait another week, nothing concrete yet.)"
 * 2) Time for a summary yet?
 * 3) Yes (see below)
 * 4) Where is this discussion happening?
 * 5) "Canonical Document": https://docs.google.com/document/d/1RxM7Zt7xq6grY2bkxwk-6biMgotkx_sVFyGj1a0Y__A/edit
 * 6) "[Wmfall] Annual Plan 2016-17" https://lists.wikimedia.org/mailman/private/wmfall/2016-January/019271.html
 * 7) "[teampractices] Please help define the term "core work"" https://lists.wikimedia.org/pipermail/teampractices/2016-January/000968.html
 * 8) Why would we do this?
 * 9) manage conversation - yes, steer people to wiki page (but make sure it's ready)
 * 10) share new info - none
 * 11) test consensus/harmonize - too soon
 * 12) give sense that somebody is responsible for coordination - yes.
 * 13) Joel to send update to threads pointing to wiki

= New business =
 * 1) Locking down the requirements for this initiative
 * 2) Teams can collect per-team core/strategic fraction data with team-specific definitions for per-team purposes
 * 3) Not required this quarter for external purposes, but is the TPG goal
 * 4) Teams can report identify core/strategic fraction data as part of WMF capacity planning (annual, quarterly, strategic)
 * 5) do roleplay of core/strategic split in Annual Planning process
 * 6) Timeline: https://www.mediawiki.org/wiki/Wikimedia_Product/2016_Product_Team_Strategy
 * 7) Feb 3: "core work narrative plan" is due: Goal, top projects, milestones/results/impact (from FDC format); metrics; staffing; budget; dependencies.
 * 8) Tony collates into a presentation.
 * 9) no decisions made about budgeting at that point
 * 10) Mar 4: "Strategy work" due.
 * 11) review and collate
 * 12) review all asks.  ratios expected to be different for each department.
 * 13) March 31: present to FDC.
 * 14) budgeting happens (no SOP available; last year not a model)
 * 15) Implications: all core work is reviewed before any strategy work is reviewed.
 * 16) Could incent teams to put work important to them in "core" regardless of definition.
 * 17) Could a team lose budget because their work is strategic, not core?
 * 18) Not expected, although not completely ruled out
 * 19) Kevin: seems like current need is for teams to identify and forecast/plan along this distinction, not to track and report
 * 20) Do we (TPG) need to help teams with the definition now, or can we do that in parallel with teams preparing their core / narrative material?
 * 21) WMF can report aggregate, consistent core/strategy fraction data for external reporting purposes (3-4 use cases, e.g., IRS, grants, charity ratings - from fundraising)'
 * 22) (Future)
 * 23) other?
 * 24) Discuss here to schedule for another time: how is this discussion going with WMF org?
 * 25) What is the core use case? Does everyone understand use cases?
 * 26) Can we strategize on how to get people read and respond more? Who is strongly dissagreeing? Who is not talking yet?
 * 27) What is the "right number" to have in different contexts?
 * 28) We should have a TPG "socialization" meeting

= Next steps =
 * 1) Joel to write up status of core / etc discussion from today (+ notes from today)
 * 2) TPG+Wes to review write-up
 * 3) Joel to send email
 * 4) TPG+Wes to have "socialization" meeting to plan meetings with people 1-1 as needed to get buy-in or objections