[07:23:04] mornin' andre__ , how do you feel about start giving access to existing users with existing projects asking to get access? https://phabricator.wikimedia.org/tag/wiki-release-team/ is asking (Alexis, Mark, Markus) [07:23:28] I would give them access explaining that they cannot upload files (they didn't uploaded any before) [07:23:50] we need more testing and they were relying on Phabricator already [07:39:30] I guess we have to... [07:41:58] ...and I should reboot my machine after installing updates, which translates to "give quim 'admin' as a fallback and make sure he is logged in" [07:48:40] andre__, ok and ok [07:49:19] andre__, I'm not having problem logging in and out btw, other than making sure to use https [07:49:32] oh that's lovely. I hope it stays like that [07:50:08] not that I have tested heavily, just in case... but I have been logging in and out [07:50:28] actually let me try consciously now [07:51:00] yep, seem to work [07:51:45] if you give me admin then the only thing I will do with it is to open/close the LDAP gate to let existing users needing to work in existing projects [07:52:03] without bothering you [07:53:55] another possibility being to give the related permissions to https://phabricator.wikimedia.org/tag/phabricator.wikimedia.org/ in the interim (I actually don't enjoy having admin permissions) [07:54:34] done; will be back in 6min [07:58:28] Now I'm intrigued. Why 6 precisely. :) [08:04:43] seems to work. nice. [09:41:00] andre__ whenever you have time, please have alook at https://www.mediawiki.org/wiki/Phabricator#Migration_timeline and tell me whether something is terribly wrong or is horribly missing [09:42:56] I'd just love to have ONE central place for the timeline. If we can kill comment 0 in T174 for that, lovely. [09:45:38] andre__, I will double check that comment 0 to make sure no info is missing and then I will remove that content, linking to https://www.mediawiki.org/wiki/Phabricator#Migration_timeline [09:45:48] I like. [09:46:05] andre__, and we could do the same with https://www.mediawiki.org/wiki/Phabricator/Plan#Migration_plan [09:46:19] urgh. true. a 3rd place. sigh. [09:46:30] ok, I'll continue [09:47:12] I think I considered https://www.mediawiki.org/wiki/Phabricator/Plan#Migration_plan canonical so far [09:47:20] don't mind where, just one place would be awesome [09:52:43] why is there https://phabricator.wikimedia.org/tag/phabricator.wikimedia.org/ ? [09:53:00] we have https://phabricator.wikimedia.org/tag/phabricator/ , we have https://phabricator.wikimedia.org/tag/wikimedia_phabricator_production_instance/ [09:53:06] why a 3rd project? [09:53:49] https://phabricator.wikimedia.org/tag/phabricator.wikimedia.org/ says "creation of new projects". so that's a rename from https://phabricator.wikimedia.org/tag/project-request ? [09:54:08] I don't expect anybody to find that with such generic names. [09:54:31] Either feels like overengineering or I don't get the permissions setup. [10:06:21] and we have https://phabricator.wikimedia.org/tag/wikimedia_phabricator_maintenance/ too [10:18:24] qgil__: why is there a "blocked by" section on https://www.mediawiki.org/wiki/Phabricator for "Bugzilla migration" ? It's obviously blocked by all tasks that are still open on https://phabricator.wikimedia.org/project/board/10/ [10:18:42] I'm not keen on updating several places with the same info. [10:18:52] it feels like we are duplicating the hell out of everything. [10:19:12] andre__, I'll take care of that, these are the top level blockers and they are there for communication with the outside [10:19:32] you take care of the project tasks & woirkboard, I take care of that list [10:19:41] you work for the project, I work for the communicatin [10:19:41] ok? [10:20:19] probably... [10:20:20] sending people directly to a workboard like https://phabricator.wikimedia.org/project/board/10/ won't work [10:20:37] creating four workboards for Phabricator in Phabricator neither :) [10:21:00] not my idea... I created just one for the whole Day 1 :) [10:21:16] * andre__ tempted to kill several tasks and projects. [10:21:33] at this point, let's kill them by completing them [10:22:06] I don't consider the phab, phab maintenance, and phab.wikimedia.org projects "completeable". [10:22:12] (by definition) [10:22:43] phab is a team, and I also don't understand why are we assigning tasks to it if they are in other fab projects [10:22:56] phab maintenance will probably disappear, yes [10:23:21] If teams can have tasks, they are defacto projects. [10:23:31] true [10:23:39] mmm [10:23:41] I don't see any difference between teams and projects. [10:23:47] in the end, everything is a tag. [10:24:00] phabricator.wikimedia.org wins? [10:24:12] we have permissions tied to this one [10:24:18] what does that project do? [10:24:23] maintenance? administration? [10:24:23] and is the clearest name [10:24:28] it's very unclear to me. [10:24:32] all of it, isn't this what you are saying? [10:25:05] what is not a specific Pabricator project goes to phabricator.wikimedia.org [10:25:06] what's the difference to a project called "Phabricator", from reading the name? [10:25:19] if I wanted to file a task in the right place? [10:26:06] ok, then we can have Phabricator only, and move the permissions there [10:26:39] and we can remove from Phabricator all the tasks that are dealt with in specific projects [10:26:39] well, it's confusing to me. I expect it's also confusing to anybody else. [10:27:01] andre__, I agree and this is why I'm proposing solutions [10:27:40] andre__, so, question: can I get rid of Maintenance and phabricator.wikimedia.org, moving everything under Phabricator only?> [10:28:27] now it's good time: almost nobody is cced on those tasks so we won't generate notifications :) [10:28:31] hmm, "Phabricator" doesn't have a workboard. Was that meant to be an umbreall project? [10:29:01] Chase CCed plenty of tasks to Phabricator, as some kind of backup (don't know exactly why) [10:29:18] I guess it was meant as an umbrella project. [10:29:19] once we enter maintenance mode, we can focus more on that workboard, now it's not urgent [10:29:40] sure, but as you say, why do we need an umbrella project duplicating stuff? [10:30:19] see endless debates on Commons whether to have the categories "Artists", "Female Artists" and "Male Artists", or combine searches for several categories. [10:30:46] * andre__ dropped LesbianGayGenderTranssexualQueerEtc to simplify the example [10:31:16] kill https://phabricator.wikimedia.org/tag/wikimedia_phabricator_maintenance/ , move all to https://phabricator.wikimedia.org/tag/phabricator ? [10:31:31] ok! progress :) [10:31:50] move https://phabricator.wikimedia.org/tag/phabricator.wikimedia.org/ into https://phabricator.wikimedia.org/tag/phabricator ? [10:32:10] I need some coffee. [10:33:32] https://phabricator.wikimedia.org/project/view/8/ moved and archived [10:34:53] heh, thanks. also for your patience with me :) [10:45:19] andre__, https://phabricator.wikimedia.org/project/view/14/ also archived [10:45:38] andre__, now, you need to change the policy to create new projects, must point to #phabricator [10:45:56] ... and with this I think that's all. Much better! [10:46:03] Even better when we clean #phabricator [10:47:17] yay, great. now let me try to find where that generic policy setting was configured [10:54:42] andre__, "Edit policies" at https://phabricator.wikimedia.org/applications/view/PhabricatorProjectApplication/ [10:55:56] ... aaaand, there you have a backlog of generic Phabricator tasks not listed redundantly in other projects: https://phabricator.wikimedia.org/project/board/5/ [10:56:54] w00t, fun times ahead :) [10:57:55] well, advanced search + batch edits rock [11:10:06] https://www.mediawiki.org/w/index.php?title=Phabricator%2FPlan&diff=1171849&oldid=1163848 -- you're welcome :) [11:24:12] ... and T174 description now points to the canonical timeline as well: https://phabricator.wikimedia.org/transactions/detail/PHID-XACT-TASK-ekoajpy4ejlzjnd/ [11:24:14] done [11:24:15] lunch [11:34:36] +1 on lunch [12:09:18] andre__, bon appetit. I had permissions to switch on/off LDAP but no more? Please consider giving them to the #phabricator team, if possible at all. [12:39:06] awesome, I'm logged out. [12:39:18] * andre__ swears [12:40:02] oh wait, what [12:41:05] interesting. LDAP off but I can re-log in. I wonder what the default cookie time period is [12:47:46] andre__, I *think* I have been logged out before, but I could login without problems. I will pay more attention now, and I will file a task if I find myself out in the middle of a session [12:48:06] andre__, do you agree with these rules for early users? https://www.mediawiki.org/wiki/Phabricator#Access_to_phabricator.wikimedia.org [12:48:09] yeah, I could also re-log in. interesting. [12:48:23] qgil__: and only admins can configure auth policies (like enabling LDAP). [12:48:31] ok, well... [12:48:45] might make sense to have you or mukunda just for that as a backup [12:48:53] I think so too [12:49:07] btw, doies mukunda have a user yet? [12:49:13] yes [12:49:21] ah, goos, dome tasks that can be assigned [12:49:23] good [12:49:31] since a few hours ago [12:49:55] if the rules linked above make sense to use, I will start using them [12:50:28] if you are involved in any of the current projects "and really need to get some planning done"? [12:50:49] well, I think it's too restrictive already [12:51:03] c'mon, all this is only for the files, really? [12:51:14] we need real testers [12:52:00] oh, one more, not using it for more testing / learning but for real tasks [12:52:02] will add it now [12:53:38] We need real testers. Not sure when though. [12:53:51] and we have a test instance which is meant to have the same setup. for testing. [12:54:23] so you can switch on/off LDAP too now. [12:54:48] but the term "testing" is pretty blurry. Just saying. [12:55:36] I mean, we need real users trying to do real work and providing real feedback if something doesn't work as they expect [12:56:00] I just added "you will work on real tasks, leaving any testing or learning for https://phab-01.wmflabs.org/ " [12:56:09] that's indeed more likely to happen in production than on phab--01. [12:56:26] ok, thank you :) [12:56:31] you're probably right. [12:59:15] I added another one :) * you are aware of the timeline and the fact that the site might be entirely down during the RT and Bugzilla migrations [13:01:11] that's welcome, true [13:13:09] oh wow, that's a lot of people in here [13:15:52] hi YuviPanda :) [13:15:52] hello qgil__ [13:16:22] YuviPanda, since we are in a room on-topic, may I ask you about the bots vs Phabricator? [13:16:51] ah [13:17:06] well, I still think it shouldn't be too hard to move our rules into the phab irc bot [13:17:28] our current grrrit-wm was written in about 3 days, and so was wikibugs, so I suspect importing it to phab will take not too much longer [13:17:45] it's time for action, do you know who will do this task (if it's not you)? [13:18:19] qgil__: assuming we only care about wikibugs for now (not grrrit-wm, since we aren't migrating from gerrit yet), it's either me, or valshallaw, or legoktm, or chase [13:18:28] it's just trivial php, so pretty much anyone can pick it up [13:18:32] is it considered a blocker for day0? [13:18:39] not chase, he has just too many critical items on his plate [13:18:46] yes, a blocker [13:19:40] YuviPanda, I have toi show you the timeline defining the blockers that I just did this morning ;) [13:19:41] https://www.mediawiki.org/wiki/Phabricator#Migration_timeline [13:19:47] find "IRC" there [13:20:03] qgil__: yeah [13:20:06] * YuviPanda considers [13:20:17] did, I mean compiled from the work andre__ and chase had actually done... [13:21:40] qgil__: I don't think I can volunteer my time next week, though :( in the middle of a huge, multipatch refactor of something in the ops repo [13:22:22] we have more than one week, but maybe valhallah has more time? [13:22:35] possibly [13:22:38] I also suggest poking legoktm [13:22:57] you just did :) [13:23:35] :) [15:21:00] qgil__: andre__ btw, the phab-01 migration went well, no hiccups, just about 1min of downtime [16:32:27] yuvipanda, tank you! wow [16:32:56] (I manage to introduce at least one typo in every line I write) :( [16:33:16] and Yuvi is not here to thank him anymore, ah well [16:36:03] qgil__: oh I am :) [16:36:39] ah, good that I didn't say anything bad about you :) [16:37:12] hehe [16:52:42] qgil__: can I get Phabricator access? [16:52:49] I want to update https://phabricator.wikimedia.org/T382 [16:53:03] ok, 1 min [16:57:17] qgil__: ditto! [16:57:21] ;) [16:57:23] no rush [16:58:09] greg-g, sorry, I'm about to start a meeting with... you :) [16:59:00] :) :) [16:59:08] robla: btw, no video link in calendar invite? [16:59:36] I'd add it, but I dont' have edit access [17:02:07] he's probably fighting with the mac mini... [17:02:27] qgil__: what am I being poked for? :) [17:02:53] hi legoktm IRC bots ready for Phabricator [17:03:03] and whether you would like / were thinking to work on them [17:03:10] legoktm: DOOOOOIIIITTTTTT [17:04:17] uhh just wikibugs right? [17:04:33] did someone set up phab emails to go to a mailling list yet? [17:06:02] legoktm: nooooo [17:06:08] legoktm: there's already an IRC bot in phab, in php [17:06:14] it doesn't do filtering based on rulesets [17:06:16] just need to add that [17:06:21] right but, [17:06:34] do we also have the mailing list set up? [17:06:40] unsure [17:06:40] that's a must have for me [17:06:43] ask qgil__ [17:06:44] legoktm: why [17:06:58] so I can look through the bug spam for when I was asleep. [17:07:08] hardcore legoktm is hardcore? :) [17:07:49] also is phab going to be indexable by search engines? [17:08:00] that's also why archiving comments via email was super important [17:08:13] https://phabricator.wikimedia.org/robots.txt I guess so? [17:08:35] yuvipanda: where's the irc bot in php? [17:08:54] https://secure.phabricator.com/book/phabdev/article/chatbot/ [17:09:56] legoktm, yuvipanda I assume nothing has been done ref mailing list: https://phabricator.wikimedia.org/T453 [17:09:59] what do you need? [17:10:11] someone to do it? :P [17:10:40] re-using wikibugs is going to be the best idea because it's already set up to archive everywhere [17:17:01] legoktm: the wikibugs code is tightly tied to the bugzilla email format [17:17:14] I don't mean for the IRC bot [17:17:16] I mean just in general. [17:17:22] we need the mailing list [17:18:03] but I'll play with the bot today [17:18:19] legoktm: \o/ [17:18:40] where is the new phab labs instance? [17:18:53] legoktm: phab-01.eqiad.wmflabs [17:18:58] legoktm: phab-01.wmflabs.org [17:19:18] all puppetized and stuff right? :D [18:38:23] do we have a guide somewhere about bugzilla terminology --> phab? [18:38:43] what is a bz product or component called in phab? [18:38:44] andre__: ^ [18:39:33] project [18:39:40] terminology mapping: not really [18:40:09] product, component, keyword, target milestone all become 'project', basically. [18:42:34] hmm ok. [18:43:19] so, we'll have a "MassMessage" project basically? And a "Gadgets" one? [18:43:29] and then the bot just needs to route messages based on projects it's in [18:44:02] would we have one "MediaWiki" component for core bugs? or "MediaWiki Configuration" (for MediaWiki --> Configuration) ? [18:56:21] andre__: ^ ? :) [19:04:08] <^demon|away> Hi. Can registration be opened for me on phab.wm.o? [19:05:27] ^demon|away, got LDAP cred's ready? [19:05:33] <^demon|away> Yes. [19:05:44] ^demon|away, go! (and tell me when done) [19:05:55] <^demon|away> Done. [19:06:06] <^demon|away> "Check your e-mail" etc etc [19:06:26] ^demon|away, I assume you want to verify. :) [19:06:38] <^demon|away> Yes, all done that too. [19:06:52] alright [19:07:50] legoktm: "MediaWiki-Configuration" that would become (normally: BZProject-BZComponent). We only have a flat namespace for projects. [19:08:04] related long discussions in https://phabricator.wikimedia.org/T43 , for the records. [19:08:06] ok [19:08:29] if project.startswith('VisualEditor') : channel = '#mediawiki-visualeditor' [19:08:31] wonderful. [19:12:07] <^demon|away> I got booted from being logged in (I see T465, so I tried to login again) [19:12:11] <^demon|away> But I'm timing out on login. [19:16:01] <^demon|away> andre__: Can I also get +admin? As an existing BZ admin + the gerrit admin? :) [19:16:26] ^demon|away: are you on https instead of http [19:16:32] <^demon|away> Yessir. [19:16:35] hmm [19:16:51] ^demon|away, could you elaborate what you need admin for? [19:17:10] (for the records, we have no rules defined why and how people get admin.) [19:17:12] <^demon|away> Ah, that login window was http. Stupid me. I'm in. [19:17:22] thought so [19:17:33] <^demon|away> andre__: Habit? Ability to manage git stuff once we're there too. [19:18:15] ^demon|away: then let me give you admin when we're closer to setting up git stuff, if that's okay? [19:18:55] so, does https://secure.phabricator.com/book/phabdev/article/chatbot/ have to run on the same server as the phab instance? that part isn't super clear. [19:19:03] <^demon|away> andre__: I'm wanting to go ahead and move one of our Java things for Elasticsearch to Phabricator as an early user. [19:19:38] legoktm: uh, don't know. If you can't figure out, #phabricator might be an option :-/ [19:20:06] ^demon|away: Okay. How does that require admin on the production instance? [19:20:36] I just don't want to end up with 30 Bugzilla admins again. That was... not helpful. [19:20:54] <^demon|away> Who all's admin right now? [19:22:06] I wonder if I can query that, but I'm afraid the answer is me. [19:22:17] <^demon|away> 1 user doesn't scale :( [19:22:45] Correct. I'm happy to give that to Chase and Mukunda. [19:22:55] because they know the system. [19:23:31] <^demon|away> I'm not familiar with the code, but I do know my way around phabricator by now :) [19:23:58] <^demon|away> Anyway, I guess I'll just wait until closer to git. [19:24:24] ^demon|away, if you run into issues when trying moving Java things for Elasticsearch to Phab which would require admin, please tell and I'm happy to give admin to you. [19:24:44] what special powers do admins in BZ have that mortals don't? [19:24:44] but in general I like usecases in addition to "I trust you and I know what you're doing". [19:24:47] er, in phab* [19:25:01] legoktm: simplified: changing any config settings. [19:25:15] anyone can create new projects? [19:25:26] <^demon|away> andre__: I'm also willing to give a hand on meta things like creating projects/components/etc, as I've done on BZ for years. [19:25:34] <^demon|away> Just so you're not alone in that. [19:25:50] (also I asked in #phabricator about the IRC bot) [19:26:03] legoktm: no. We've restricted project creation to a certain group and the wiki has documentation on requesting a new project [19:26:19] (group = project) [19:26:33] ^demon|away: that would indeed be welcome! Let me find the group/project for that to join... [19:27:19] "Phabricator team" [19:27:20] okay [19:27:34] > Access to https://phabricator.wikimedia.org is restricted due to some pending tasks. You can request an exception if you are involved in any of the current projects. [19:27:42] can I haz exemption please :) [19:29:25] ^demon|away: that would be "Join project" on https://phabricator.wikimedia.org/tag/phabricator/ (though that is not only project creation stuff) [19:29:33] legoktm: got LDAP cred's handy? [19:29:43] I think so. [19:29:52] just wikitech account info? [19:30:10] legoktm, yeah. GO! [19:30:15] and use https [19:30:44] <^demon|away> andre__: That sounds like a good place to start! I'll start out with just this before getting the keys to the kingdom :) [19:30:54] ^demon|away, heh. Thanks, man! [19:31:05] <^demon|away> But I don't have permission to join. [19:31:06] andre__: ok, done :) [19:31:22] <^demon|away> "Joinable By Phabricator (Project)" [19:33:16] ^demon|away, ahem, sorry, true, invitation only. Shall I add you? [19:33:18] (In any case, be aware that there's naming scheme rules for projects, so that's rather something to help with after the migration from Bugzilla.) [19:33:32] <^demon|away> andre__: Please and thanks! [19:33:38] <^demon|away> (And yes, I'd seen the new naming scheme) [19:33:41] alright! [19:33:43] thanks! [19:34:09] <^demon|away> \o/ awesome [19:45:05] legoktm: *waves* [19:53:52] o/ [19:54:01] valhallasw`cloud: so in #phabricator: [12:47:58] <@epriestley> legoktm: in theory, any server [19:54:05] for running the bot [19:55:07] but I think we should try keeping pywikibugs [20:16:50] legoktm: right. then the question is whether it's easier to use IRC as phab->wikibugs gateway or e-mail [20:16:53] probably the latter [20:17:11] I think email is best. [20:17:12] I *think* the best option would be to make phab spam wikibugs-l with changes [20:17:24] then we can slowly adapt pywikibugs to understand those emails [20:17:39] yes [20:30:00] If you guys manage to work this out I really owe you some drinks. [20:30:45] +1 to valhallasw`cloud [20:30:58] that's what i meant as well on that former fab.wmflabs ticket [20:31:10] make it send emails like bz did [20:31:31] might be easier than using a new bot [20:44:38] yeah, apparently fab sends mails with extra headers now [20:44:49] but I'm not sure if they are sent anywhere pywikibugs can listen to them [20:44:59] they aren't [20:45:15] I filed a fab.wmflabs bug for setting up the mails going to wikibugs-l [21:35:06] hmm yeah https://phabricator.wikimedia.org/T453 [21:35:36] and making sure that does not report on restricted tickets