[02:11:23] 10Wikibugs: Inconsistent versioning in wikibugs - https://phabricator.wikimedia.org/T141364#2497704 (10Legoktm) [02:14:46] 10Wikibugs: Inconsistent versioning in wikibugs - https://phabricator.wikimedia.org/T141364#2495667 (10Legoktm) Maybe. This is both the third and second iterations of wikibugs. The first was a perl script that read from wikibugs-l. Then it was rewritten into a Python script, which also parsed email, but that was... [03:16:31] 10Phabricator, 07Regression: Phabricator is auto claiming tasks when closing as resolved (again) - https://phabricator.wikimedia.org/T134106#2254658 (10Krinkle) [03:21:53] 10Phabricator, 07Regression: Phabricator is auto claiming tasks when closing as resolved (again) - https://phabricator.wikimedia.org/T134106#2254658 (10matmarex) Unlike before, you can override it by also adding a "Claim" action and emptying the field, and the preview shows exactly what will happen. I don't mi... [06:20:16] 10Phabricator, 07Regression: Phabricator is auto claiming tasks when closing as resolved (again) - https://phabricator.wikimedia.org/T134106#2498010 (10Aklapper) p:05Low>03Lowest [06:47:46] 10GitHub-Mirrors: Update GitHub Commons Android app repo one-liner - https://phabricator.wikimedia.org/T127623#2498025 (10Nicolas_Raoul) 05Open>03Resolved a:03Nicolas_Raoul Fixed, thanks all :-) [09:48:14] 10Phabricator, 10Phabricator (Upstream), 07Upstream: Phabricator sends mail notification for moving tasks between workboard columns even if configured not to - https://phabricator.wikimedia.org/T139312#2498294 (10Aklapper) p:05Triage>03Low [10:13:57] 10Phabricator: Herald_rule_for_Unplanned_Sprint_Work_Tag - https://phabricator.wikimedia.org/T141129#2498331 (10Aklapper) 05Open>03Invalid Impossible to do hence closing as Invalid for time being [11:27:22] 10Phabricator, 06Project-Admins: Create new Project: #WMF-Internal-Tech - https://phabricator.wikimedia.org/T139994#2498482 (10Danny_B) @Milimetric I can create the tag, that's no issue with that. But that won't guarantee you the privacy yet. So I thought having the space set prior the tag would be better. How... [11:30:54] andre__: joe claims he can't edit the project policies although he's member of the project and the group which is allowed in the policy. any known issue about that? can phab admins step in then? (also, it's not the first case, there were some other users in the same issue. seems like after some update projects with custom policies became uneditable...) [11:31:14] Danny_B: which project? where does joe claim that? [11:31:44] link / context welcome [11:32:11] andre__: https://phabricator.wikimedia.org/tag/services-tooling/ (in our discussion - i asked him to change the policies and he said he can't) [11:32:48] any link to that discussion? [11:33:09] andre__: nope. irc/conpherence [11:33:10] (as that might save followup questions) [11:33:15] not important [11:33:21] Oh, if Conpherence feel free to add me [11:34:34] Danny_B, and Phab admins cannot step in then... [11:34:43] see https://www.mediawiki.org/wiki/Phabricator/Permissions#Administrators [11:36:24] well, via direct db access anything is doable... ;-) [11:36:38] Yeah, but that does not require Phab admins ;-) [11:36:46] is "Edit details" in the right menu enabled or disabled for joe? [11:36:54] on https://phabricator.wikimedia.org/project/manage/1233/ [11:37:47] got no response on this particular question yet. but i assume he is not blind ;-) [11:40:31] Need that info, same for other projects potentially affected. [11:41:35] will try to get them. my assumption is that the menu item is disabled [11:43:35] anyway, we should consider putting some note into project creation guidelines like "please use custom policies only and only if you really need them as it can cause issues" [11:43:54] Danny_B: thanks for finding out. And trying to fix this stuff. [11:43:57] Danny_B, see https://www.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects#Project_Policies [11:44:00] already there. [11:44:05] ah, cool [11:44:09] if not, feel free to edit away :) [11:45:46] andre__: according to the custom policy, you should be able to edit https://phabricator.wikimedia.org/project/manage/1297/ [11:45:50] can you? [11:46:01] then you would have an answer to your questions [11:54:59] Danny_B, hmm, editing worked for me for project 1297 [11:55:12] Danny_B: regarding the talkpage: no time yet, and it will take me a while. because the answer is likely somewhere in the middle between all those opinions and positions... [11:55:40] (and if noone actually explains their motivations I'm not yet sure how much there is to discuss and (dis)agree...) [17:08:19] 10Phabricator, 06Project-Admins: Create new Project: #WMF-Internal-Tech - https://phabricator.wikimedia.org/T139994#2499423 (10Milimetric) I think it would be useful to have the tag created first. We can just refrain from discussing anything sensitive until we have the space. But it would be nice to get ours... [18:08:47] qchris: Question. I was looking at https://gerrit.wikimedia.org/r/#/c/299164/. Do you see any reason we couldn't use the debian-provided mysql-connector? It's available as libmysql-java and uses the same version. [18:08:57] (I don't think we can do the same with bcprov, debian version too far behind [19:45:08] ostriches: I have made bad experiences with mysql-connector being older than what gerrit required. [19:45:09] But if I read that correctly, Debian's version is newer than what Gerrit requires. Right? [19:45:13] wheezy is on 5.1.39, while 5.1.21 is required by gerrit 2.12.2. [19:45:17] I have no experienc with mysql-connector being newer than what Gerrit requires. [19:45:21] It's probably worth testing. [19:45:41] qchris: We're on jessie right now. [19:45:47] They both have 5.1.22 iirc. [19:46:07] Argh. I meant jessie. right. [19:46:19] https://packages.debian.org/source/jessie/mysql-connector-java [19:46:27] ^ says 5.1.39-1~deb8u1 [19:46:46] Anyways. Be it 5.1.22 or 5.1.39. [19:46:54] Both are newer than what Gerrit requires. [19:47:30] I'd be careful to not have two different versions in gerrit's lib dir at the same time (That gets gerrit confused) [19:47:41] But other than that, I'd say it's worth trying. [19:47:42] Oh yeah, I wouldn't. [19:47:52] I'd install the system one and remove the lib copy entirely. [19:48:15] Just makes the packaging simpler if we can :) [19:48:22] Yup. Definitely. [19:48:35] I'd give it a shot. [19:50:15] Will do that then [22:29:05] 10Phabricator, 06ArchCom, 06Developer-Relations, 06Release-Engineering-Team, 15User-greg: Consider alternative processes for Unbreak Now bugs, especially those which cross-cut components - https://phabricator.wikimedia.org/T140207#2500474 (10greg) 05Open>03Resolved a:03greg #wikimedia-incident crea... [22:35:15] 10Diffusion, 07Regression: Unable to browse refs/meta/config in Diffusion - https://phabricator.wikimedia.org/T137354#2500499 (10Paladox) I think I may have an idea on how to fix this in gerrit, it requires a change in gerrit and phabricator. So will need help by @mmodell to develop the fix please. [22:36:20] 10Phabricator, 06ArchCom, 06Developer-Relations, 06Release-Engineering-Team, and 2 others: Consider alternative processes for Unbreak Now bugs, especially those which cross-cut components - https://phabricator.wikimedia.org/T140207#2500504 (10greg) [22:42:33] 10Phabricator: Phabricator uses different monospace fonts for inline code snippets and block code snippets - https://phabricator.wikimedia.org/T141494#2500522 (10matmarex)