[00:46:04] not without also limiting people who can edit them? [00:46:11] which afaik was deemed bad [00:50:04] that would be bad, yes [00:51:31] I was thinking in code [00:51:37] rather than just fiddling with project application settings [02:29:54] 6Project-Creators: Create MediaWiki-extensions-SkinPerPage project - https://phabricator.wikimedia.org/T102865#1487274 (10Spage) p:5High>3Normal [02:44:10] 6Project-Creators: Create MediaWiki-extensions-SkinPerPage project - https://phabricator.wikimedia.org/T102865#1487292 (10Spage) 5Open>3Resolved We decided not to create a new namespace just for pages in the (renamed) "Web APIs hub", so we need to deploy the SkinPerPage extension, not SkinPerNamespace. So I... [05:23:24] 6Engineering-Community, 10MediaWiki-skins-Blueprint, 10Web-APIs-Hub, 3ECT-August-2015, and 3 others: Goal: Integrate new Developer hub with mediawiki.org - https://phabricator.wikimedia.org/T101441#1487410 (10Spage) [07:41:55] 6Phabricator: Tasks moving back to default column on their own - https://phabricator.wikimedia.org/T107103#1487522 (10mmodell) Moving a task from column to column is actually an expensive server-side process, due to checking policies, loading objects, creating all of the transactional details, etc. If you leave... [08:44:48] 6Phabricator: Email notifications for reassigning/claim should be consistent with web interface - https://phabricator.wikimedia.org/T107062#1487573 (10Glaisher) Indeed, my bad. :) That was T106963#1485598 which happened at the same time and I saw the other task's change on IRC. Thanks. [09:04:15] 6Engineering-Community, 6Community-Advocacy, 6Team-Practices, 10Wikimania-Hackathon-2015: Binding code of conduct for all Wikimedia technical spaces with consequences for breaches - https://phabricator.wikimedia.org/T90908#1487612 (10Ladsgroup) Comparing to other CoCs we should have some explicit statement... [09:18:31] 6Phabricator, 6Release-Engineering: Evaluate Releeph for SWAT queue management - https://phabricator.wikimedia.org/T101794#1487644 (10Qgil) [09:34:47] 6Phabricator, 10Phabricator-Upstream: Assign due date to task and have tasks with due dates displayed on a calendar (similar to Trello) - https://phabricator.wikimedia.org/T76094#1487698 (10Qgil) [09:34:49] 6Phabricator: Enable the Calendar app in Phabricator - https://phabricator.wikimedia.org/T466#1487695 (10Qgil) 5Open>3Resolved a:3Qgil It is a fact that the Calendar application has been enabled for some time now. Resolving this task. [09:35:05] 6Phabricator: Enable the Calendar app in Phabricator - https://phabricator.wikimedia.org/T466#1487699 (10Qgil) a:5Qgil>3mmodell [09:43:01] 6Engineering-Community, 6Community-Liaison, 6WMF-Legal, 10Wikimedia-General-or-Unknown, 5Patch-For-Review: Identify survey services compatible with our privacy policy - https://phabricator.wikimedia.org/T94807#1487704 (10Qgil) [09:44:24] 6Engineering-Community, 6Community-Liaison, 6WMF-Legal, 10Wikimedia-General-or-Unknown, 5Patch-For-Review: Identify survey services compatible with our privacy policy - https://phabricator.wikimedia.org/T94807#1173052 (10Qgil) So we have Qualtrics and AllOurIdeas that have been explicitly vetter by #WMF-... [09:49:11] 6Phabricator, 6WMF-Design-Research: wmf-design-research project not showing up in autocomplete for keywords "design" or "research" - https://phabricator.wikimedia.org/T105412#1487709 (10Qgil) [14:11:41] twentyafterfour: hey! [14:12:00] thanks for offering to help us, but i'm a bit confused by call signs [14:13:40] bgerstle: no prob. Yeah, callsigns are confusing, and it's not made any better by our arbitrary limitations / naming conventions [14:13:52] it seems like i should use the "AP" prefix [14:13:57] is that also the callsign? [14:14:02] or is it something like APIOS? [14:14:48] it would be like apios except that they are arbitrarily limited to 4 letters [14:15:01] so APIO I guess [14:15:04] 😑 [14:15:14] or yell at ostriches about it [14:15:24] that seems cruel to the ostriches [14:15:27] there is no reason to limit them to 4 letters that I know of [14:15:30] I just got back from vacation, please don't yell at me. [14:15:46] /part time to hide [14:16:07] ostriches: can i have a callsign of APIOS? [14:16:09] pretty please? [14:16:18] it would make so much more sense [14:16:22] :) heh, that maybe better than yelling. maybe [14:16:40] twentyafterfour: Because otherwise people were basically writing their full repo name as a callsign. [14:16:48] When we were planning [14:16:57] ostriches: right, but why not 6 or something instead of 4 [14:17:01] yeah ^ [14:17:02] we have SO many repositories [14:17:03] beat me to it [14:17:17] twentyafterfour: We picked a number, 4 was it. [14:17:19] short and sweet is good [14:17:22] Maybe it should've been six. [14:17:25] but 4 isn't sweet it's sour [14:17:25] Who knows. [14:17:36] but since it's arbitrary we can change it ;) [14:17:44] Do what you want. [14:17:47] * ostriches doesn't care anymore [14:17:53] :-/ [14:17:54] APWIKIPEDIAIOSOSTRICHESISAWESOME [14:17:55] * ostriches goes and makes coffee instead [14:18:10] bgerstle: nice one [14:18:26] new rule: all callsigns must pay homage to ostriches [14:19:32] twentyafterfour: so i'll stick w/ APIOS for now [14:20:04] bgerstle: that sounds good to me :) [14:20:06] if this comes up again (like if we decide to break out a standalone OSS component), then i might go longer [14:20:15] e.g. APIOS${COMPONENT} [14:20:29] IOS >>> IO though [14:20:48] twentyafterfour: https://phabricator.wikimedia.org/T107153 [14:21:08] twentyafterfour: want me to move it to the bottom of your backlog? [14:21:32] bgerstle: no need, I'll get it set up right away [14:23:11] oh sweet! [14:23:25] 🎉🍻 [14:24:41] bgerstle: so you just want a mirror, right? that'll pull from github into phab [14:24:50] twentyafterfour: On the subject of repos...I should probably get around to having Phab do the replication to Github and anywhere else, instead of Gerrit doing replication. [14:24:59] So all repos will go to Phab, then to their final destinations [14:25:04] * ostriches should file a task [14:25:12] * ostriches should also finish making coffee [14:25:20] ostriches: yeah that should be fairly easy to set up. I'll help [14:26:58] twentyafterfour: exactly [14:27:03] twentyafterfour: will that pull tags as well? [14:27:57] bgerstle: I believe so [14:28:24] Oh yeah, I remember why I didn't do that /just yet/ [14:28:38] We need Phab to pull all refs/* from Gerrit, not just refs/heads/* and refs/tags/* [14:28:39] bgerstle: https://phabricator.wikimedia.org/diffusion/APIOS/ [14:28:51] ostriches: yeah, I was gonna look into that too [14:29:11] I /believe/ Gerrit just does whatever Git does by default, which is that. [14:29:28] If we adjust the [fetch] section of repo's .gitconfigs on iridium, it should Just Work [14:29:30] I think [14:29:31] Maybe [14:29:40] s/Gerrit/Phab/ [14:29:52] ostriches: yeah you are probably right [14:31:03] Failed to connect to github.com port 443: Connection timed out [14:31:05] hmm [14:31:13] Yeah, that'd make sense. [14:31:29] You gotta go through the proxy since you're an internal host. [14:31:36] doh! [14:31:43] twentyafterfour: on a related note... either of you know about registering IRC channels? [14:31:54] i'd like to register the #wikipedia-ios channel for IRC notifications from GitHub [14:32:03] bgerstle: not really very much [14:32:10] twentyafterfour: so, we probably already have a diffusion repo come to think of it.. [14:32:19] ? [14:32:31] twentyafterfour: https://phabricator.wikimedia.org/rAPIW364535fd59c0ba9f20b7a97c7328b7cf32e0b3aa [14:32:42] twentyafterfour: http://url-downloader.wikimedia.org:8080, for starters. [14:32:54] which has the completely unambiguous prefix of "API" 😬 [14:33:22] ostriches: I don't know how to make phabricator use a proxy. I remember having to hack the core before when I did the same thing at deviantARt [14:33:31] bgerstle: It's actually AP-IW, not API-W :) [14:33:33] it wasn't pretty [14:33:34] But, :p [14:33:40] but this is git.. [14:33:47] oh [14:35:00] twentyafterfour: #til: git has an http.proxy config setting. [14:35:22] ostriches: same [14:35:39] I'll set it globally... so the proxy is url-downloader.wikimedia.org:8080 ? [14:35:51] what about https? [14:36:07] https.proxy seems to also exist? [14:36:18] The proxy has to have the destination whitelisted. I'm not sure if Github is on that list yet. [14:36:22] * ostriches tries to find whitelist [14:36:26] iirc. [14:37:22] ostriches: seems to work [14:37:26] 6Phabricator: Herald rule for WMDE-Tech-Community-Communication - https://phabricator.wikimedia.org/T107154#1488149 (10Tobi_WMDE_SW) 3NEW [14:37:28] it's cloning now [14:37:36] 6Phabricator: Herald rule for WMDE-Tech-Community-Communication - https://phabricator.wikimedia.org/T107154#1488156 (10Tobi_WMDE_SW) [14:38:01] bgerstle: https://phabricator.wikimedia.org/diffusion/APIOS/ is importing now. I'm not sure what we should do about the old repo? [14:38:54] the old one is tracking gerrit, if you only manually push to gerrit then it seems kinda pointless to have that [14:39:26] should I deactivate that old one? [14:40:26] twentyafterfour: the old phab mirror? i suppose. what about tieing to phab tasks? [14:40:37] e.g. if i merge a pull request that mentions T123456 [14:40:40] would that ticket be updated? [14:40:42] or referenced? [14:41:05] bgerstle: yes, it will update tickets [14:43:47] ok [14:43:57] twentyafterfour: and if we deactivate, it won't go away [14:43:58] yet [14:44:00] 10Gitblit-Deprecate, 6Phabricator, 6Release-Engineering, 10Wikimedia-Git-or-Gerrit: Set Git configuration on all Phab repositories - https://phabricator.wikimedia.org/T107156#1488171 (10demon) 3NEW [14:44:09] twentyafterfour: Filed so we don't forget ^ [14:45:02] 10Gitblit-Deprecate, 6Phabricator, 6Release-Engineering, 10Wikimedia-Git-or-Gerrit: Set Git configuration on all Phab repositories - https://phabricator.wikimedia.org/T107156#1488180 (10mmodell) @demon: is it possible, perhaps, to just set these in /etc/gitconfig? [14:47:28] 6Phabricator: Herald rule for WMDE-Tech-Community-Communication - https://phabricator.wikimedia.org/T107154#1488183 (10mmodell) 5Open>3Resolved a:3mmodell Done: H82 [14:48:12] twentyafterfour: my main concern is that we are still planning on letting people submit patches via gerrit if they really want to [14:48:18] and will keep the code reasonably up to date [14:48:24] as long as what we're doing here doesn't hamper that [14:48:38] so we'll have a perfectly up-to-date WMF mirror of the repo in phab [14:48:42] how would you pull the gerrit changes into github? [14:48:48] manually [14:48:58] code review the patch in gerrit, then once approved, create a PR in GH and merge it [14:49:06] i.e. same way we were handling GH PR's before we were on GH [14:49:21] twentyafterfour: we don't expect we'll have to do this often [14:49:46] in that case it should be fine, because the phab repo that tracks github will get the commit once it's merged [14:50:02] k [14:50:03] 6Engineering-Community, 10Wikimania-Hackathon-2015: Create a user friendly encouraging-to-contribute site - https://phabricator.wikimedia.org/T91633#1488192 (10Petrb) There should be a project for this on labs [14:50:04] phabricator doesn't need to explicitly track gerrit if github is the canonical repo [14:50:40] k [14:58:36] twentyafterfour: would you please set the other associated projects for the phab repo to: Wikipedia-iOS-App-Product-Backlog [14:58:42] and Wikipedia-iOS-App-Development [15:01:17] 10Gitblit-Deprecate, 6Phabricator, 6Release-Engineering, 10Wikimedia-Git-or-Gerrit: Set Git configuration on all Phab repositories - https://phabricator.wikimedia.org/T107156#1488212 (10demon) Oooh, didn't think of that. Probably yeah :) [15:04:53] twentyafterfour: also, there's a "phabricator" output of a new build tool we're using... not sure what that means [15:05:24] apparently it's something you can "plug directly into arc:diff" [15:05:26] * bgerstle shrug [15:41:54] 6Engineering-Community, 6Team-Practices, 3ECT-July-2015: What to do with old open patches for unmaintained repositories when not even the uploader responds - https://phabricator.wikimedia.org/T102920#1488312 (10Aklapper) > * Should these changesets be marked as abandoned after, say, a year? I'd say No if th... [16:39:30] 10Gitblit-Deprecate, 10Gerrit-Migration, 3releng-201516-q1: Allow cloning of Phabricator hosted git repositories - https://phabricator.wikimedia.org/T128#1488559 (10mmodell) [17:22:39] bgerstle: interesting [17:33:41] twentyafterfour: I wrote up 2 puppet patches for the /etc/gitconfig stuff on iridium [17:34:00] Although, I'm curious if it'll needlessly proxy Gerrit connections... [17:34:30] I wonder if you can wildcard the URLs somehow in [http] [17:35:09] I think so. [17:35:23] [http "github.com/*"] perhaps? [17:53:03] 6Engineering-Community, 6Community-Liaison, 6WMF-Legal, 10Wikimedia-General-or-Unknown, 5Patch-For-Review: Identify survey services compatible with our privacy policy - https://phabricator.wikimedia.org/T94807#1488792 (10Whatamidoing-WMF) For some (smaller) purposes, {T89970} would solve the privacy prob... [19:54:40] 6Phabricator, 6Services: max execution timeout when loading burndown, leads to 503s a& 504s - https://phabricator.wikimedia.org/T107197#1489450 (10Josve05a) 3NEW [20:14:56] 6Phabricator, 6Services: max execution timeout when loading burndown, leads to 503s a& 504s - https://phabricator.wikimedia.org/T107197#1489511 (10Josve05a) ``` Request aborted by debug time limit after 20 seconds. STACK TRACE qsprintf.php:149 PhabricatorStartup->onDebugTick() xsprintf.php:70 xsprintf_query()... [20:32:04] 6Phabricator, 6Services: max execution timeout when loading burndown, leads to 503s a& 504s - https://phabricator.wikimedia.org/T107197#1489620 (10mmodell) My best guess is that the sprint extension just isn't scalable enough to handle the amount of data for this particular sprint. [20:33:15] 6Phabricator, 10Phabricator-Sprint-Extension, 6Services: max execution timeout when loading burndown, leads to 503s a& 504s - https://phabricator.wikimedia.org/T107197#1489622 (10Josve05a) [20:34:09] 6Phabricator, 10Phabricator-Sprint-Extension, 6Services: max execution timeout when loading burndown, leads to 503s a& 504s - https://phabricator.wikimedia.org/T107197#1489624 (10mmodell) Why is VisualEditor a sprint? Shouldn't a sprint be a time-limited thing, not an ongoing project? [20:38:07] 6Phabricator, 10Phabricator-Sprint-Extension, 6Services: max execution timeout when loading burndown, leads to 503s a& 504s - https://phabricator.wikimedia.org/T107197#1489641 (10Jdforrester-WMF) > Why is VisualEditor a sprint? Shouldn't a sprint be a time-limited thing, not an ongoing project? Because we c... [20:38:22] 6Phabricator, 10Phabricator-Sprint-Extension, 6Services: max execution timeout when loading burndown, leads to 503s & 504s - https://phabricator.wikimedia.org/T107197#1489648 (10Josve05a) [20:39:59] 6Phabricator, 10Phabricator-Sprint-Extension, 6Services: max execution timeout when loading burndown, leads to 503s & 504s - https://phabricator.wikimedia.org/T107197#1489662 (10JAufrecht) Specifically, we want to maintain a backlog, which is currently 1300+ items, that is retrievable and sortable in a query... [20:42:21] 6Phabricator, 10Phabricator-Sprint-Extension, 6Services: max execution timeout when loading burndown, leads to 503s & 504s - https://phabricator.wikimedia.org/T107197#1489681 (10Josve05a) How about creating an #Upstream (#Phabricator-upstream)-task to add poins without being sprint? Would be one way. But tha... [20:43:27] 6Phabricator, 10Phabricator-Sprint-Extension: Phabricator (Phragile?) gives max execution timeout when loading some burndowns, instead giving 503s & 504s - https://phabricator.wikimedia.org/T107197#1489697 (10Jdforrester-WMF) [20:43:58] 10Wikibugs: wikibugs announcing phab column changes on IRC - https://phabricator.wikimedia.org/T107208#1489704 (10greg) 3NEW [20:45:18] 10Wikibugs: wikibugs announcing phab column changes on IRC - https://phabricator.wikimedia.org/T107208#1489719 (10greg) [20:46:07] 6Phabricator, 10Phabricator-Sprint-Extension: Phabricator (Phragile?) gives max execution timeout when loading some burndowns, instead giving 503s & 504s - https://phabricator.wikimedia.org/T107197#1489724 (10Josve05a) ``` >>> UNRECOVERABLE FATAL ERROR <<< Maximum execution time of 30 seconds exceeded /srv/p... [21:08:25] 6Phabricator, 10Phabricator-Sprint-Extension: Phabricator (Phragile?) gives max execution timeout when loading some burndowns, instead giving 503s & 504s - https://phabricator.wikimedia.org/T107197#1489815 (10Christopher) There is an easy fix for this. Just disable the events view. This is a global config op... [22:27:19] 10Wikibugs, 5Patch-For-Review: wikibugs announcing phab column changes on IRC - https://phabricator.wikimedia.org/T107208#1490007 (10Legoktm) 5Open>3Resolved a:3Legoktm [22:55:35] 6Phabricator, 10Phabricator-Sprint-Extension: Phabricator (Phragile?) gives max execution timeout when loading some burndowns, instead giving 503s & 504s - https://phabricator.wikimedia.org/T107197#1490097 (10mmodell) @christopher: sadly, disabling events view doesn't seem to solve the problem - it's still tim... [22:58:53] 6Phabricator, 10Phabricator-Sprint-Extension: Phabricator (Phragile?) gives max execution timeout when loading some burndowns, instead giving 503s & 504s - https://phabricator.wikimedia.org/T107197#1490101 (10mmodell) Here's the stack with the events view disabled: ``` STACK TRACE LiskDAO.php:608 PhabricatorS... [23:01:05] 6Phabricator, 6Team-Practices, 7Epic: [EPIC] Gather requirements from teams for Phab project management feature requests - https://phabricator.wikimedia.org/T105404#1490109 (10ksmith) [23:07:31] 6Phabricator, 10Phabricator-Sprint-Extension: Phabricator (Phragile?) gives max execution timeout when loading some burndowns, instead giving 503s & 504s - https://phabricator.wikimedia.org/T107197#1490124 (10mmodell) Yeah this just isn't going to ever work with that much data. It's querying all of the transac... [23:09:13] 6Phabricator, 10Phabricator-Sprint-Extension: Sprint extension doesn't scale to thousands of tasks in a single sprint: burndown page exceeds max execution timeout on visual editor project - https://phabricator.wikimedia.org/T107197#1490135 (10mmodell) [23:12:15] 6Phabricator, 6Team-Practices, 7Epic: [EPIC] Gather requirements from teams for Phab project management feature requests - https://phabricator.wikimedia.org/T105404#1443177 (10ksmith) [23:13:15] 6Phabricator, 10Phabricator-Sprint-Extension, 10VisualEditor: Sprint extension doesn't scale to thousands of tasks in a single sprint: burndown page exceeds max execution timeout on visual editor project - https://phabricator.wikimedia.org/T107197#1490156 (10Josve05a) [23:15:55] 6Phabricator, 10VisualEditor, 6operations: Unable to load https://phabricator.wikimedia.org/tag/visualeditor/ - https://phabricator.wikimedia.org/T107229#1490160 (10Josve05a) 3NEW [23:18:40] 6Phabricator, 6Team-Practices, 7Epic: [EPIC] Gather requirements from teams for Phab project management feature requests - https://phabricator.wikimedia.org/T105404#1490171 (10ksmith) [23:32:15] 6Phabricator, 6Team-Practices, 7Epic: [EPIC] Gather requirements from teams for Phab project management feature requests - https://phabricator.wikimedia.org/T105404#1490217 (10ksmith) [23:54:04] 6Engineering-Community, 6Community-Liaison, 6WMF-Legal, 10Wikimedia-General-or-Unknown, 5Patch-For-Review: Identify survey services compatible with our privacy policy - https://phabricator.wikimedia.org/T94807#1490260 (10leila) The second point is very valuable @Whatamidoing-WMF. @Qgil Manprit from Lega...