[00:48:26] 6Team-Practices, 6Community-Advocacy, 6Developer-Relations, 10Wikimedia-Developer-Summit-2016, 3DevRel-January-2016: Goal: Binding code of conduct for all Wikimedia technical spaces with consequences for breaches - https://phabricator.wikimedia.org/T90908#1933593 (10Mattflaschen) >>! In T90908#1929234, @... [05:31:13] 6Team-Practices, 6Community-Advocacy, 6Developer-Relations, 10Wikimedia-Developer-Summit-2016, 3DevRel-January-2016: Goal: Binding code of conduct for all Wikimedia technical spaces with consequences for breaches - https://phabricator.wikimedia.org/T90908#1933842 (10greg) >>! In T90908#1933593, @Mattflas... [05:56:19] 6Team-Practices, 6Community-Liaison, 6Developer-Relations, 10WMF-Product-Development-Process: Proposal: any WMF software project willing to be prioritized requires a concept publicly available - https://phabricator.wikimedia.org/T118231#1933855 (10Ironholds_backup) Is phabricator widely used by either the... [06:43:35] 6Team-Practices, 6Community-Liaison, 6Developer-Relations, 10WMF-Product-Development-Process: Proposal: any WMF software project willing to be prioritized requires a concept publicly available - https://phabricator.wikimedia.org/T118231#1933861 (10Qgil) I think the canonical place for concepts of software... [07:09:14] 6Team-Practices, 6Community-Liaison, 6Developer-Relations, 10WMF-Product-Development-Process: Define good practices to start working on project concepts privately - https://phabricator.wikimedia.org/T123611#1933868 (10Qgil) 3NEW [09:32:27] 6Team-Practices, 6Community-Advocacy, 6Developer-Relations, 10Wikimedia-Developer-Summit-2016, 3DevRel-January-2016: Goal: Binding code of conduct for all Wikimedia technical spaces with consequences for breaches - https://phabricator.wikimedia.org/T90908#1934011 (10Tgr) The big problem with voting is th... [14:11:00] 6Team-Practices, 6Community-Advocacy, 6Developer-Relations, 10Wikimedia-Developer-Summit-2016, 3DevRel-January-2016: Goal: Binding code of conduct for all Wikimedia technical spaces with consequences for breaches - https://phabricator.wikimedia.org/T90908#1934259 (10Krenair) >>! In T90908#1933593, @Mattf... [21:26:09] dstrine: Does "successfully upstreamed" mean that we created a ticket in phac's system? Or that we actually got joy from an upstreamed request being delivered? [21:29:10] meeple27 The first. I gave Kristen more notes about how unlikely it is that we will be happy [21:32:15] thanks. I commented in the deck [21:35:57] kristenlans: oops. I messed up your clean doc. Let me know if you want me to revert the damage myself. [21:36:38] and as a "for next time", you could set the doc to read only :whistle: [21:40:38] we have 3 tpg meetings in a row, in 3 different rooms. I tried to move one, but neither of the other 2 rooms are available (and the other 2 meetings are non-editable so I can't try to move them) [21:41:01] doesn't affect me since I'm WFH today, but I figured I would try to help out the oppressed non-remoties [21:55:27] 6Team-Practices: Investigate CSAT participation statistics - https://phabricator.wikimedia.org/T123439#1935489 (10DStrine) @MBInder_WMF Edward noted that approximately 50% was ok for a combined assessment, which is what we are doing. Edward said he could answer the second 2 points in more detail but needs tim... [22:03:30] jaufrecht_ et al: Trying to get into hangouts. All of google has been a bit off today [22:28:46] meeple27: need to skip grooming [22:36:14] 6Team-Practices, 7Epic, 7Milestone, 3TPG-2016Q3: [EPIC] TPG does "Other" work in FY2016Q3 - https://phabricator.wikimedia.org/T123145#1935616 (10JAufrecht) [22:36:31] 6Team-Practices, 15User-JAufrecht: Experiment with new Phabricator Functionality - https://phabricator.wikimedia.org/T123317#1926146 (10DStrine) Please create and account. You will see many differences from our current version. I will need to grant you specific access to some features and send instructions on... [22:38:54] 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#1935636 (10ksmith) [22:40:01] 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#1915103 (10ksmith) p:5Triage>3High [22:40:54] 6Team-Practices, 7Milestone: Product-facing teams have agreed upon method for tracking core/strategic work - https://phabricator.wikimedia.org/T122841#1935657 (10ksmith) p:5Triage>3High [22:42:34] 6Team-Practices, 7Milestone: A documented and agreed upon definition of ‘core work’ exists - https://phabricator.wikimedia.org/T122839#1935666 (10ksmith) p:5Triage>3High [22:43:31] 6Team-Practices, 7Epic, 3TPG-2016Q3: [EPIC]Engineering teams can communicate their capacity for core vs new work - https://phabricator.wikimedia.org/T122838#1935669 (10ksmith) p:5Triage>3High [22:53:03] 6Team-Practices: [EPIC] Review, synthesize, and present Q4 THC data - https://phabricator.wikimedia.org/T108215#1935711 (10ksmith) 5Open>3Resolved a:3ksmith Closing, per comments above. [22:58:15] i keep hitting "join meeting" from the calendar invite, and ending up on a completely blank new browser tab :( [22:58:27] that's weird [22:59:29] i'm in [22:59:36] just took about a dozen tries [23:03:06] jaufrecht_: wil you join? [23:03:16] coming