[02:14:41] Hola bd808 [02:14:56] Please, request to global ban joaquinito01 [02:16:44] @kb Wagglie [05:05:43] enwiki.{analytics,web}.db.svc.eqiad.wmflabs s1 0.0000 00:00:00 [05:05:51] well that's something new and different [08:26:13] Krenair: it is available. Seems like the protocol version changed? Reported at T259431. [08:26:14] T259431: labs-vagrant broken due to NFS issues - https://phabricator.wikimedia.org/T259431 [17:02:36] !log admin increased db connection limit to 800 across galera cluster because we were clearly hovering at limit [17:02:38] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Admin/SAL [18:44:08] My new instance has been "scheduling" for 2,5 hours now. Is that expected? [18:44:31] https://horizon.wikimedia.org/project/instances/27c3c81e-06f3-4adc-8587-e06ce66ade83/ [18:44:33] kalle: no, it usually takes just a minute [18:45:02] we can't follow that link unless we are in the same project [18:45:27] kalle: i'd try to just cancel and repeat it .. for now [18:45:34] Ok, I'll try. Thanks! [18:45:35] if it happens again let's open a ticket [18:47:19] I can't seem to delete it either. But that's ok, I'll just come up with another name and create one more. Hopefully it will disappear later on. [18:47:57] kalle: ugh, yea.. hopefully at does. sounds good as long as you don't run into quota issues [18:55:45] And the new one is up. Yay! [18:58:58] cool, so it was some race condition or temp maintenance or so [21:23:42] when you register a new user on wikitech wiki, does it make you confirm the email address before you can use it? [21:23:49] i didn't want to create one just to find this out [21:24:15] um... I think so [21:24:19] it's been a few months since I did it [21:34:38] ningu: thanks. i just tested it anyways. and i am logged in right away :p [21:34:54] which isn't great if that is used to determine who is WM staff :p [21:34:58] I think you need to confirm the email to fully enable it though? [21:35:15] would you know what the difference is between semi and fully enabled? [21:35:38] I don't remember... maybe to use phabricator for example? [21:36:46] I just remember there being a few steps to get all that set up, but I don't remember enough details at this point to be more helpful, sorry [21:37:02] mutante: there is a flag inside the MediaWiki database for email confirmation [21:37:12] ningu: alright, thanks [21:37:35] but I don't know that I would call it a secure thing if you are thinking about automating stuff related to LDAP group membership [21:38:19] the email confirmation flag is only used by MediaWiki to decide if it will send you emails about watchlist changes and things like that [21:38:34] bd808: ACK, but nobody uses that i think. no, i am not trying to automate stuff, i am just trying to answer if anyone could create a user for someone else [21:38:57] so "go to mwmaint and check LDAP for the email address" is not a verification [21:39:19] its pretty sketchy [21:39:21] discussing issues we will have when the corp LDAP goes aways [21:39:34] basically we won't have a method left to check who is staff and who is not [21:39:47] hmm... that's a fun one [21:40:21] hmmm I see [21:40:23] WMF really needs to provide an orgchart [21:40:35] oh, there isn't one? [21:40:37] i don't get how that is asking too much [21:40:47] mutante: namely [21:40:58] that's the "best" system of record in my experience [21:41:01] bd808: i am being told we have to wait until 2021 for that to have the info [21:41:11] it still gets out of date but not as bad as other lists [21:41:20] I'm working with a WMF employee who, supposedly, is the only WMF employee who works on wikisource [21:41:29] not sure if that info is publicly available [21:41:43] ningu: what does "work on wikisource" mean? like editing it? [21:42:18] mutante: no, I think like coordinate and monitor different communities and their needs [21:42:26] or integrate into larger WMF initiatives [21:43:07] ningu: yea, i don't know if that work happens in public. i would hope so, but might be just email-based [21:43:11] I think he edits it too but tthat's not what he meant [21:43:19] mutante: I don't mean that the work is public, I meant his status [21:43:28] like if I want to look up WMF employees who are responsible for wikisource [21:43:44] first you have to define "responsible" :) [21:43:48] hehe [21:43:59] well like it's part of their job description in some way [21:44:48] ok, he's a program officer in GLAM [21:45:37] There are a whole bunch of us who work on software things and those intersect with the project wikis. But that is different than trying to influence what happens in the projects. [21:45:56] yeah I didn't mean influence what happens [21:46:02] I'm still trying to fully understand his role to be honest [21:46:29] he doesn't do software, I think it's more promoting otherwise under-represented groups to contribute and making sure they know how to do it etc [21:46:39] but he knows a lot about how wikisource is structured from a user perspective [21:47:27] which is kind of a niche thing compared to wikipedia [21:48:42] by the way, it's looking like the tool I've been working on for wikisource would be better deployed as a gadget. is it ok to host the js/css assets on toolforge? [21:48:59] the main ones I mean, obviously the gadget has to have code to load them [21:49:31] ningu: "maybe". The folks on the Security team have been working towards making that something that will at least need a user opt-in (loading js from toolforge) [21:49:41] hmm i see [21:50:01] so generally speaking if I want to do that, is there a recommended way? [21:50:08] it's a react app which will load on certain pages [21:50:20] effectively an alternative to proofreadpage which is optimized for this use case [21:50:21] ningu: you might want to talk to someone like Krinkle who has managed complex gadgets. There are patterns for hosting the code in a git repo and using a bot to sync things to the wikis [21:50:29] hmm ok [21:50:47] I mean yeah, that could work too... it's got a whole webpack toolchain but we could always commit the output [21:51:07] react + gadget sounds nasty in all honesty [21:51:25] yeah but the alternative is worse [21:51:34] we don't want to reimplement the proofreadpage content model [21:51:50] people still need that form where they can add their summary, page status, etc [21:52:23] which, sure, we could do with our own interface (which we'd then have to localize) and send it via api using proofreadpage's content model, but... why? [21:52:47] also the react app is already written and seems to work just fine :P [21:52:53] so it's less work to just use it [21:53:51] ningu: I don't know how busy he is, but Krinkle is probably your best bet for informed ideas. He is a js wizard (jquery core committer), has done a lot of work with both tools and gadgets, and is on the WMF Performance team [21:53:58] ok cool [21:54:17] yeah, now is good time to figure this out so we don't go down a long path of something that's a bad idea [21:54:53] ningu: https://www.mediawiki.org/wiki/User:Krinkle [21:55:18] btw user opt in is no issue at all, as long as that can be remembered [21:55:53] and if in the future we have a separate balinese wikisource we can decide if it's auto-enabled or not [21:56:04] or whatever [21:56:21] the tool would have had the oauth confirmation anyway [21:57:06] bd808: any suggestions for contacting cscott? is he just very busy? [21:57:12] (on a separate matter) [21:58:16] I haven't been able to reach him via irc or email [21:59:24] ningu: cscott always has about 100 things going. :) I don't know what hours he's working these days. But email and irc are how I would try to reach out. [21:59:48] maybe I'll just do the languageconverter stuff myself and propose a pull request [21:59:56] I just wanted to run the design by him first [22:00:04] since it's a departure from current stuff [22:02:30] ningu: for irc pokes to him, I would try #mediawiki-parsoid during the US East coast work day (something like UTC 01:00 - 21:00) [22:04:14] ok cool, thanks