Page Comparison

Discussion ensuedPoints raised:

• The contributor is owed a response, it has been in review for a long time
• Question raised as to if anyone had been able to test and run the codeHas any shared their , has anyone shared build issues with Glue42?
• Point made that code may not need to be able to run/build to be acceptedDoes it need a home in FDC3 while there is additional consideration 
• A list of concerns need to be made - Riko, Tim, Neil and Frank will evaluate proposal
• Issues need to be documented on GitHub itself
• Need to be able to make an informed vote.

• https://github.com/FDC3/appd-launcher-poc - being used for the Tick42 contribution PR, may need to be renamed
• https://github.com/FDC3/appd-poc - will be moved under "examples" in https://github.com/FDC3/FDC3 (task for Frank)
• https://github.com/FDC3/open-api-demo - appd-launcher-poc is being used for the Tick42 contribution PR, may need to be renamed

We got some new design love for fdc3.finos.org from the

FINOS team

• FINOS and Riko will continue working on designs and standard branding & put up a PR

https://finosfoundation.atlassian.net/wiki/download/attachments/160104463/Plexus-FDC3%20Alignment%20Proposal.docx?api=v2

• The proposal from OpenFin is not based on a good understanding of what Plexus is, it is not just RPC.
• An "RPC working group", or any separate working group from FDC3 itself, would not be applicable
• Proposal from Rob and Neil is to grandfather the Plexus standards into the existing FDC3 1.0 ones, not spending time to review them (which will take time), but take them as-is.
• FDC3 + Plexus could then become FDC3 2.0
• More information is needed to determine if and how this will work - discuss with Plexus team.
• Plexus does not currently have a "standard" published, which is a blocker for such work to take place.