[05:53:53] 6Team-Practices, 6ArchCom, 10Architecture, 10Wikimedia-Developer-Summit-2016: Discuss and approve a MediaWiki developer community governance model - https://phabricator.wikimedia.org/T89907#1960987 (10RobLa-WMF) 5Open>3Resolved a:3RobLa-WMF {T123606} and {E135} is where this conversation continued [19:02:29] jaufrecht_: having some problems getting the hangout to load, be there ASAP [19:02:46] still writing down notes from last meeting [19:04:51] jaufrecht_: do you see me in the hangout? [19:04:59] yes, but no sound or video [19:05:04] back in 30 sec [19:06:08] just me in the chat [19:45:45] 6Team-Practices, 7Milestone: A documented and agreed upon definition of ‘core work’ exists - https://phabricator.wikimedia.org/T122839#1963046 (10JAufrecht) [19:45:47] 6Team-Practices, 7Milestone: Product-facing teams have agreed upon method for tracking core/strategic work - https://phabricator.wikimedia.org/T122841#1963045 (10JAufrecht) [19:45:59] 6Team-Practices, 7Milestone: A documented and agreed upon definition of ‘core work’ exists - https://phabricator.wikimedia.org/T122839#1915065 (10JAufrecht) [19:46:01] 6Team-Practices, 7Epic, 3TPG-2016Q3: [EPIC]Engineering teams can communicate their capacity for core vs new work - https://phabricator.wikimedia.org/T122838#1963047 (10JAufrecht) [20:36:44] 6Team-Practices, 7Milestone: A documented and agreed upon definition of ‘core work’ exists - https://phabricator.wikimedia.org/T122839#1963287 (10JAufrecht) [20:40:05] 6Team-Practices, 7Epic, 3TPG-2016Q3: [EPIC]Engineering teams can communicate their capacity for core vs new work - https://phabricator.wikimedia.org/T122838#1963304 (10JAufrecht) [20:46:24] 6Team-Practices, 7Epic, 3TPG-2016Q3: [EPIC] Engineering teams can communicate their capacity for core vs new work - https://phabricator.wikimedia.org/T122838#1963354 (10JAufrecht) [20:48:32] 6Team-Practices, 7Epic, 3TPG-2016Q3: [EPIC] Engineering teams can communicate their capacity for core vs new work - https://phabricator.wikimedia.org/T122838#1963361 (10JAufrecht) [20:51:43] 6Team-Practices, 7Milestone: A documented and agreed upon definition of ‘core work’ exists - https://phabricator.wikimedia.org/T122839#1963375 (10JAufrecht) [20:53:44] 6Team-Practices, 7Milestone: A documented and agreed upon definition of ‘core work’ exists - https://phabricator.wikimedia.org/T122839#1963403 (10JAufrecht) [20:53:46] 6Team-Practices, 7Milestone: Product-facing teams have agreed upon method for tracking core/strategic work - https://phabricator.wikimedia.org/T122841#1963402 (10JAufrecht) [21:00:18] 6Team-Practices, 7Milestone: Product-facing teams have agreed upon method for tracking core/strategic work - https://phabricator.wikimedia.org/T122841#1963435 (10JAufrecht) [21:04:10] 6Team-Practices, 7Epic, 7Milestone: [EPIC] 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#1963470 (10JAufrecht) [21:06:17] 6Team-Practices, 7Epic, 7Milestone: [EPIC] A documented and agreed upon definition of ‘core work’ exists - https://phabricator.wikimedia.org/T122839#1963471 (10JAufrecht) [21:06:28] 6Team-Practices, 7Epic, 7Milestone: [EPIC] Product-facing teams have agreed upon method for tracking core/strategic work - https://phabricator.wikimedia.org/T122841#1963473 (10JAufrecht) [21:34:12] 6Team-Practices: Update best meeting practices doc to include summary/detailed split format - https://phabricator.wikimedia.org/T122987#1963571 (10RobLa-WMF) p:5Triage>3Normal [22:42:39] jauchrect_ ggellermen et. al. : I had commented in the strategy spreadsheet earlier, but now that things have evolved, it's no longer directly relevant [22:43:31] Any objections to deleting cell E27 (which I added), and then resolving my comment in E28? And/or should E26 be deleted as well? [22:44:01] I think originally the text for E28 was "Run 50% of tests", which seemed weird without context. But "50% of tests have been run" somehow works in isolation, I think [22:56:03] 6Team-Practices: Make sure that TPG strategic possibilities are not out of alignment with potential org strategies - https://phabricator.wikimedia.org/T124724#1963941 (10ggellerman) 3NEW [23:22:39] dstrine: jaufrecht_: meeple27: klans: would any of you be willing to pair with me to create tests for 2 remaining barriers in Pos8? [23:24:06] ggellerman: this afternoon? I probably could [23:25:23] meeple27: Thanks, but I am booked for rest of day. Would you still be willing to do tomorrow or Weds if I can find a time? [23:27:23] ggellerman: my next couple days are pretty bad. If you can't find someone else, check back with me [23:27:40] or i suppose I could try on my own for half an hour today [23:28:55] meeple27: thanks! If you want to try on your own, the barriers are 3B, 4A and 4B in the Pos8 deck. [23:31:01] ggellerman: Ok. I'm down to 100 threads in my inbox, so I can take a break from emails and try writing some tests [23:31:15] Meeple27, I already copied that to the wiki page. [23:31:37] taking advantage of a surprisingly meeting-free monday afternoon [23:31:58] jaufrecht_: Doh, right! OK. Ignore my ramblings then. That's what I get for catching up on old emails! [23:35:44] ggellerman: I'm free in the next hour, Thursday after 3 or Friday morning [23:37:26] dstrine: thanks! meeple27: is in Pos8 deck now if you want to join him there. If there's anything remaining after today, I will book Thurs at 4pm with you. Thanks! [23:48:33] dstrine ggellerman: I added one test, but am not thrilled with it. I don't think I can go farther without clarification about the barriers themselves, as noted in my comments. Sorry I couldn't take it farther, but hopefully this is at least a step toward resolving those missing tests. [23:49:21] meeple27: thanks for the start! I'll see if I can find a hacking partner to keep it going [23:50:01] if I had my way, 2 of the missing tests probably wouldn't need to get written (deemed unnecessary)