[00:06:09] <bd808>	 Is there a protocol for creating "bot" phabricator accounts?
[00:06:40] <bd808>	 I guess I could make a wikitech or SUL account but that seems possibly overkill
[00:07:31] <wikibugs>	 6Project-Creators, 15User-greg: Create #scap and #trebuchet components - https://phabricator.wikimedia.org/T126261#2013616 (10greg) To #scap: * https://phabricator.wikimedia.org/maniphest/?ids=126372,125108,122914,122913,121597,121585,121276,120104,120103,120102,118772,118760,118745,118738,118478,118206,116634...
[00:18:16] <greg-g>	 bd808: I don't remember
[00:20:27] <greg-g>	 (lame response, I know)
[00:24:54] <wikibugs>	 6Phabricator: Evaluate Phabricator for its ability to export and import data - https://phabricator.wikimedia.org/T108199#2013656 (10mmodell) See also: {T123417}  I intend to build an extension that publishes the public phabricator change feed as a usable API with the individual object references (PHIDs) resolved...
[00:36:07] <bd808>	 greg-g: I just made a wikitech account. It may come in handy there too.
[00:41:13] <wikibugs>	 6Phabricator: Evaluate Phabricator for its ability to export and import data - https://phabricator.wikimedia.org/T108199#2013684 (10mmodell) You are probably already aware of this, but the new edit engines feature provides standardized conduit APIs. This means it is becoming more straightforward to [[ https://se...
[00:51:17] <wikibugs>	 6Phabricator: investigate hiding the policy controls for phabricator projects. - https://phabricator.wikimedia.org/T120903#2013710 (10mmodell) >>! In T120903#1865177, @Krenair wrote: > I don't think my proposal about limiting who can change project edit policies themselves would be incompatible with that setup,...
[01:21:23] <wikibugs>	 6Phabricator, 5Patch-For-Review, 3Scap3, 7WorkType-Maintenance: Refactor phabricator module in puppet to remove git tag pinning behavior - https://phabricator.wikimedia.org/T125851#2013788 (10mmodell)
[01:21:26] <wikibugs>	 6Phabricator, 5Release, 7WorkType-Maintenance: Next Phabricator Upgrade - https://phabricator.wikimedia.org/T120013#2013787 (10mmodell)
[01:24:02] <wikibugs>	 6Phabricator, 5Release, 7WorkType-Maintenance: Next Phabricator Upgrade - 02-18-2016 - https://phabricator.wikimedia.org/T120013#2013802 (10mmodell)
[01:25:59] <wikibugs>	 6Phabricator, 5Release, 7WorkType-Maintenance: Next Phabricator Upgrade - 02-18-2016 - https://phabricator.wikimedia.org/T120013#1842651 (10mmodell)
[01:33:31] <wikibugs>	 6Project-Creators: Using Tags (yellow) for Pragmatic Personas - https://phabricator.wikimedia.org/T124729#2013831 (10aripstra) @Aklapper I am not sure which "we" you are referring to in the task description. I don't see a "we" in the task description in this task. The link behind your question above "who is 'we'...
[01:39:27] <wikibugs>	 6Phabricator, 3Scap3, 7WorkType-Maintenance: Move /srv/phab/repos to /srv/repos - https://phabricator.wikimedia.org/T125853#2013839 (10mmodell)
[03:42:18] <bd808>	 twentyafterfour: which conduit method adds a comment to an existing task?
[03:42:40] <twentyafterfour>	 bd808: I don't know if there is a method for that
[03:42:49] <twentyafterfour>	 well duh there must be
[03:43:06] <twentyafterfour>	 (jenkins does it, etc.)
[03:43:15] <bd808>	 none of the maniphest.* calls look right
[03:43:46] <bd808>	 yeah. If you can point me at the repo of something that does it I can dig around
[03:44:08] <bd808>	 phab automation seems to be badly documented black arts
[03:44:12] <twentyafterfour>	 bd808: https://secure.phabricator.com/conduit/method/maniphest.update/   has a comments field
[03:44:37] <bd808>	 ah. yup
[03:45:23] <bd808>	 cool. I'll see if I can make that work then
[03:49:50] <twentyafterfour>	 bd808: https://secure.phabricator.com/conduit/method/maniphest.edit/ is the new way
[03:49:57] <twentyafterfour>	 probably easier/better to use that one
[03:50:13] <twentyafterfour>	 it's transactional rather that record-based
[03:50:31] <twentyafterfour>	 also it's documented: https://secure.phabricator.com/book/phabricator/article/conduit_edit/
[03:51:16] <bd808>	 are we getting that "soon"?
[03:51:53] <twentyafterfour>	 yeah
[03:52:02] <twentyafterfour>	 hopefully next week
[03:53:06] <twentyafterfour>	 it's on phab-scap.wmflabs.org and phab-01 though phab-01 is partially broken (can't log in to ssh at the moment, the web interface nonetheless seems to work)
[03:54:04] <bd808>	 it worked! -- https://phabricator.wikimedia.org/T126419?workflow=create#2014002
[03:59:55] <twentyafterfour>	 cool, what's stashbot?
[04:00:37] <bd808>	 it's the python bot I have that feeds https://tools.wmflabs.org/sal/ and http://tools.wmflabs.org/bash/
[04:01:32] <bd808>	 I'm going to see if I can make it post !log notices to tasks that get mentioned
[05:40:05] <twentyafterfour>	 bd808: that's cool. you should also make it post links in IRC to tasks that get mentioned - the way phabbot does
[05:40:12] <twentyafterfour>	 e.g. I say T123
[05:40:35] <bd808>	 It could totally do that
[05:40:37] <twentyafterfour>	 phabbot says "T123: Turn on "diffusion.allow-http-auth"
[05:40:50] <twentyafterfour>	 +link to T123
[05:41:21] <twentyafterfour>	 or we could just enable phabbot but that's just yet one more bot
[05:41:26] <bd808>	 make a feature request :) -- https://github.com/bd808/tools-stashbot/issues
[05:42:17] <bd808>	 right now it is recording irc into an Elasticsearch cluster and then powering the 2 tools I linked before
[05:42:34] <bd808>	 "someday" I want to make an irc viewer app too
[05:45:38] <twentyafterfour>	 interesting
[05:46:35] <twentyafterfour>	 by irc viewer you mean a log browser / search tool?
[05:46:43] <bd808>	 yeah
[05:46:49] <twentyafterfour>	 that would be pretty nifty
[05:47:21] <bd808>	 we have a couple of different tools today that you can use to look at channel logs, but no search and no cross channel correlation
[05:47:42] <twentyafterfour>	 it would be neat if IRC clients could pull in history from something like that (or even plain text logs on an http server) instead of each client maintaining it's own channel history
[05:48:07] <bd808>	 "mattermost" :)
[05:48:31] <twentyafterfour>	 search and cross channel correlation would be super cool
[05:48:54] <twentyafterfour>	 treat a bunch of irc channels like twitter ;)
[05:49:03] <bd808>	 *nod*
[05:49:38] <bd808>	 I had a Kibana front end on a previous version of the ES cluster. It was nice to play with
[05:49:58] <bd808>	 easy to stalk people across channels
[05:50:28] <twentyafterfour>	 neat
[05:51:25] <twentyafterfour>	 I worked on http://about.psyc.eu/ for a while, a few years back... it has a ton of cool 'slack' type features, as well as distributed social network features and persistent presence (your account is essentially a bot that you connect to with a client when ever you want to access the network)
[05:51:58] <twentyafterfour>	 but bad-old-irc has the advantage of being ubiquitous
[05:53:59] <bd808>	 YuviPanda and RobLa are interested in finding a good FLOSS irc replacement. There is a lot of resistance to be overcome though from folks who are irc old timers
[05:54:20] <bd808>	 the mattermost server that Yuvi setup has an irc bridge which mostly works
[05:55:02] <twentyafterfour>	 psyc is one of the coolest projects I've ever been involved in (or even witnessed) ... and it interoperates with IRC. but it's lacking in polish, mostly focused on the low level technologies rather than client-facing applications
[05:55:44] <bd808>	 ah. they are looking for the inverse. They want something more slack like for the users
[05:55:52] <bd808>	 shiny and easy to use
[05:55:55] * robla reads backlog a little
[05:56:00] <twentyafterfour>	 yeah
[05:56:25] <twentyafterfour>	 is elasticsearch a good fit for a chat backend? it kinda seems well suited to the task
[05:57:17] <bd808>	 it's good for the search bits but crappy for a cursor over incoming messages
[05:57:56] <bd808>	 you basically have to remember where you left off on the client side an poll
[05:58:05] <twentyafterfour>	 hmm...
[05:58:06] <robla>	 take it from a guy responsible for authoring a bad protocol; IRC is truly awful
[05:58:13] <bd808>	 so its ok for an archive thing but not a live client
[05:58:48] <twentyafterfour>	 psyc is actually a great protocol
[05:59:10] <robla>	 twentyafterfour: sticking with IRC would be similar to sticking with FTP in 1995
[05:59:40] <twentyafterfour>	 robla: yeah but interoperating with IRC is important
[05:59:53] <robla>	 twentyafterfour: as was interoperating with FTP
[06:00:20] <twentyafterfour>	 in order for a tool to catch on it'll have to coexist for a while
[06:00:35] <robla>	 sure.  same with FTP
[06:00:48] <twentyafterfour>	 robla: I'm not arguing with that ;)
[06:00:55] <robla>	 what does psyc have that will make it beat Slack?
[06:01:38] <twentyafterfour>	 robla: it's open and the guys who designed it have spent the past 30 years thinking about messaging/conferencing protocols
[06:02:03] <twentyafterfour>	 but it's not shiny or user-friendly at all so it probably isn't the answer unless someone comes along and makes a pretty client for it
[06:02:23] <robla>	 oh, I see, the world cares about experience designing protocols.  they don't care about user interface.  got it
[06:02:37] <twentyafterfour>	 (that wiki is a treasure trove of information, btw, about all things chat)
[06:02:58] <twentyafterfour>	 robla: I never said it was going to beat slack ;)
[06:04:04] <twentyafterfour>	 but every modern chat system I've looked at is just a pretty face on top of a horrible back-end (like IRCAnywhere uses mongoDB and despite mongodb being "webscale" IRCAnywhere completely does not scale)
[06:04:28] <twentyafterfour>	 (http://www.mongodb-is-web-scale.com/)
[06:05:11] <robla>	 I tune out when I hear y'all dismissively talk about "pretty face" as if user experience is irrelevant
[06:05:53] <robla>	 we're going to get our collective butts kicked by the proprietary world because we're a bunch of nerds that write off user experience
[06:06:00] <twentyafterfour>	 robla: I don't think it's irrelevant, in fact I think it is very relevant and that's why psyc is still obscure after more than 20 years ;)
[06:06:20] <robla>	 so....what do you think of Mattermost?
[06:06:41] <twentyafterfour>	 I haven't seen it before, I just started checking it out. looks good so far
[06:07:30] * robla looks for twentyafterfour on Yuvi's test instance
[06:07:47] <twentyafterfour>	 robla: where is yuvi's test instance? I haven't used it
[06:08:00] <robla>	 http://mattermost.wmflabs.org/wikimedia/channels/town-square
[06:08:07] <twentyafterfour>	 I only googled mattermost just now when bd808 mentioned it
[06:15:03] <robla>	 bd808: party moved over to mattermost.wmflabs.org  :-)
[06:43:02] <wikibugs>	 6Phabricator, 15User-bd808: pick up ticket mentions from !log lines - https://phabricator.wikimedia.org/T108720#2014071 (10bd808) a:3bd808 I've gotten far enough in playing with this in the last few hours to lick the cookie. I'll take a stab at adding the functionality to the https://github.com/bd808/tools-s...
[10:32:07] <wikibugs>	 6Phabricator: Set up redirects from RT URLs to Phabricator - https://phabricator.wikimedia.org/T41#2014351 (10mark) What was the use case for this anyway?  I believe all RTs included the RT ticket nr anyway. I think the limited user base of RT is smart enough to be able to search for the RT number in Phabricator...
[11:14:02] <wikibugs>	 6Phabricator: Create Outreachy-Round-12 project in Phabricator - https://phabricator.wikimedia.org/T126443#2014465 (1001tonythomas) 3NEW
[11:14:14] <wikibugs>	 6Phabricator, 6Developer-Relations: Create Outreachy-Round-12 project in Phabricator - https://phabricator.wikimedia.org/T126443#2014473 (1001tonythomas)
[13:17:53] <wikibugs>	 6Project-Creators, 6Developer-Relations: Create Outreachy-Round-12 project in Phabricator - https://phabricator.wikimedia.org/T126443#2014686 (10Aklapper)
[13:18:05] <wikibugs>	 6Project-Creators, 6Developer-Relations: Create Outreachy-Round-12 project in Phabricator - https://phabricator.wikimedia.org/T126443#2014465 (10Aklapper) ( #Project-Creators territory, not #Phabricator )
[13:18:17] <wikibugs>	 6Project-Creators, 6Developer-Relations: Create Outreachy-Round-12 project in Phabricator - https://phabricator.wikimedia.org/T126443#2014688 (10Aklapper) a:3Aklapper
[13:20:03] <wikibugs>	 6Project-Creators, 6Developer-Relations: Create Outreachy-Round-12 project in Phabricator - https://phabricator.wikimedia.org/T126443#2014694 (10Aklapper) 5Open>3Resolved Project has been created: https://phabricator.wikimedia.org/project/profile/1761/
[17:22:27] <ostriches>	 twentyafterfour: Is there a way to de-attach an LDAP account an attach a new one?
[17:22:51] <ostriches>	 Dumb question.
[17:22:52] <ostriches>	 Yes.
[17:22:54] <ostriches>	 https://phabricator.wikimedia.org/settings/panel/external/
[17:23:02] <twentyafterfour>	 ostriches: yes but you need to have an alternate way of logging in so set up oauth first
[17:51:45] <mutante>	 i want to find out how to create more/custom award tokens
[17:52:17] <mutante>	 so i can have an ostrich besides the pterodactyl.. and give it to ostriches for renaming people
[17:52:39] <ostriches>	 Hehe, I dunno how :)
[17:52:49] <mutante>	 the memes are too large, but the awards are just right
[17:52:59] <mutante>	 and the pterodactyl and cactus become boring
[17:53:12] <mutante>	 asked #phabricator :p
[17:56:02] <greg-g>	 what would you call the ostrich? Big Bird?
[17:56:17] <James_F>	 Neck Bird.
[17:57:51] <ostriches>	 Flightless bird
[17:59:08] <ostriches>	 Actually James_F is right...neck bird
[18:03:21] <mutante>	 also.. barnstar icons
[18:12:26] <greg-g>	 mutante++
[18:23:39] <twentyafterfour>	 mutante: we could just patch the source
[18:23:54] <twentyafterfour>	 likely to break at some point but not that difficult to maintain
[18:24:54] <mutante>	 twentyafterfour: i'll try to make a change in our parsoid repo then :)
[18:25:05] <mutante>	 then one you now deploy from, right
[18:25:19] <mutante>	 i saw that change to remove the old way to deploy stuff
[18:25:39] <mutante>	 the tag pinning
[18:27:03] <greg-g>	 quid pro quo?
[18:32:58] <mutante>	 yea:)
[18:45:14] <twentyafterfour>	 mutante: deploy from https://phabricator.wikimedia.org/diffusion/PHDP/
[18:45:33] <twentyafterfour>	 https://phabricator.wikimedia.org/diffusion/PHAB/browse/production/;9d372ca91f4957e95689c5c930c6ca2ef7272194
[18:46:07] <mutante>	 twentyafterfour: ok! thanks
[18:47:36] <twentyafterfour>	 it looks like the tokens use a sprite image rather than a glyph font, so that kinda sucks for maintainability - have to edit spritesheet image and region definitions
[18:47:48] <twentyafterfour>	 resources/sprite/manifest/tokens.json
[18:48:30] <mutante>	 heh, editing "sprites", last time was on a Commodore
[18:48:52] <twentyafterfour>	 src/applications/tokens
[18:49:24] <twentyafterfour>	 _joe_  wanted to add a bullshit token
[18:49:35] <mutante>	 mr.hanky?
[18:49:47] <twentyafterfour>	 yeah
[18:50:05] <twentyafterfour>	 the naming 'tokens' is unfortunate - grepping for that word gets a lot of false positives ;)
[18:50:33] <mutante>	 greps for pterodactyl
[18:50:51] <mutante>	 hah
[18:50:53] <mutante>	 src/applications/tokens/query/PhabricatorTokenQuery.php:      array('misc-1', pht('Pterodactyl')),
[18:51:28] <twentyafterfour>	 ;)
[18:56:38] <mutante>	 .. but in the wrong directory where i had a really old checkout
[19:00:45] <mutante>	 eh, when i do this
[19:00:47] <mutante>	 git clone https://gerrit.wikimedia.org/r/p/phabricator/deployment
[19:00:52] <mutante>	 i dont actually get those files
[19:01:25] <mutante>	 submodules ? sigh
[19:59:03] <wikibugs>	 6Project-Creators: Using Tags (yellow) for Pragmatic Personas - https://phabricator.wikimedia.org/T124729#2016122 (10Aklapper) >>! In T124729#2013831, @aripstra wrote: > @Aklapper I am not sure which "we" you are referring to in the task description. I don't see a "we" in the task description in this task.  That...
[21:55:23] <twentyafterfour>	 mutante: you can just check out the phab repo directly instead of the deployment module
[21:55:42] <twentyafterfour>	 the deployment module is really just for scap3 usage
[22:14:59] <mutante>	 twentyafterfour: ok! thx