[16:24:15] 6Team-Practices, 6Developer-Relations, 3DevRel-December-2015: Goal: Define potential actions to reduce code review queues and waiting times - https://phabricator.wikimedia.org/T101686#1848492 (10Aklapper) [16:26:48] 6Team-Practices, 6Developer-Relations: Wikimedia Foundation service-level agreement on code review times - https://phabricator.wikimedia.org/T113707#1848499 (10Aklapper) [16:26:50] 6Team-Practices, 6Developer-Relations: Define Cut-off date for abandoning old changesets in our code review tool - https://phabricator.wikimedia.org/T113706#1848500 (10Aklapper) [16:26:52] 6Team-Practices, 6Developer-Relations, 3DevRel-December-2015: Goal: Define potential actions to reduce code review queues and waiting times - https://phabricator.wikimedia.org/T101686#1848498 (10Aklapper) [16:27:18] 6Team-Practices, 6Developer-Relations, 3DevRel-December-2015: Goal: Define potential actions to reduce code review queues and waiting times - https://phabricator.wikimedia.org/T101686#1345036 (10Aklapper) [16:27:19] 6Team-Practices, 6Developer-Relations: Define Cut-off date for abandoning old changesets in our code review tool - https://phabricator.wikimedia.org/T113706#1673884 (10Aklapper) [16:27:26] 6Team-Practices, 6Developer-Relations, 3DevRel-December-2015: Goal: Define potential actions to reduce code review queues and waiting times - https://phabricator.wikimedia.org/T101686#1345036 (10Aklapper) [16:27:27] 6Team-Practices, 6Developer-Relations: Wikimedia Foundation service-level agreement on code review times - https://phabricator.wikimedia.org/T113707#1673927 (10Aklapper) [16:33:47] 6Team-Practices, 6Developer-Relations, 3DevRel-December-2015: Goal: Define potential actions to reduce code review queues and waiting times - https://phabricator.wikimedia.org/T101686#1848531 (10Aklapper) [16:37:27] 6Team-Practices, 6Developer-Relations, 3DevRel-December-2015: Goal: Define potential actions to reduce code review queues and waiting times - https://phabricator.wikimedia.org/T101686#1848544 (10Aklapper) [16:37:31] 6Team-Practices, 6Developer-Relations: Wikimedia Foundation service-level agreement on code review times - https://phabricator.wikimedia.org/T113707#1848543 (10Aklapper) [16:37:35] 6Team-Practices, 6Developer-Relations, 3DevRel-December-2015: Goal: Define potential actions to reduce code review queues and waiting times - https://phabricator.wikimedia.org/T101686#1345036 (10Aklapper) [16:45:27] 6Team-Practices, 6Developer-Relations, 3DevRel-December-2015: Goal: Define potential actions to reduce code review queues and waiting times - https://phabricator.wikimedia.org/T101686#1848563 (10Aklapper) p:5Normal>3High [17:24:33] 6Team-Practices, 7Epic: EPIC: TPG Strategy Process - https://phabricator.wikimedia.org/T113053#1848767 (10JAufrecht) [17:24:35] 6Team-Practices: [EPIC] Run Strategy Tests - https://phabricator.wikimedia.org/T117924#1848766 (10JAufrecht) [17:24:56] 6Team-Practices, 7Epic: EPIC: TPG Strategy Process - https://phabricator.wikimedia.org/T113053#1653604 (10JAufrecht) [17:24:57] 6Team-Practices: [EPIC] Run Strategy Tests - https://phabricator.wikimedia.org/T117924#1787004 (10JAufrecht) [17:25:34] What is the best way to mark tasks as Epics? [17:25:40] a) tag as Epic; don't put Epic in the title [17:25:51] b) tag as Epic; put [EPIC] at the beginning of the title [17:26:09] c) tag as Epic; put EPIC: at the beginning of the title [17:26:10] ? [17:28:32] jaufrecht: My preference would be to have Epic in the title (EPIC, [EPIC] whatever), but no tag. However, I was scolded for doing so, so I tend to put it in the title and tag it now [17:29:21] What is and is not an epic is so fuzzy for the teams I work with that we are tending not to flag them at all now [17:29:40] some tasks have subtasks, but that doesn't make them epic [18:00:51] 6Team-Practices: Create test plan for Team Practices Group strategy possibilities - https://phabricator.wikimedia.org/T117104#1849053 (10JAufrecht) [18:00:53] 6Team-Practices, 7Epic: EPIC: TPG Strategy Process - https://phabricator.wikimedia.org/T113053#1849052 (10JAufrecht) [20:36:26] 6Team-Practices: Document cost/benefit of Phlogiston and Phragile - https://phabricator.wikimedia.org/T120271#1849839 (10JAufrecht) 3NEW [20:46:21] 6Team-Practices: Document active TPG projects - Grace - https://phabricator.wikimedia.org/T119469#1849891 (10JAufrecht) [21:01:20] 6Team-Practices, 6Release-Engineering-Team: One year review of RelEng offsite outcomes (April 2016) - https://phabricator.wikimedia.org/T112763#1849971 (10greg) [22:03:57] 6Team-Practices, 7Epic, 15User-JAufrecht: [EPIC] Get some teams to pilot collecting Maintenance Fraction data - https://phabricator.wikimedia.org/T99958#1850389 (10JAufrecht) [22:04:34] 6Team-Practices: [EPIC] engage phacility and drive feature requests through upstream - https://phabricator.wikimedia.org/T117608#1850395 (10DStrine) [22:22:48] 6Team-Practices: Document active TPG projects - Grace - https://phabricator.wikimedia.org/T119469#1850634 (10JAufrecht) [22:24:28] 6Team-Practices: Document active TPG projects - https://phabricator.wikimedia.org/T119464#1850647 (10Awjrichards) p:5Triage>3Normal [22:25:23] 6Team-Practices, 7Epic, 15User-JAufrecht: EPIC: Pilot Milestone-Based Burnup usage within TPG - https://phabricator.wikimedia.org/T119473#1850654 (10JAufrecht) [22:25:48] 6Team-Practices, 7Epic, 15User-JAufrecht: [EPIC] Pilot Milestone-Based Burnup usage within TPG - https://phabricator.wikimedia.org/T119473#1827196 (10JAufrecht) [22:26:00] 6Team-Practices, 7Epic: [EPIC] TPG Strategy Process - https://phabricator.wikimedia.org/T113053#1850662 (10JAufrecht) [22:27:08] 6Team-Practices: Create position paper on Team Practices confidentiality - https://phabricator.wikimedia.org/T111449#1850666 (10Awjrichards) 5Open>3declined [22:27:28] 6Team-Practices, 3Team-Practices-This-Week: Create test plan for Team Practices Group strategy possibilities - https://phabricator.wikimedia.org/T117104#1850668 (10KLans_WMF) [23:00:00] ggellerman: I added some tests to 7 [23:00:37] sorry...not tests..."would have to bes"