[16:18:06] kristenlans (or other wolves): I'm not quite clear about the meeting proposal I'm supposed to vote on [16:18:48] doh! I'm meeple! [16:18:48] :-) Guest67529 [16:19:01] let me see if I can figure out how to become myself again [16:19:04] Guest67529: no you're not! [16:19:15] Guest67529: this is a lifelong quest [16:27:54] Perhaps now I'm me? [16:29:13] Guest67529: nope, you're int he matrix now [16:29:48] goldurnit [16:30:21] I'm connecting through vector (experimental slack-like client), and it shows me as meeple27, but I see that in irc I'm not. Sigh. [16:30:29] seems that I'll be mostly irc-less today [16:30:37] switching back to my normal client. [16:32:29] kristenlans: I'll ask my meeting questions via email [16:34:43] ok almost-meeple27 tl;dr vote in the staff notes on any of the meeting/process twekas you are game ot try [16:35:09] I can't really vote on each one without understanding the interactions between them [16:40:50] almost-meeple27: I tried to outline that a bit in the email I sent - mabe we can discuss at one on one [16:42:45] kristenlans: I sent email, which I think will benefit everyone to be sure we're all agreeing to the same thing [16:42:57] thanks almost-meeple27 [17:17:14] jaufrecht: still getting a 404 error for Phlog, been that way the whole week. Any idea why? http://phlogiston.wmflabs.org/and_report.html [17:18:17] All phlogiston has been down for two weeks due to an upstream problem. No eta. Maybe next week. [17:19:44] k [18:07:22] 06Team-Practices, 10TPG-2017Q1-Roll-Out-Engagement-Survey: Select teams for Light Engagement survey - https://phabricator.wikimedia.org/T141133#2488136 (10JAufrecht) [18:10:42] 06Team-Practices, 10TPG-2017Q1-Roll-Out-Engagement-Survey: Administer Light Engagement survey - https://phabricator.wikimedia.org/T141134#2488154 (10JAufrecht) [18:10:58] 06Team-Practices, 10TPG-2017Q1-Roll-Out-Engagement-Survey, 07Epic: [EPIC] Roll out Light Engagement survey - https://phabricator.wikimedia.org/T139549#2435674 (10JAufrecht) [18:21:12] 06Team-Practices, 10TPG-2017Q1-Roll-Out-Engagement-Survey: Report on Light Engagement Survey - https://phabricator.wikimedia.org/T141136#2488271 (10JAufrecht) [18:25:32] 06Team-Practices, 10TPG-2017Q1-Roll-Out-Engagement-Survey, 07Epic: Determine SOP for Light Engagement survey - https://phabricator.wikimedia.org/T141138#2488318 (10JAufrecht) [18:25:38] 06Team-Practices, 10TPG-2017Q1-Roll-Out-Engagement-Survey: Determine SOP for Light Engagement survey - https://phabricator.wikimedia.org/T141138#2488318 (10JAufrecht) [18:25:48] 06Team-Practices, 10TPG-2017Q1-Roll-Out-Engagement-Survey, 07Epic: [EPIC] Roll out Light Engagement survey - https://phabricator.wikimedia.org/T139549#2435674 (10JAufrecht) [18:26:35] 06Team-Practices, 10TPG-2017Q1-Roll-Out-Engagement-Survey: Select teams for Light Engagement survey pilot - https://phabricator.wikimedia.org/T141133#2488337 (10JAufrecht) [18:26:40] 06Team-Practices, 10TPG-2017Q1-Roll-Out-Engagement-Survey: Administer Light Engagement survey pilot - https://phabricator.wikimedia.org/T141134#2488338 (10JAufrecht) [18:26:42] 06Team-Practices, 10TPG-2017Q1-Roll-Out-Engagement-Survey: Report on Light Engagement Survey pilot - https://phabricator.wikimedia.org/T141136#2488271 (10JAufrecht) [18:27:28] 06Team-Practices, 10TPG-2017Q1-Roll-Out-Engagement-Survey: Refine the Light Engagement survey based on pilot results - https://phabricator.wikimedia.org/T141139#2488343 (10JAufrecht) [18:28:16] 06Team-Practices, 10TPG-2017Q1-Roll-Out-Engagement-Survey, 07Epic: [EPIC] Roll out Light Engagement survey - https://phabricator.wikimedia.org/T139549#2488356 (10JAufrecht) [18:30:39] 06Team-Practices, 10TPG-2017Q1-Roll-Out-Engagement-Survey: Select teams for Light Engagement survey 2nd round - https://phabricator.wikimedia.org/T141140#2488366 (10JAufrecht) [18:31:07] 06Team-Practices, 10TPG-2017Q1-Roll-Out-Engagement-Survey: Select teams for Light Engagement survey 2nd round - https://phabricator.wikimedia.org/T141140#2488366 (10JAufrecht) [18:31:16] 06Team-Practices, 10TPG-2017Q1-Roll-Out-Engagement-Survey: Refine the Light Engagement survey based on second round results - https://phabricator.wikimedia.org/T141142#2488397 (10KLans_WMF) [18:32:23] 06Team-Practices, 10TPG-2017Q1-Roll-Out-Engagement-Survey: Administer Light Engagement survey 2nd round - https://phabricator.wikimedia.org/T141143#2488413 (10JAufrecht) [18:32:53] 06Team-Practices, 10TPG-2017Q1-Roll-Out-Engagement-Survey, 07Epic: [EPIC] Roll out Light Engagement survey - https://phabricator.wikimedia.org/T139549#2488426 (10KLans_WMF) [18:33:13] 06Team-Practices, 10TPG-2017Q1-Roll-Out-Engagement-Survey, 07Epic: [EPIC] Roll out Light Engagement survey - https://phabricator.wikimedia.org/T139549#2435674 (10KLans_WMF) [18:33:36] 06Team-Practices, 10TPG-2017Q1-Roll-Out-Engagement-Survey, 07Epic: [EPIC] Roll out Light Engagement survey - https://phabricator.wikimedia.org/T139549#2488430 (10JAufrecht) [18:33:49] 06Team-Practices, 10TPG-2017Q1-Roll-Out-Engagement-Survey, 07Epic: [EPIC] Roll out Light Engagement survey - https://phabricator.wikimedia.org/T139549#2435674 (10JAufrecht) [18:33:52] 06Team-Practices, 10TPG-2017Q1-Roll-Out-Engagement-Survey: Report on Light Engagement Survey second round - https://phabricator.wikimedia.org/T141144#2488435 (10KLans_WMF) [18:35:19] 06Team-Practices, 10TPG-2017Q1-Roll-Out-Engagement-Survey: Report on Light Engagement Survey second round - https://phabricator.wikimedia.org/T141144#2488435 (10KLans_WMF) [18:35:43] 06Team-Practices, 10TPG-2017Q1-Roll-Out-Engagement-Survey, 07Epic: [EPIC] Roll out Light Engagement survey - https://phabricator.wikimedia.org/T139549#2435674 (10KLans_WMF) [18:36:07] 06Team-Practices, 10TPG-2017Q1-Roll-Out-Engagement-Survey: Determine new SOP for Light Engagement survey - https://phabricator.wikimedia.org/T141138#2488467 (10JAufrecht) [18:36:18] 06Team-Practices, 10TPG-2017Q1-Roll-Out-Engagement-Survey, 07Epic: [EPIC] Roll out Light Engagement survey - https://phabricator.wikimedia.org/T139549#2488468 (10KLans_WMF) [18:36:55] 06Team-Practices, 10TPG-2017Q1-Roll-Out-Engagement-Survey: Report on Light Engagement survey pilot - https://phabricator.wikimedia.org/T141136#2488470 (10JAufrecht) [18:37:07] 06Team-Practices, 10TPG-2017Q1-Roll-Out-Engagement-Survey: Report on Light Engagement survey second round - https://phabricator.wikimedia.org/T141144#2488472 (10JAufrecht) [18:37:52] 06Team-Practices, 10TPG-2017Q1-Roll-Out-Engagement-Survey: Refine the Light Engagement survey based on 2nd round results - https://phabricator.wikimedia.org/T141142#2488476 (10KLans_WMF) [18:38:02] 06Team-Practices, 10TPG-2017Q1-Roll-Out-Engagement-Survey, 07Epic: [EPIC] Roll out Light Engagement survey - https://phabricator.wikimedia.org/T139549#2488479 (10JAufrecht) [18:38:13] 06Team-Practices, 10TPG-2017Q1-Roll-Out-Engagement-Survey: Report on Light Engagement survey 2nd round - https://phabricator.wikimedia.org/T141144#2488480 (10KLans_WMF) [18:42:10] 06Team-Practices, 10TPG-2017Q1-Identify-Common-Pain, 07Epic: [EPIC] Identify and address a common pain point across teams we interact with. - https://phabricator.wikimedia.org/T139630#2488500 (10JAufrecht) [18:42:24] 06Team-Practices, 10TPG-2017Q1-Identify-Common-Pain, 07Epic: [EPIC] Identify and address a common pain point across teams we interact with. - https://phabricator.wikimedia.org/T139630#2438191 (10JAufrecht) [18:42:57] 06Team-Practices, 10TPG-2017Q1-Identify-Common-Pain, 07Epic: [EPIC] Identify and address a common pain point across teams we interact with. - https://phabricator.wikimedia.org/T139630#2438191 (10JAufrecht) [18:43:51] 06Team-Practices, 10TPG-2017Q1-Identify-Common-Pain: "Fix a pain point" target selected - https://phabricator.wikimedia.org/T140936#2488532 (10JAufrecht) [18:45:50] 06Team-Practices, 10TPG-2017Q1-Identify-Common-Pain: PLACEHOLDER Pain point solution tested - https://phabricator.wikimedia.org/T140938#2481574 (10JAufrecht) [18:46:17] 06Team-Practices, 10TPG-2017Q1-Identify-Common-Pain: PLACEHOLDER: Measure outcomes/impact of fixing a common pain point for teams - https://phabricator.wikimedia.org/T140940#2481609 (10JAufrecht) [18:46:53] jaufrecht: for tracking a milestone in Phlog, do I just spell it out explicitly, the way Phab does, in the scope and recat? e.g. (without the quotes) "Android-app-feature-Feeds (MVP)". I'm confused because, technically, the Milestone in question ("MVP") is a project called "MVP." How does Phlog differentiate from, say, any project that has "MVP" in the [18:46:53] title? [18:47:41] 06Team-Practices, 10TPG-2017Q1-Identify-Common-Pain: Method to get candidates for "fix a pain point" decided - https://phabricator.wikimedia.org/T140931#2488546 (10JAufrecht) [18:47:52] (I've gotten around this for now by calling the Milestone "Android-app-feature-Feeds (Android-app-feature-Feeds-MVP)" but I would like to just call it "MVP" since it is redundant in the workaround [19:16:16] From phlogiston's perspective, a milestone is just another project [19:18:57] And I'm pretty sure phlogiston won't do any of the clever title stuff Phabricator does. If the title is this-week, that's all it will match on. It won't use the milestone's parent's title in matching. [19:22:45] To guarantee a match on a non unique project title, use the match on two ids feature, or file a ticket for phlogiston to be able to match on a single id. Shouldn't be too hard to code. [19:23:45] Phlogiston used to use id, but I figured it would be easier if people could put in names instead. Maybe should go back to ids on the config. [19:52:15] TPG nerd-dom confession: I am ridiculously pumped to get my latest shipment of new post it notes. [20:50:06] jaufrecht: awjr vote on tea :) [20:50:51] done [23:57:24] jaufrecht: regarding Phlog: naming IS better, but ideally I should be able to search for "Android-app-feature-Feeds (MVP)", where "MVP" is the Milestone on the "Android-app-feature-Feeds" project. I believe that's the name of the project anyway, but I'm not sure. It shows up that way in tickets and search, but not on the Milestone page/workboard itself. [23:59:03] the proper way to support naming is to replace the config files with an interface using Phabricator auto-complete to select names, but there are substantial technical barriers to that. Practical options right now include: adding support for categorizing based on a single project ID; dumping names altogether in favor of IDs; doing nothing. [23:59:47] Phlogiston supporting categorization by "parent Project name (immediate project name)" is probably not realistic given the three or four complications I can think of just looking at it