[08:24:34] d3r1ck: GCI: Do you really think it is realistic to see a merge in a random code repository, within 36 hours? [08:25:21] andre__: I think so if one has poked some backup and it's ready [08:25:49] d3r1ck, What does "poke some backup" mean? [08:25:54] It's what I've been using in the mean time [08:26:04] So I've poked a few devs with +2 rights on mediawiki/* [08:26:19] Honestly though it's not a very efficient method :( [08:26:30] Ah! Alright... as long as you keep track, that's cool! Appreciated. :) [08:26:35] Also, some tasks come up with some complications I never ever knew [08:26:45] Like the licenses :D [08:26:55] I asked as I wondered how you'd make someone +2 https://gerrit.wikimedia.org/r/#/c/mediawiki/extensions/HoverGallery/+/470303/ etc within the next 27 hours :) [08:27:02] Those tasks may sound easy but need some serious checking :) [08:27:15] I still think it's unlikely to block review on +2, but well [08:27:27] s/review/approval on the GCI site/ [08:27:35] Yes andre__ you're very correct [08:27:49] If I could get merge faster, that would have been ideal [08:28:13] But merges come a little slower and sometimes with some very good corrections so, that is the trade-off :( [08:28:24] Hmm. I see your point, yeah. [08:29:13] andre__: These licenses tasks are nice, honestly. They're making silly me to read a lot! [08:29:22] these days [08:30:11] andre__: But I've put a cap of 24hrs and if no merge, I approve but so far so good, I've not yet reached that cap :) [08:30:33] So not that bad [08:40:16] oh great! :) [09:17:49] d3r1ck, andre__: I think we can take "approval" of GCI task on a project mentor hasn't +2 rights as "being responsible for the patch and its correctness since approving". Anyway, if we can get patches merged in time, no problem with that ofc. [09:18:51] * d3r1ck nods