Page Comparison

...

Action Items from Previous Meeting

•  All: to expand out comparison matrix - SOME UPDATES FROM Former user (Deleted)
•  Former user (Deleted), schedule session to review APIs
•  Former user (Deleted) speak to Peter Monks re potentially undertaking some of the comparison work - COMPLETED 2016-07-07
•  Former user (Deleted): schedule discussion on future plans and how we manage contributions plus major design decisions (like a move to Electron). We should discuss future support arrangements, i.e. we shouldn't all need to make the same security patch.

...

• Minuet open sourcing:
  • Still awaiting signed CCLA from Goldman Sachs
  • Discussion of which code base should be open sourced - currently there are two forks:
    • Goldman Sachs (contains 6 months worth of bug fixes that aren't in the Symphony LLC fork)
    • Symphony LLC (contains some enhancements that aren't in the GS fork)
  • The Foundation's intent is to consolidate 
• Existing requirements & comparison documents:
  • Goldman has some internal documents, but they can't be shared verbatim
    • Would need an NDA
  • Question: will Minuet converge towards Electron or not?  Bigger picture question: what do we think 
  • Goldman perspective:
    • C# based solution has been really good to date, but now is the time to pivot to Electron or OpenFin
    • Lots of complexity in supporting it, not cross-platform
    • Some complex stuff that may be difficult to port, but it's been overtaken
    • In terms of OpenFin vs Electron, OpenFin v6 is an Electron app anyway, and their open source framework may be "good enough" (with those interested able to purchase the more fully featured commercial version)
    • Electron is the market leader - whatever we look at should use Electron at the core
    • But Electron has some pretty serious security holes in it (e.g. sandbox) - OpenFin have had to disable some of this
  • Should this group be making a public statement around Electron being the market leader?
    • Gareth: I think that's Goldman's conclusion - that whatever we choose should be based on Electron
    • In which case, should that statement actually be based on an OpenFin overlay?  It's close to what would have to be done anyway.
  • Had an existing conversation with Colin Everheart Eberhardt from "ScottLogic"
    • Seemed to be pretty strong in Javascript, Electron etc.
    • Colin recently spoke at a conference in London and was pretty impressive
  • Perhaps there's an option to use vanilla, insecure Electron, and then hardening for production use is a choice for the user?
    • There are common security elements that would require need to be addressed by everyone, so perhaps an "Open Core" OpenFin wrapper would be a better choice
  • WilliamS: moving away from a model where we're dependent on one vendor and instead promote an open-source, standard, secure container for FinTech
  • What is the MVP for a framework?
    • Vanilla electron?
    • Electron + security?
    • Electron + language bindings?
    • Capability mechanisms (to support variation between container implementations / editions)?
  • Longer term, Electron will inevitably lose its lustre, and this group could / should be ahead of the next generation of container technology
• OpenFin has just joined the Foundation as a Community Member - should we bring them into this WG?
  • Group: Yes

...

Action items

•  Peter Monks to introduce OpenFin folks to the Desktop Wrapper WG, and request their participation
•  Former user (Deleted) to introduce Colin Everheart Eberhardt (ScottLogic) to Peter Monks (peter@symphony.foundation)
  •  Peter Monks to give Colin an overview of the platform and Foundation, if he's interested
  •  Peter Monks to introduce Colin to Symphony LLC BD/partnerships team
•  WilliamS to coordinate a review of the current WG charter (with assistance from any/all interested WG members), and proposed changes will be presented back to the WG at a future meeting

...