[00:01:24] 10Gitblit-Deprecate, 10Diffusion, 10Gerrit-Migration, 6Release-Engineering-Team: Import all gerrit.wikimedia.org repositories with Diffusion - https://phabricator.wikimedia.org/T616#1744502 (10mmodell) @demon: it looks like upstream has a solution for us: >@[[ https://secure.phabricator.com/T4245#135441 |... [00:07:43] 6Project-Creators: Clarify #Phabricator project confusion - https://phabricator.wikimedia.org/T112040#1744529 (10chasemp) just a note that this exists https://phabricator.wikimedia.org/project/view/1081/ [00:19:03] 6Phabricator: Visibility of files should be public by default - https://phabricator.wikimedia.org/T115848#1744568 (10Negative24) Oh I see. When a file is uploaded via drag-and-drop it inherits the policy from the task and the Files policy is set to private because its assumed the file wouldn't need to be accesse... [00:20:47] 6Phabricator: Visibility of files should be public by default - https://phabricator.wikimedia.org/T115848#1744569 (10Negative24) I think some documentation should be written on this. I'm afraid code comments aren't commonly read by regular users. :) [09:47:43] 6Project-Creators, 10Internet-Archive, 10The-Wikipedia-Library: Create Internet Archive Project - https://phabricator.wikimedia.org/T115306#1745037 (10Aklapper) 5Open>3Resolved H99 created: * When any of these conditions are met: ** Description contains Internet Archive ** Description contains archive.o... [10:13:35] 6Project-Creators, 10Phabricator-Upstream, 15User-Bd808-Test: Per-user projects for personal work in progress tracking - https://phabricator.wikimedia.org/T555#1745102 (10Addshore) @JAufrecht > In particular, what are you trying to use it for? personally I will just use it for tracking and planning my... [11:23:26] 6Phabricator: Visibility of files should be public by default - https://phabricator.wikimedia.org/T115848#1745182 (10Aklapper) >>! In T115848#1744569, @Negative24 wrote: > I think some documentation should be written on this. I'm afraid code comments aren't commonly read by regular users. :) @Negative24: Would... [13:10:32] 6Phabricator: Visibility of files should be public by default - https://phabricator.wikimedia.org/T115848#1745318 (10Negative24) >>! In T115848#1745182, @Aklapper wrote: >>>! In T115848#1744569, @Negative24 wrote: >> I think some documentation should be written on this. I'm afraid code comments aren't commonly r... [14:12:08] hey all, is anyone evaluating mattermost.org ? [14:21:27] I sent an email to wikitech-l, feel free to respond there as well [14:23:51] 6Phabricator, 5Patch-For-Review, 7Regression: Phabricator login page does not show Welcome text / "Click button below" text anymore - https://phabricator.wikimedia.org/T116142#1745392 (10Dzahn) Do we want to do what it says in that linked upstream ticket? " get equivalent behavior by putting a file like thi... [14:52:04] bgerstle: I don't personally find a slack clone to be any more compelling than slack itself. And open source walled garden is still a walled garden. Communications should really happen over open protocols with a breadth of client and server support IMO. [14:56:07] bd808: FWIW they do have plans for export/import functionality https://mattermost.atlassian.net/browse/PLT-22?filter=10002 [14:57:17] *nod* [14:58:11] i also mentioned in the email there's a feature request for an IRC bridge [14:59:27] lastly, if we think this kind of tool is cool and offers some nice functionality which plain IRC/XMPP can't solve, maybe encouraging the development of an open tool like this could lead to a standard [14:59:55] I'm still a bit confused about what makes irc too hard to use, but I suppose it is the lack of bouncers for most people [15:00:29] bd808: perhaps (which is why IRCCloud was a nice step towards having more user-friendly chat tech) [15:00:39] 6Phabricator, 6operations, 7audits-data-retention: Enable mod_remoteip on Phabricator and ensure logs follow retention guidelines - https://phabricator.wikimedia.org/T114014#1745468 (10chasemp) >>! In T114014#1745461, @greg wrote: > I like Phab's 403 page: "Peace out" :) > > Since I can't see it: how much d... [15:01:20] 6Phabricator, 6operations, 7audits-data-retention: Enable mod_remoteip on Phabricator and ensure logs follow retention guidelines - https://phabricator.wikimedia.org/T114014#1745469 (10greg) good! [15:01:25] bd808: i think at the end of the day it's a UX thing. Slack et. al just have better UX so people enjoy using it more [15:02:07] type things, read things. I'm not sure there is much more user experience than that [15:02:13] bd808: have you tried Slack? [15:02:16] but maybe I just don't get it [15:02:36] nope. [15:04:25] i see, if you ever get a chance to try it out i think it would offer a lot more perspective on why people want to use something like it [15:05:15] like i said, IRCCloud is a step in that direction, but Slack still has a few things which make it nicer to work with. off the top of my head, mostly being able to do inline markdown/GHFM formatting [15:05:41] but also digests & email notifications so it's easier to track mentions while you were away [15:05:51] not to mention file storage, etc. [15:05:56] heh. "rich messages" is one of the things I'm sure I would hate about it [15:06:02] anyway "don't know it 'til you try it" [15:06:09] s/know/knock/ [15:06:28] bd808: also, you could use your argument to say "I don't understand why people need IDEs" [15:06:40] you know what else was better, betamax :) [15:06:57] and... I make that argument too [15:07:09] chasemp_: you mean, like the precursor to VHS? [15:07:21] i.e. would we force everyone who developed for WM projects to use vim/emacs? [15:08:04] no, but switching to a closed comms platform just that [15:08:27] it is exactly like forcing everyone to use emacs [15:09:21] (I'd recommend talking about this in -tech, not here, -tech gets a wider audience) [15:09:33] * bd808 rants in a dark corner [15:10:19] I haven't even finished my coffee yet, I'm not ready to rant, it'd spoil my day ;) [15:11:37] bd808: i see, so don't think we should force someone to use a particular client (which using mattermost would effectively do) [15:12:06] that's kind of confusing as it seems like you are against mattermost there [15:12:46] chasemp: meant to clarify what bd808 was saying: using mattermost means we limit people's options for how they communicate w/ us in real time [15:12:55] I'm against anything that isn't an established communications platform/standard [15:13:07] 6Phabricator: Phabricator scripts directory needs to be readable and executable by phd.user - https://phabricator.wikimedia.org/T105575#1745509 (10Negative24) a:5Negative24>3chasemp [15:13:10] XMPP, irc are fine [15:13:19] bd808: as an aside we are going to ferm (fw) up logstash things here [15:13:20] fyi [15:13:24] hipchat, slack, slack clones are not [15:13:33] chasemp: +1 [15:13:46] right, so if mattermost allowed for clients to connect & communicate using XMPP/IRC, you'd be happier [15:13:59] yeah, that would be swell [15:14:16] 6Phabricator: Phabricator scripts directory needs to be readable and executable by phd.user - https://phabricator.wikimedia.org/T105575#1447013 (10Negative24) Going to leave this for @chasemp. I'm not going to try anything until #Gerrit-migration calls for it. [15:15:15] as long as the canonical location for information is the non-slack-like-thing, then it's probably fine [15:15:24] as much as i'm interested in this conversation, i need to move onto other things, so one last question... i need to do more research into the evolution of open standards, but is it far-fetched to claim that nurturing a project like mattermost could result in the evolution & ratification of a new open protocol that supports slack-like features? [15:15:34] but, as soon as some teams start using it, then they'll use all the special sauce, which means others will lose the ability to see it [15:16:04] bgerstle: impossible to tell without knowing what their devs think and the wider community thinks [15:16:22] community of open commms protocol people, that is [15:16:32] gotchya [15:16:46] greg-g: also: what if there's pretty much 0 barrier to using mattermost? [15:16:49] I don't know it very well, other than the Open Social Web people [15:17:06] bgerstle: doesn't address any of my concerns :) [15:17:08] i.e. people using the IRC gateway should, in theory, have nothing stopping them from using the web client (or some other mattermost client) instead [15:17:14] I'm worried about segragating of information/people [15:17:22] The next question in that line is whether or not the Wikimedia community is interested in spending their energy/resources on promoting a new communications protocol [15:18:04] I don't think anyone would care if someone had a slack to irc bridge [15:18:10] and it affected no one one who didn't want to change [15:18:25] so effectively we are taking a single payer comm system if we have to negotiate at all :) [15:18:48] which is just almost untenable from a complexity of change situation when we consider that irc is defacto for all OSS communities I imagine [15:20:23] not sure what you're getting at chasemp. is it that some people who are accustomed to IRC wouldn't know the difference if we used mattermost as long as they could connect to our channel(s) using typical IRC methods? [15:20:50] no it's that if you are talking about a change for you where you use slack or whatever and run some bridge that makes it transparent to everyone else [15:20:57] then there isn't probably much to talk about, would anyone care? [15:21:09] if you mean to pursue other-than-you adoption then it's an unsolvable problem [15:21:31] everyone else feels teh same way about some means of use as you do about whatever you like, vim/emacs etc [15:21:53] Its really more the other direction. We have a 10+ year investment in irc and related tooling, so any replacement has to prove it can replace everything (bots, archives, client interoperability, ...) [15:22:17] sure but would you care if I was typing into a slack client right now? [15:22:22] nope [15:22:26] +1 chasemp [15:22:28] so there you go [15:22:41] it is one of two problems, either you find a way to make it useable w/ irc or it's not tenable [15:22:45] and you can never force a switch [15:22:49] and nothing can do the bridging well [15:22:52] that I have seen [15:23:00] just like I don't care that you use mIRC still, chasemp :P [15:23:03] chasemp: so, IRCCloud makes it pretty seamless [15:23:22] I use limechat greg-g! [15:23:28] which I'm not proud of [15:23:34] e.g. if i upload a file or put in a snippet of some kind [15:23:49] people using an augmented client (i.e. Slack, IRCCloud, Mattermost) would see it embedded etc. [15:23:58] others would see a link that they would have to click [15:24:08] so there isn't (AFAIK) must loss of information [15:24:28] also, IRC doesn't provide ways to search history etc., so you'd have to go outside of IRC for that anwyay [15:24:30] anyway* [15:25:00] my earlier point is that using something that bundles those "extra" features, and is open, might provide an opportunity for standardizing that cluster of features—if that's even possible [15:25:43] in any case, those standards would probably need to be proposed based off of working proofs of concept. like i said, i don't know much about standards, but it seems more feasible to develop them outside of a vacuum [15:26:20] s/must loss of information/much loss of information/ [15:26:28] this is guerrilla adoption territory I think dude, you gotta bootstrap viability at the same time as proposing [15:26:30] right, without knowing the whole situation, proposing that this one specific option could help create an open standard is just vapor ware and doesn't mean anything :) [15:26:32] and then build critical mass [15:26:49] I've actually created an open standard :) [15:27:01] well, lead/managed the working group [15:27:11] greg-g: right, but i think what myself and chasemp are saying is, we need to try it to see if it works and then see where it goes if we like it [15:27:27] instead of waiting for someone to come to us w/ something standardized [15:27:44] that's fine, just don't try to smoke screen an experiement with possible "open standard!" rhetoric that is just vapor ware [15:28:05] not sure what you mean by "smoke screen," i was just asking a question [15:28:12] i wasn't trying to make any claims about anything [15:28:15] :) [15:28:20] I mean... play it up? [15:28:29] greg-g: you're twisting my words, i think [15:28:42] i'm not trying to mislead anyone [15:29:11] kk, then I simply mean: don't talk much about the open standard since that's no where to be seen yet and isn't really a viable reason to think about switching any time soon :) [15:29:24] (at least afaict) [15:29:31] ok [15:30:01] people will think you're trying to make it seem better than it is (which is what I'm trying to prevent you from sounding like, I know you're not) [15:31:12] "you're trying to make it seem better than it is"... i guess if that's how you see it. i'm just expressing my opinion [15:31:48] which i qualified by saying i'd need to do more research on the development of standards. and in this case i would defer to you as you have more experience in this area [15:32:11] no no, I said people will see it as that since it's not a real option [15:32:14] I said I konw you're not :) [15:32:39] can you clarify what you mean by, "since it's not a real option"? [15:33:38] it sounds like you're saying "i think this shouldn't be evaluated [for the reasons you stated above, lacking open protocol support, etc.]" [15:33:42] merely the idea that us using any of these tools will help the creation of an open standard in the space is wishful thinking, and to use it as an argument for use of any of them won't help [15:33:54] ok [15:34:25] that's all I meant to communicate :) [15:34:50] i'm curious then, what would you recommend for people who want a Slack-like client, but also want to promote development of FOSS & open comm protocols/standards? [15:35:22] aside from making their own start-up whose sole purpose is to create said protocol and an implementation of it [15:35:34] irccloud? :) I'm not the person to ask, honestly. My .irssi/config file is 10 years old [15:35:45] ok [15:36:11] greg-g I love that you are in unintentional hipster [15:36:18] chasemp: it pains me [15:36:36] :) [16:05:05] "unintentional hipster". :D [16:17:27] bgerstle: I don't understand why slack/mattermost need a new protocol. Is it really impossible for them to build on, or at a minimum bridge to, either irc or xmpp? There is a ton of value leveraging existing protocols (and therefore users) [16:18:32] meeple27: there's a feature request for adding an IRC bridge, not sure how they send/store data [16:18:44] and how compatible that is w/ existing standards [16:19:10] obligatory xkcd reference: https://xkcd.com/927/ <-- bd808 greg-g [16:19:20] right. Just seems like anyone who values open stuff would start from an open protocol, push it to its limits, and then maybe do some optional extensions to it [16:19:26] rather than starting from something all new [16:19:36] * bgerstle shrugs [16:19:39] nih is a powerful force, of course. "I can do it better!" [16:20:21] you asked for recommendations, but framed it as needing a new protocol. I'm just questioning the premise [16:20:25] yeah, i'm _guessing_ that if they could've leveraged some Erlang(?) IRC/XMPP implementations to bootstrap their efforts they would have? [16:20:35] google ditched XMPP for gchat *because* it was an open standard. They got mad that microsoft built support into their client for gchat. [16:20:55] and adium, etc. [16:21:00] those don't work anymore? [16:21:44] adium still has a plugin and I think google still runs an xmpp bridge but you can't federate with other xmpp servers anymore [16:22:19] actually I know they have a bridge because that's how I get gchat messages from WMF folks (xmpp to adium) [16:22:26] i see [16:22:38] i haven't had much success using gchat in other clients [16:22:46] was usually a bit wonky [16:23:52] meeple27: also, i meant to ask for recommendations for things people should use if they want to promote existing/new standards for Slack-like chat experiences [16:24:08] meeple27: as opposed to recommendations _for a standard_ [16:24:31] (which is sort of a subset of my original request: i.e. "use something that's built on top of an RFC for a standard") [16:25:05] bgerstle: limechat and textual do inline media from urls if that's mostly what you are looking for [16:25:23] would still need a bouncer [16:25:23] and irc includes formatting support (colors and bold at least) [16:26:05] that's what's nice about IRCCloud, it does everything you mentioned plus being a bouncer, tracking transcripts etc. [16:26:20] yep. [16:26:40] bgerstle: ah, thanks for the clarification. that makes sense [16:26:46] problem solved! [16:26:52] but we don't use it as our canonical chat medium, instead opting for a conglomeration of IRC channels on freenode + manual logging to some archives [16:27:13] irccloud is just a client [16:27:22] it's more than that though [16:27:22] I don't see the correlation [16:27:56] no, it's really not. I have all the things you are saying it provides (or at least the ones I want) with my clients [16:27:57] it stores previous chats/mentions, keeps an archive of things i've uploaded [16:28:10] textual can act as a bouncer? [16:28:18] znc + textual + colloquy for my phone [16:29:08] right, so IRCCloud = bouncer (znc) + clients (web & apps) [16:29:08] I have logs, replay on connect, and push notifications [16:29:21] i.e. more than a client [16:29:24] but a bouncer is just a client. [16:29:34] * bd808 is confused [16:29:51] I think irccloud is great for turnkey users [16:30:05] but I don't see how it has to be "standard" for the community [16:30:39] anymore than your emacs/vim point eariler [16:31:11] so, the advantage to having some thing like IRCCloud/Mattermost/Slack be our canonical chat medium, is that, by using it, you gain access to all of our chat data [16:31:25] otherwise, there's "some assembly required" [16:31:47] vertical integration and all that [16:32:14] bgerstle: you still gain everything irccloud provides by using it yourself without everyone else using it [16:32:20] maybe I'm missing the point [16:32:41] I think he's saying that he wants to count on everyone else having the same experience [16:32:48] and feautres [16:32:48] ah, nope :) [16:33:03] irssi4life, and I'm not putting IRC on my phone :) [16:34:30] but I understand the desire of knowing what someone else is experiencing [16:34:46] i don't think that's really what i'm after [16:35:07] i don't _need_ to know what other people are experiencing as long as they're happy w/ what they're doing [16:35:13] * greg-g nods [16:35:15] and it means our requirements for synchronous chat [16:35:27] meets* [16:35:30] right [16:35:31] :) [16:36:08] which, AFAICT are: 1) highly available (i.e. bouncers) 2) persistent (logs/transcripts) [16:36:24] irccloud :) [16:36:54] and my own setup (ssh+irssi) and bd808 own setup (znc + textual) [16:37:54] one question I never heard back from anyone about slack et al is: do they have the ability, and do they exercise it, to delete logs from user's history? [16:38:04] of course, I only tweeted the question once ;) [16:38:08] i guess part of what i'm saying is that there might be more to non-video chatting than what IRC has to offer [16:38:54] greg-g: don't know about slack, but users can at least edit previous messages [16:39:05] and i'm guessing mattermost would offer more control in that regard (self-hosted) [16:39:27] yeah, I'm wary of anything that lets you rewrite history without verification by a third-party [16:39:44] with IRC, I have my logs, and someone else has there's, if they agree, then we can assume it's valid [16:39:46] i don't know if mattermost also allows editing messages or if that's configurable [16:40:30] what i can say, is that getting non-engineers on IRC has been a challenge, but we seem to have made some progress w/ IRCCloud [16:41:00] maybe we could make even more progress by using something more towards the end of the Slack spectrum, but is at least open source and gives us more control [16:41:18] if people are interested, i think it might be worth trying, and they can report their experience, we can weigh pros/cons, etc. [16:41:40] so, I'm just going to give unsolicited advice here: it sounds like you have a solution looking for a problem. [16:41:59] didn't i state the existing problem just now? [16:42:08] the assumption in your statement is that slack is better, so moving toward it would obviously be beneficial [16:42:18] "assumption"? [16:42:25] 16:40 < bgerstle> maybe we could make even more progress by using something more towards the end of the Slack spectrum, but is at least open source and gives us more control [16:42:35] i'm proposing an experiment [16:42:37] that ^ statement assumes moving towards that end is better [16:42:42] "progress" [16:43:03] i.e. get more people in IRC-like chat rooms [16:43:10] which we seem to have done w/ IRCCloud [16:43:32] I think we agree that irccloud is a win for getting more people on IRC [16:43:51] ok [16:45:25] greg-g: still, i think you're mischaracterizing what i said, which was essentially a hypothesis [16:45:26] not a statement [16:45:46] i.e. "we should try X to see if it has Y effect" vs. "we should do X _because_ it will have Y effect" [16:45:53] gotcha [16:45:58] I did then [16:46:28] but I think we need to define what Y is and what else we've tried to fix Y and how bad the current state of Y is [16:47:02] * greg-g leaves on a positive note [16:47:08] sure, my email was mostly a cheap way to get a gut check to see if anyone was even interested in something like this [16:47:09] +note [16:47:14] yeah [16:47:21] i agree that if we want to do this right, we would try to measure it [16:47:30] try to identify some key results, etc. [16:47:37] OKR4lie [16:47:39] +f [16:48:02] (freud?) [17:22:24] 6Phabricator: Redesign phabricator login page - https://phabricator.wikimedia.org/T862#1745871 (10chasemp) fyi T116142 [17:22:30] 6Project-Creators: Creating several tags for fundraising features - https://phabricator.wikimedia.org/T116296#1745873 (10DStrine) 3NEW a:3DStrine [17:24:45] 6Phabricator: Redesign phabricator login page - https://phabricator.wikimedia.org/T862#1745893 (10chasemp) https://gerrit.wikimedia.org/r/#/c/247793/ [18:36:16] x-post: So before anybody says "I told you so", is there a way to reset my Phabricator 2FA without having a committed identity hash? [18:38:24] parent5446: I told you so! [18:38:40] parent5446: I think in the past andre__afk has done hangouts to verify identities? [18:38:45] :P [18:39:51] It's just I remember there being a discussion about this, and I definitely said something along the lines of "if you lose your 2FA, you're just screwed, so be careful" [18:40:19] has to be reset via cli [18:40:25] and yes andre__afk can do it [18:41:15] Awesome [18:44:49] clearly we need to find a way to do chat in phabricator. >:D [18:47:02] brion: your sarcasm broke my meter :) I dunno whether to say we are or if "that's the joke" [18:47:14] teehee [18:48:50] Not as good as in-wiki chat. Extension:IRC [18:50:39] brion: https://phabricator.wikimedia.org/T92289 [18:51:18] close :D [18:51:49] parent5446: i would actually love a good chat system integrated into the wiki and available like etherpad sidebar during multi-user editing sessions and stuff [18:52:03] but that sounds like a security/harassment nightmare to run more chat stuff [18:52:08] though .... it would be damn useful [18:52:52] mhm, we'd have to keep some sort of permanent logs of all chats, and even then it might cause problems [18:54:48] [ ] I hereby license my private chat messages under CC-BY-SA 4.0 [18:56:00] imagine it fully integrated into mw [18:56:09] you hit the normal Edit button on any page [18:56:16] and just because somebody else did as well it turns into Etherpad [18:56:32] and when you are done with a session it saves [18:57:15] autosave? things just working? mutante you must be thinking of someone else's software ;) [18:57:56] We need to go in the other direction: re-implement Wikipedia as an IRC protocol extension. [18:58:18] heh [18:58:52] so give dispenser the grant for telnet wikipedia [18:59:50] lol [19:44:07] can people mail into an existing ticket? [19:44:34] does task@ still work [19:44:54] it seems more complicated than logging in .. but people want it [19:49:43] what now? [19:49:51] task@ works from an email for a registerd account [19:50:02] we don't do anon tickets and it's been discussed o death [19:54:24] chasemp: managers who "are not on phabricator" yet have to put "approved" on a ticket and ask if they can email [19:54:42] that answer atm is no [19:54:47] i pointed out they can use the normal wikipedia account [19:54:49] with no real way to change that [19:54:51] :p [19:55:04] ok [19:55:49] maybe they meant email a person, but that's even more no :) [19:57:02] even if they could email in as anon [19:57:17] it wouldn't be a very valuable approval then [19:59:21] right [19:59:47] i said "login once" but then could possibly use mail in the future [20:00:28] if they wanna figure out the syntax for task@ and use the right subject i assume it'd be fine [20:19:55] subject doesn't matter, just tasK+1308518250198501@ [20:48:56] greg-g: oh! didnt know, thanks. like 12345@rt.wm.org once [20:56:10] chasemp: managers who "are not on phabricator" yet have to put "approved" on a ticket and ask if they can email [20:56:14] I have a better solution for this problem [20:56:43] why would they "not" be "on phabricator" yet? [20:56:45] Don't give out access to people whose managers don't use phabricator [20:56:53] ^ +1 [20:57:21] I didn't know we had managers who were not on phabricator. amazing [20:57:30] haha [20:58:17] solution: require managers to use phabricator. effective immediately. start a commission to study what went wrong to get us here in the first place. [20:58:33] [20:58:37] survey if we need a survey [20:58:42] then survey about phab use [20:58:43] :) [20:58:50] correlate data with hierarchy points [20:59:10] is there a correlation between it and phab use or not [20:59:38] 100% the commission head will not be on phab [21:00:54] no biggie, google doc and hire contractor to convert to office wiki [21:01:12] hahah [21:01:19] amazon mechanical turk [21:01:54] 6Phabricator: Phabricator scripts directory needs to be readable and executable by phd.user - https://phabricator.wikimedia.org/T105575#1746566 (10chasemp) We have functional diffusion hosting and differential now. what was the catalyst for the change? [21:06:40] mutante: what kinds of things are in phab that need a manager approval from a non-phab manager? [21:06:48] non-phab using* [21:06:53] HR? [21:07:15] greg-g: access requests [21:07:31] shell on stat1002/1003 is like 90% of it [21:07:37] because numbers [21:07:42] everybody needs numbers :) [21:07:51] I think the idea is they are not non-phab managers, they only are acting as non-phab managers [21:08:06] schrodinger's phab manager [21:08:42] mutante: :/ [21:08:46] the rules say their manager needs to sign , but then we do all these "works temp for another team" things, ya know [21:09:02] 6Phabricator: Phabricator scripts directory needs to be readable and executable by phd.user - https://phabricator.wikimedia.org/T105575#1746609 (10Negative24) I believe the VCS user couldn't execute the script that is responsible for checking SSH keys against the Phabricator database which blocked users from aut... [21:11:29] also the part that there is no orgchart tool (anymore) doesn't help. i'd want an API call to get the name of the next person in the hierarchy for a given user [21:12:13] or "is X above Y". then you can actually answer questions like "is it ok if Z approves instead" [21:12:58] parsing the wiki templates for that isnt great [21:13:00] Krenair: thinking about closing this https://phabricator.wikimedia.org/T62215 [21:13:17] last meaningful communication was 17 months ago [21:13:50] fine with me, I have no particular attachment to this ticket [21:14:05] I just moved projects around a bit [21:14:26] mutante: heh, no comment on orgchart craziness [21:15:10] greg-g: we'd just have to assign "boss points", the more you have the more boss you are [21:15:23] no need for drawing diagrams [21:15:34] lol [21:15:47] do you get them by defeating other bosses? [21:16:38] probably there is some complicated formular that includes that, the number of reports, payment level and if there is a C in the title [21:16:40] first rule of boss points you don't talk about boss points [21:22:55] 6Phabricator: Phabricator scripts directory needs to be readable and executable by phd.user - https://phabricator.wikimedia.org/T105575#1746662 (10chasemp) 5Open>3Resolved >>! In T105575#1746609, @Negative24 wrote: > I believe the VCS user couldn't execute the script that is responsible for checking SSH keys... [22:22:50] 6Phabricator, 3Scap3: Deploy Phabricator with scap3 - https://phabricator.wikimedia.org/T114363#1746894 (10greg) [22:32:05] Sigh [22:32:12] Another one: https://phabricator.wikimedia.org/tag/performance_metrics/ [22:34:36] User doesn't even have project creation permissions [23:14:46] user doesn't have project creation permissions? [23:15:17] https://phabricator.wikimedia.org/project/members/835/ [23:33:37] parent5446, https://www.mediawiki.org/wiki/Phabricator/Help/Two-factor_Authentication_Resets [23:33:52] Krenair: I already sent Ori an email about that project to please fix it [23:34:01] ok, thanks andre__afk