Jun 27 2017
May 21 2017
This was basically just a work log for an earlier iteration on Nuance focused on bi-directional bridging with GitHub. We're pursuing Nuance again now, but not with the same focus, so I'm going to close this and reorganize things. Some similar task will likely fall out at the end, but with a better focus on where we're actually headed.
Apr 7 2017
Mar 21 2017
Coming from T12430: Stop cutting of Mail History for new Tasks I think Nuance could be a great Application for our Use Case of managing Requests to our Team.
Feb 13 2017
Hard to say since it fell off the roadmap a year ago, but we do have rough plans to ship Nuance (pre-requisite) in the shorter term.
See Planning for help with timelines and status.
Where does this feature stand? I wasn't able to find any documentation on how to use this, but it also looks that a non-trivial amount of work has been completed towards this goal. Is this something still in the immediate roadmap? Being able to easily integrate GitHub issues into Phabricator (and back) is a big roadblock to adoption for us.
Nov 16 2016
Relevant to my feature request in T11878, if Nuance could also work on incoming Tasks, that would make that feature request redundant as I wouldn't need to use Herald rules instead.
Nov 15 2016
Oct 2 2016
Aug 29 2016
Aug 5 2016
Jul 5 2016
Will this be a one way or two way bridge?
Mar 29 2016
Mar 28 2016
Mar 25 2016
Mar 24 2016
Mar 22 2016
Mar 21 2016
Mar 11 2016
Mar 9 2016
The "Issue Events API" appears to provide the remaining events in a different format with different rules. It does not provide any duplicate events, so, e.g., one API retrieves issues being created and commented on while a different API retrieves labels, milestones, etc., except that both report opens and closes, I think. Anyway, seems mostly workable.
Alright, so here's the first real issue. Here's what I did on GitHub:
Mar 8 2016
Ah, ok. I think that information is out of date with our current plans. Right now we (or maybe just I) see Nuance as a high risk product, one that is difficult to build and support/maintenance costs are completely unknown (and also likely very high). As such we're going to test a single connector (GitHub) and see how it performs / meets needs. Beside that, and maybe a basic email connector at some point, I don't believe we have plans for any other connectors. Nuance I think is a great product for the community to perhaps build and share connectors, though.