[10:13:17] 6Team-Practices, 6Developer-Relations: Define Cut-off date for abandoning old changesets in our code review tool - https://phabricator.wikimedia.org/T113706#2177250 (10hashar) From the few comments on this task, seems we want to keep changes open bit rotting until they get manually abandoned or worked again un... [11:00:54] 6Team-Practices, 6Developer-Relations: Define Cut-off date for abandoning old changesets in our code review tool - https://phabricator.wikimedia.org/T113706#2177323 (10Jdlrobson) >>! In T113706#2177250, @hashar wrote: > From the few comments on this task, seems we want to keep changes open bit rotting until th... [11:02:39] 6Team-Practices, 6Developer-Relations: Define Cut-off date for abandoning old changesets in our code review tool - https://phabricator.wikimedia.org/T113706#2177324 (10Jdlrobson) (I should add that there is a difference between a patchset being open 1000 days and rebased consistently every week and a patchset... [14:38:27] 6Team-Practices, 6Developer-Relations: Define Cut-off date for abandoning old changesets in our code review tool - https://phabricator.wikimedia.org/T113706#2177640 (10JanZerebecki) No I strongly disagree. A patch that has no review should not be abandoned. Also we don't want to encourage clicking the rebase b... [14:54:59] 6Team-Practices, 6Developer-Relations: Define Cut-off date for abandoning old changesets in our code review tool - https://phabricator.wikimedia.org/T113706#2177733 (10JanZerebecki) 5Open>3declined Declining because there is no consensus for this. See https://www.mediawiki.org/wiki/User:AKlapper_%28WMF%29/... [15:50:51] 6Team-Practices, 6Developer-Relations: Define Cut-off date for abandoning old changesets in our code review tool - https://phabricator.wikimedia.org/T113706#2177996 (10greg) 5declined>3Open Reopening as I think it was a premature close. @Jdlrobson just said he was working on more information. [19:30:02] 6Team-Practices: Propose replacement for term "sprint" as used for short working sessions - https://phabricator.wikimedia.org/T131794#2178760 (10JAufrecht) [19:45:43] 6Team-Practices, 10WMF-Product-Development-Process, 10Community-Liaisons (Apr-Jun-2016): Define good practices to start working on project concepts privately - https://phabricator.wikimedia.org/T123611#2178803 (10Keegan) Just needs plugged into the forthcoming Guidelines on Community Engagement, not closing... [20:58:43] ggellerman: this weeks is a mess with schedules, so I assume our strat pairing can wait until the week after [20:59:14] meeple27: it is a mess! I am out 3 days next week, but will look for times on M or T [21:01:06] ggellerman: it could even slip a week past that if necessary [21:01:19] and/or I could try to chip away at it before then [21:01:27] meeple27: I found a time on Monday [21:01:32] cool [21:07:27] https://etherpad.wikimedia.org/p/TPG-Phab-2016-04-04 [21:22:50] 6Team-Practices, 6Community-Advocacy, 6Community-Liaisons, 6Developer-Relations: Goal: Binding code of conduct for all Wikimedia technical spaces with consequences for breaches - https://phabricator.wikimedia.org/T90908#2179158 (10Mattflaschen) We’ve gotten good participation as we’ve worked on sections of... [22:00:05] jaufrecht: Can you move our notes to wiki? [22:01:16] okay [23:26:07] meeple27: any problems with me sharing the doc with the rest of the team at this point? [23:26:27] awjr: good timing. Yes, share awa [23:26:31] away [23:26:38] :) [23:26:38] done [23:30:55] anyone know where i can find the official text of the Strategic Problem? [23:33:41] ggellerman: perhaps? ^ [23:35:42] awjr: "How do we support the organization to be effective and sustainable, while maturing to the next level and maintaining its core values?" though we never resolved variations in its interpretation [23:35:54] ty :) [23:37:23] awjr: is the doc you linked in T131100 the doc you intended to link? [23:37:46] * awjr checks [23:38:19] nope [23:38:22] good catch meeple27 thanks [23:38:57] fixed [23:41:06] cool