[16:19:58] Upgrade to Phabricator seems to have messed up the data dump Phlogiston uses. Dump ran, data is present, Collab is fine, but VE is missing hundreds of tasks. [17:32:18] jaufrecht: the risks of poking around directly in native data, as opposed to relying on documented apis or standardized dumps (not that either of those were an option in this case) :( [17:35:32] I've found the place in Phlogiston where the data goes awry but it's hard to see how any change in the Phabricator data dump would have caused the change. [17:35:36] I hate computers [17:41:05] good thing you chose a career to avoid them then! :P [17:42:33] meeple27: messing with phabricator data in general is fraught with peril. The upstream project is very much in "move fast and break things" mode and plans to stay that way for 2+ more years. [17:42:57] afaik none of their apis are marked as stable [17:43:23] and we all get to see how they randomly shuffle the UI on a regular basis [17:50:42] i thought they had some json/xml peeker/poker thingy that was moderately stable [17:50:50] for some definition of stable [18:12:18] the combination of "our data model is unstable" and "we won't get to reporting until 2018ish" is not cool [18:12:34] problem seems to be narrowed down to projectcolumns being changed in the new dump [18:13:02] there were warning labels all over the json/xml/whatever thingy [18:13:09] so we didn't use it [18:13:24] it also didn't actually expose a couple of the key bits of data that we absolutely needed [18:13:29] (as I recall) [19:39:23] 06Team-Practices, 06Community-Advocacy, 06Community-Liaisons, 06Developer-Relations: Goal: Binding code of conduct for all Wikimedia technical spaces with consequences for breaches - https://phabricator.wikimedia.org/T90908#2252001 (10Mattflaschen) In the past few weeks, over a dozen people, including me,... [20:07:11] 06Team-Practices, 06Community-Advocacy, 06Community-Liaisons, 06Developer-Relations: Goal: Binding code of conduct for all Wikimedia technical spaces with consequences for breaches - https://phabricator.wikimedia.org/T90908#2252070 (10Yaron_Koren) So I guess that's a yes, then. If anyone's wondering what... [20:09:02] jaufrecht: ggellerman awjr what say ye for tea? [20:09:37] kristenlans: jaufrecht: what is our topic today? [20:09:53] I don't know I can't get the doc to load! [20:13:10] kristenlans: I just stacked the deck for the neutrality one [20:13:19] smooth move ggellerman [20:14:06] let's see if kristenlans and jaufrecht can tip the balance [20:14:25] ggellerman: I just countered with head/ass [20:14:50] kristenlans: I like it [20:17:13] I'm pretty wiped out and could pass on tea time. Kona was up at 4:30 this morning. [20:18:59] Kona! [20:25:06] kristenlans: I could use the time or do TT - up to you [20:32:31] jaufrecht: awjr ggellerman how about we punt, I mean, kick the can down the road, to next week. [20:33:08] jaufrecht: awjr: kristenlans: works for me [20:37:51] jaufrecht: awjr: kristenlans: consider it cancelled [20:37:58] ggellerman: ^ [20:39:55] 06Team-Practices, 06Community-Advocacy, 06Community-Liaisons, 06Developer-Relations: Goal: Binding code of conduct for all Wikimedia technical spaces with consequences for breaches - https://phabricator.wikimedia.org/T90908#2252156 (10Mooeypoo) >>! In T90908#2252070, @Yaron_Koren wrote: > So I guess that's... [21:01:51] kristenlans: WFM [21:13:51] 06Team-Practices, 06Community-Advocacy, 06Community-Liaisons, 06Developer-Relations: Goal: Binding code of conduct for all Wikimedia technical spaces with consequences for breaches - https://phabricator.wikimedia.org/T90908#2252349 (10Yaron_Koren) To clarify, the big discussion we had was unrelated to the... [23:06:16] 06Team-Practices, 10TPG-Essential-Functions, 15User-JAufrecht: Propose agenda for Editing annual retrospectives - https://phabricator.wikimedia.org/T134023#2252849 (10JAufrecht)