Phlogiston/Meeting Notes/2016-08-04 Collaboration Phlogiston

Review current Phlogiston Report and configuration
Roan: what is the growth in these Q1 projects?

Investigated. Some real bugs, possibly also Phlogiston problems. Feature request to make this clearer: Q4 categories should all be empty but are not. see bug below, which probably accounts for all of this.
 * put date added column in Open Tasks report and sort by it (after category sort).  TODO: file this as a Phab task.

What config to change?

 * Hide all Q4


 * Carve out Q1 Edit Review Improvements


 * Intersection of two projects:


 * https://phabricator.wikimedia.org/tag/edit-review-improvements/   = 2040


 * https://phabricator.wikimedia.org/tag/collab-team-q1-july-sep-2016/   = 2039


 * Hide rump (rename to "Edit Review Improvements Other")

What to change outside of Phlogiston (like team practices or Phabricator configuration)?
Phlogiston bugs:
 * https://phabricator.wikimedia.org/T132804 was removed from Q4 in April but still shows up in Q4.  Lots more like this, throwing off counts. TODO: file bug.


 * make retroactive categorization state more visible to aid understanding charts. TODO: file ticket.

Work Planning
Current Forecasts suggest no Q1 goals will come close to finishing, because growth outstrips velocity in all categories.

Is there a specific feature you want to ship this quarter?
 * quarterly goal
 * blocked from progress on quarterly goal by designer being out

Joel's suggestions: Get a clear goal, and then say no to everything that isn't part of that goal. To do this, need to be able to easily tell which things are and aren't part of the goal. So express goal in terms of binary release criteria.
 * three main things we're working on
 * new user support feed
 * make it so that people can identify good-faith users that are [struggling?]
 * anti-vandalism feed
 * new user support special page
 * Roan: lots of stuff overlapping

Less useful: "New User Support Feed"

More useful: "make it so that people can identify good-faith users that are [struggling?]"

Then use Phlogiston to spot creep and fix it in triage.

Next steps:
1) joel to tweak config

2) joel to fix bug

3) joel to fix feature request

4) Joel to write up notes better

5) Joel to book followup meeting

Nexter steps:

 * Roan to cut stuff from Q1 board


 * Joe/Roan/team to firm up Q1 goals