[11:35:04] Permission denied [11:35:04] @seenrx [Tt][Bb]ayer.* [11:35:11] boo [17:52:13] Phabricator Tech Talk starts in 10 min [17:52:35] please ping me with questions for qgil & andre__ at any point :) [18:00:41] starting in 5 min [18:02:22] "Please stand by." [18:02:26] * greg-g stands [18:03:35] just started [18:03:38] should be live [18:03:39] :) [18:03:42] :) [18:03:44] hear everything OK? [18:03:56] yep [18:04:22] listening on the stream, howdy [18:04:23] Should I go to "#meidawiki-office" (quote: YouTube link in topic) [18:05:10] hi gilles baby! [18:05:35] f v bv gvbfvfv [18:05:38] :) :) [18:06:06] can you see Quim's screen share? [18:06:58] gi11es: so cute :) greg-g: for a second I thought that was your nick name for gilles ;) [18:07:29] rfarrand: :P [18:07:34] and yep, can see the screen fine [18:15:08] questions? [18:16:26] Lcawte: fixed [18:16:31] the limits are only enforced with a visual notification [18:16:49] the column header turns red [18:18:59] is it just me or is andre breaking up? [18:19:04] not just you [18:19:15] a bit yes [18:20:05] greg-g: he seems OK here [18:20:16] or at least it is a bit better now [18:20:26] * greg-g blames the rain [18:20:28] if it gets so you can not understand him let me know [18:20:34] s'all right [18:20:50] yeah, SF is the wild west today [18:20:50] it's not quite a problem for hearing :) [18:21:58] rfarrand: do you know how many folks are streaming right now? [18:22:06] 16 [18:22:09] :) thanks! [18:22:10] awjr ^ [18:22:23] andre__ broke up a lot for about 10 second and then got better [18:22:30] just as a warning from people following along [18:22:41] qs? [18:22:52] sorry :-/ [18:23:04] awjr: 18 now + 3 in SF and 5 on the hangout [18:23:06] probably my connection isn't the best, or my computer gets old :-/ [18:27:05] qs? [18:27:19] hi folks [18:27:28] hi thedj :) [18:30:03] This is a weird format for office hours [18:30:43] QueenOfFrance: that might be because this is not 'office hours' ;) [18:36:13] last chance for qs! [18:36:35] one thing about the control bit: I think Jan's comment on T819 is a good one. We need mass revert tools. [18:37:01] I'm good [18:37:12] robla++ [18:37:19] search, are we planning to improve taht ? [18:37:29] rfarrand: ^ [18:37:47] it should be easy to build, I screwed up the priority on a few hundred tickets and it was trivial to build a script that undid it using conduit [18:38:03] i.e. reading the old prio and setting it again [18:38:44] it'll depend on what you want to undo, basically [18:39:35] I was gonna ask about Phabricator-MyLyn integration, but I just saw it's only an upstream wishlist [18:39:51] https://secure.phabricator.com/T4548 [18:40:09] we've had mass vandalism on BZ in the past. we will almost certainly have it in the future on Phab, so we need to be ready for that day. Is there a tracking request for that? [18:40:12] AndyRussG: let me know if you want me to ask [18:40:30] robla: will ask next [18:40:51] what was teh cleanup mechanism in BZ? [18:40:57] robla: There is the ability to perform an action for all tasks in a search... might help cleaning up. [18:41:30] chasemp: it was a lot of manual work. it sucked. it was one of the things that soured me on BZ, since upstream had a "meh" attitude about it [18:41:54] chasemp: upstream's solution was "lock your instance down" [18:42:13] I'm not sure what the right thing to do for this is other than have a restore point but that's global in general [18:42:27] maybe, possibly, we could wrote something taht essentially voided a user and all their activity [18:42:35] robla, T84 [18:42:50] but I haven't put serious thought into it, I just know that the way thingns are stored in theory maybe we could rewind the transactions [18:42:59] but it's a not simple problem that I haven't seen solved well [18:43:21] chasemp: I think making it per user is a fine solution. There's a lot of ideas we can borrow from MediaWiki on this [18:43:48] search ticket: T75854 [18:43:51] ^ thedj [18:43:55] thumbs up ! [18:44:21] rfarrand: if there's extra time and nothing more relevant, u could ask :) I don't know how many others at the WMF might be interested... [18:44:36] rfarrand: and thanks! :) [18:44:43] AndyRussG: there is time, will ask :) [18:45:31] csteipp: that's limited to 100 tickets only :/ [18:45:55] * greg-g had to step away for a second, may have missed that voiced in the hangout [18:46:11] greg-g: I think I got around that with "page size" in the query [18:46:18] huh [18:46:29] Not sure what the upper limit is... [18:46:46] the best mechanisms are preventative that I know of, but it's a heavy cross to bear. We could restrict edit in general for all tasks to users who have clout however you want to define it. Or requiring all users to be "verified". Those things exist natively but seem to go against the ethos so it's complicated I guess. [18:47:08] "[10:39:34] I was gonna ask about Phabricator-MyLyn integration, but I just saw it's only an upstream wishlist" [18:47:39] andre__: ^ [18:47:45] MyLyn! [18:47:54] sorry. Eclipse. I remember something. :) [18:47:57] yeah eclipse [18:48:05] but yeah, needs upstream involvement [18:48:18] K thanks!! [18:48:48] thanks! [18:49:00] bye, thanks all! [18:50:02] Thanks everyone! [18:50:41] thank you everyone ! [18:50:55] thanks! [18:51:31] good to hear that chad and nik are already working on patches ! [18:51:54] andre__: Ya, MyLyn is Eclipse, I thought it might be used with other IDEs too... I use it to keep various IDE states alive when switching between tasks... [18:52:42] Yeah, I also remember upstream requests for Bugzilla integration with Mylyn [18:52:49] Hmmm [18:53:06] I wonder if there is some more general task tool/protocol that MyLyn, Phab and maybe other IDEs could speak [18:54:03] I have no idea, sorry :-/ [18:54:09] how do you mean [18:54:13] for submitting differential? [18:59:14] I mean, for automatically seeing my Phabricator tasks in Eclipse's MyLyn vew [18:59:56] this would probably be an api call to conduit [19:00:33] the response is json [19:04:24] Yeah doesn't sound like it'd be too tough to whip up