[20:01:10] ...and I can't change the topic [20:02:03] twentyafterfour: ^ can you edit the topic to indicate the channel is publicly logged? [20:02:09] and also maybe remove +t? [20:03:27] what's +t? [20:04:49] legoktm you're an op, do what you need to do [20:05:21] thanks [20:05:26] +t means only ops can edit the topic [20:05:38] ah [20:06:08] I can't remove it, you'll need to do something like /cs set #wikimedia-devtools mlock -t [20:09:59] (I was tempted to add https://www.mediawiki.org/wiki/Phabricator/Migration#Status and https://www.mediawiki.org/wiki/Phabricator/Plan to the topic but realized this channel is not only about Phabricator) [20:14:39] (I was tempted of start asking "are we there yett???" a kid in the back seat after 3 hours on the road -- but then I realized that fab hasn't been down that long.) ;) [20:16:53] andre__: close enough ^ ? :) [20:17:16] legoktm, cool, thank you! [20:18:01] qgil: Go ahead! I'm curious when I will start ignoring everybody. ;) [20:18:34] but it will definitely take three days because the migration is rough, plus we have to sort out more things in the meantime (see https://www.mediawiki.org/wiki/Phabricator/Plan#Migration_plan for the updated list) [20:31:29] I think the legal stuff is most likely to kill us, dunno if anyone has a way to bother them [20:32:46] i thought someone had sent troops? [20:38:06] chasemp, is there a task reported upstream? I bet we are not the only Phabricator instance needing to add legal links visible in all pages [20:38:15] I can report it [20:38:39] I don't know, but usually they link to it when discussed if so [20:38:43] so I would guess not [20:39:02] * qgil goes to report [20:49:48] Legal links visible in all pages: https://secure.phabricator.com/T6052 [20:55:56] I can hack it in if we don't care about upstreaming. that'd be pretty simple [20:56:24] (not according to evan when you start talking workboards and all) [20:56:45] I was thinking header is our best shot if we have to [21:00:12] ping'ed evan to comment [21:05:00] It's not difficult. I customized the header at dA and it wasn't a terrible maintenance issue [21:05:17] legalese in header..... [21:05:26] but hacking a footer might work for now [21:05:35] workboards are a tiny portion, no problem [21:06:14] it all comes down to lingo, if legal says "all pages" [21:06:55] chasemp, we are flexible and legal can be flexible as well [21:06:58] it's odd to me that it would be negotiable, I figured legal requirement is just that, either all pages or not, or login or not [21:07:22] I can't understand legal requirements being ala carte [21:07:30] but hey not my field, open to whatever [21:07:35] theory is theory, reality is reality [21:07:55] https://gerrit.wikimedia.org/ is as official as Wikimedia Phabricator will be, and... [21:08:09] yes...that was my first question [21:08:12] and rt isn't much better [21:08:13] so...? [21:09:04] I replied to the thread you started, let's see what they say. In the meantime, don't get too distracted by this. [21:09:19] sounds good [21:23:36] yay, shiny new channel to idle on :) [21:32:30] Eloquence: welcome :) [21:42:43] twentyafterfour: did that bug where an empty member list errors on project creation ever get fixed? [21:42:55] I have a hardcoded phid from labs admin for testing, unsure if was dealt w/ [21:45:18] chasemp: I'm not sure, empty members list in the security plugin? [21:45:37] there was a bug we found after merging the project.create [21:45:47] creating a project with no members raises an exception [21:47:05] I don't remember fixing it [23:02:16] will Phabricator make our emails public as bugzilla did? Or will it use only the WMF logins? [23:03:32] helderwiki, WMF (or LDAP) logins [23:03:58] also see https://bugzilla.wikimedia.org/show_bug.cgi?id=148#c19 [23:05:01] thanks [23:05:04] np :) [23:05:17] (s/WMF/SUL, to be exact) [23:05:52] https://secure.phabricator.com/T6052#6 [23:05:56] https://secure.phabricator.com/T6052#9 [23:12:55] ^ legal requirements. [23:13:04] and Evan helpful as usual. [23:13:22] pretty much what we thought for immediate but yeah dude is awesome [23:23:53] andre__: with the migration from BZ to Phabricator, what happens to Bugzilla usernames? Will we have some kind of mapping of BZ-emails to SUL accounts? [23:24:13] Bugzilla usernames = email addresses [23:24:23] so you will be able to claim your Bugzilla account [23:24:30] after verifying [23:25:40] So, one just needs to have access to the email associated to bugzilla to claim it? Is there any problem if the email on Bugzilla is different from the one on SUL? [23:25:50] we will need to create a job to update such metadata (reporter, CC, assignee, commenter) [23:26:12] you can set up several email addresses for your account in Phab actually [23:26:14] I don't have any wiki accounts tied to my bugzilla email... [23:26:19] Oh, I see. [23:26:34] You will see on https://phabricator.wikimedia.org/settings/panel/email/ once it's available [23:26:56] It wasn't possible to have wiki accounts tied to Bugzilla email before :) [23:27:41] well I mean the email I am currently using in bugzilla (krenair@wm.o) is not the verified email for any of my wiki accounts [23:27:46] So, if it accepts more than one email, I assume the same idea applies for Git/Gerrit [23:28:13] in theory they could all be different now and still be linked to a single Phabricator account then [23:28:15] ? [23:28:45] it does accept more than one email [23:28:48] and that is correct [23:28:56] great :-) [23:28:57] and it doesn't matter if the email is in wiki or not for claming your bugzilla data [23:29:06] as long as it's verified to phab [23:29:07] all good [23:29:37] Might be something to cover on https://www.mediawiki.org/wiki/Phabricator/Help [23:29:49] yeah on list to write up....for a long time and I never get it done [23:30:32] was just saying in general. I wouldn't stop helder or anybody else either to document that by basically copying the sentences from this conversation :) [23:47:59] so chasemp : what do you need me to be working on right now? I'm here to help as much as I can