Symphony LLC / Desktop Wrapper WG Flow Proposal
A primary goal for the WG is to enable the Symphony application to run in any Container that meets an agreed upon interface. Ultimately, the Symphony LLC development team owns the keys to this - since they are developing the application.
To that end, it is critical that the Symphony dev group on the application takes the first step in this process and provides the desktop wrapper WG with a specification covering the current state of the API between application and container.
The ongoing responsibility for the LLC would be:
Specification for the API between the application and the container
Guidance on plans for ongoing API changes
Ensuring that this spec is followed in all relevant Symphony projects (web app and container)
Responsibilities of the WG would be:
Advice on API scope and design
Development of container reference implementations
Ongoing maintenance of the spec for the API and any supporting materials
Comments
@Peter Monks @James Turck : this ask is different from the reverse engineering exercise last year. This is the dev team actually building the application stating (and fully describing) the APIs they use - not us trying to infer what might be used.
@Former user (Deleted) am I right in thinking this approach was tried last year? I see that the instructions for reverse engineering the JS API calls that the (then) Symphony app makes were provided in the 2016-08-10 Meeting Agenda / Notes, and I seem to recall that subsequent work resulted in the Symphony Wrapper Current API Anaylsis page.