Just my 2-cents on the issue:
My primary concern would be the stability of the current APIs and
interfaces. We must not break existing "customer" tooling and
workflows. I do not think this will be an issue if we maintain access
to the current URI cluster endpoints. The other issue will be if the
Sending a reply to not end the email on a “yes/no” answer.
I had the not so well thought of idea of creating some sort of shared
runner. Could we create a service or abstraction over each of the
different engines to run the same job? What issues would we run into?
What benefits could come from
Hi all,
Heron is starting the process of graduating from the incubator and an idea
was brought up by one of our mentors.
Does anyone see synergies with the joining the two communities and/or
projects?
- Josh
--
Sent from A Mobile Device
