Done
Details
Assignee
Maurizio PillituMaurizio PillituReporter
Svyatoslav KryukovSvyatoslav KryukovPriority
HighestLabels
Details
Details
Assignee
Maurizio Pillitu
Maurizio PillituReporter
Svyatoslav Kryukov
Svyatoslav KryukovPriority
Labels
Created August 23, 2017 at 3:05 PM
Updated October 5, 2017 at 2:55 AM
Resolved October 5, 2017 at 2:55 AM
Background
Establish a well documented, open framework for interBank interoperability, connecting buy and sell side desktop applications via Symphony Chat and facilitating a richer, federated Symphony app store.
Proposal
Open source Deutsche Bank's established Plexus interop framework underpinning its Autobahn platform - a "code first" approach.
Rationale
Enhancing Symphony's interop capabilities enables organisations to increase use of the platform as a workflow tool in conjunction with existing IM and collaboration functionality.
Current State
The DB interop technology (Plexus interior) is mature and underpins all Autobahn applications.
It separates interoperability from the container. It went through a refactoring aimed at making codebase ready for open sourcing (e.g. removing incompatible licenses etc). It's being re-integrated into Autobahn mainline aiming to avoid forking from the very beginning.
Near Term Goals
Make initial Open Source contribution (establishing contribution process etc).
Aiming to provide InterApp interop within single POD boundaries as a first step.
Targeting Symphony chat in Electron only (skip Minuet).
Future Goals
Inter-organisational workflows requiring federated authentication.
Issues / Risks
1. DB recently established Open Source Policy however is still working on the mechanics (tooling by most) for the large open source contributions such as approval workflow, dev ergonomics etc. This is essential for ongoing support of our contribution and whilst can not stop contribution (as Policy is the key and most challenging part of it and it's already done), it might affect timelines for contribution (currently aimed for end of Sep/beginning Oct).
2. Federated trust / authentication is a key foundation for building inter-organisational workflows. Even though technical solution seem to be relatively clear, wide acceptance across organisations are seen to present a challenge, this might significantly slow down build out of a range of workflows where it is required.
Code and Core Developers
Current SCM:
TBD
Code Transfer Approach:
TBD
Desired GIT Repository Name(s)
TBD
Owners:
TBD
Committers:
TBD
Do you require access to the Open Developer Platform (for unit testing and continuous integration & delivery)?
TBD