+971581248768>> SAFE AND ORIGINAL ABORTION PILLS FOR SALE IN DUBAI AND ABUDHA...
June 22nd 2016 - Foundation State of the Union - London Meetup @ Red Deer
1. Proprietary and ConfidentialProprietary and Confidential
State of the Union & Roadmap
2016-06-22, London
Gabriele Columbro
Executive Director, Symphony Software Foundation
@mindthegabz gab@symphony.foundation
12. Proprietary and Confidential
12
Our ingredients for a successful open source ecosystem
Guiding Principles (aka How)
Leanness
Validation driven, KISS,
crawl/walk/run, focus on
customer problem
Openness
Open Communication,
Open Source & Standards,
Open Architecture and APIs
Developer Focus
Developer experience should
be easy & engaging,
developers love it
Inclusivity
Inclusive rather than exclusive,
the power of collaboration is in
the network
Enterprise Grade
IP Cleanliness, Predictable product
lifecycle, compliance and security
Transparency
Decision making process, public
records, clean communication
Cloud readiness
Products integrate easily with
de facto DevOps standards and
Cloud PaaS
Meritocracy
Fosters bottom up, reputation
driven influence on the project
14. Proprietary and Confidential
14
Proprietary and Confidential
What problems can we solve for our personas?
The Symphony Foundation personae
UC Platforms
CRM/ERP
Organizational innovation
Compliance
FinServ
15. 15
Who does what?
Relationship with Symphony
Symphony Software Foundation
Community fostering Symphony open development
industry interoperability and security
Symphony LLC
Symphony commercial service provider
Governs development & release of
Symphony Open Core & open extensions
Caters for Dev/Ops workflow/ergonomics
Enables industry convergence through
Working Groups
Enforces security coding best practices &
provides “security by many eyeballs”
Delivers the Symphony service in SaaS
& hosts 3rd party partner apps
Commercially supports Symphony Open
Core & APIs
Enhances the Symphony Open Core
with value-add proprietary extensions
Main contributor to the Symphony
Software Foundation
16. Proprietary and Confidential
16
Levels of Ecosystem engagement
How will the Foundation enables industry collaboration
Enforces an enterprise ready & trusted governance process
Enable collaborative governance based on Open Source well renowned successful open source models, while ensuring IP cleanliness
(licensing, trademark and copyright) and commercial viability
Fosters adoption & industry convergence
Through Working Groups, and gathering feedback from the community at large, ensures the widest adoption and interoperability for the
Symphony Platform, leveraging (and defining, where not available) industry wide standards
Hosts development and releases open source projects
Symphony Open Core platform, API clients/SDKs, extension and integration patterns, utilities, libraries and Dev tools, horizontal and 3rd
party platform integrations are example of potential projects, always with a key focus on security.
Supports open source readiness of the entire ecosystem
Enable productive 2-way participation to the open source process from Member organizations and Symphony, by sponsoring
open source readiness programs and new contribution/committer on-ramp
01
02
03
04
17. Proprietary and Confidential
17
Community governanceProgress on meritocratic representation
Enforces an enterprise ready & trusted governance process
Enable collaborative governance based on Open Source well renowned successful open source models, while ensuring IP cleanliness
(licensing, trademark and copyright) and commercial viability
01
H1 Key Achievements
✓ First Member Meeting
✓ Elected Member Leads
First Member Meeting!
60 attendees (max capacity!)
22 Organizations
18 Speakers
4 Prospective Members (2 Speaking)
ESCo Member Leads Election
Elected by the Founding + Community Members
Secret and anonymous voting process
5 Candidates (3 Community + 2 Founding)
Elected James Turck and Frank Tarsillo
18. Proprietary and Confidential
18
Proprietary and Confidential
Working Groups
Industry
convergence
Project Committers
Open Source
development
ESCo
Technical Governance &
Overall roadmap
Contributors
Pull requests, patches, docs
Business and Strategy
Board of Directors
19. Proprietary and Confidential
19
Working Groups Momentum
Technology & design focus
Fosters adoption & industry convergence
Through Working Groups, and gathering feedback from the community at large, ensures the widest adoption and interoperability for the
Symphony Platform, leveraging (and defining, where not available) industry wide standards
02
Working Groups massive momentum
✓+100% participation in Working Groups (Desktop Wrapper &
Financial Objects standardization)
✓44 total members
✓2 Working Groups active
2 additional Working Groups proposed
API
Security
Additional Working Groups on Open Source Legal and Awareness
20. Proprietary and Confidential
20
Contributions to dateFollowing the approved Code Contribution Process
Details Name Status / ETA Committers Comments
CONTRIB-4 .NET C# ReST API client Approved
Johan Forsell (FactSet)
Johan Sandersson (FactSet)
Joao Figueiras (FactSet)
Malay Shah (FactSet)
Release 0.1.0 already available on NuGet
CONTRIB-7 Java Agent ReST API client Approved
Frank Tarsillo (Markit)
Amit Joshi (Markit)
CONTRIB-3 MInuet End of Q2
4 * Goldman Sachs
4 * Symphony LLC
- Completing technical work for contribution
- Desktop Wrapper Working Group requires it
CONTRIB-2 HelpBot Approved
Frank Tarsillo (Markit)
3 * Symphony LLC
Merging of parallel Markit / Symphony
implementations required
CONTRIB-5 Hello World Client Extension App Approved Jared Rada (Symphony LLC)
CONTRIB-6 Client Embedding API Examples Approved Jared Rada (Symphony LLC)
Call to Action
If your development teams working on a Symphony integrations, and it’s not a competitive differentiator,
developing it under the Foundation will be more cost-effective
to build & maintain and typically more interoperable
Hosts development and releases open source projects
Symphony Open Core platform, API clients/SDKs, extension and integration patterns, utilities, libraries and Dev tools, horizontal and 3rd
party platform integrations are example of potential projects, always with a key focus on security.
03
21. Proprietary and Confidential
21
Proprietary and Confidential
How contributed Source Code enters the Foundation
Code Contributions
Committer initiated
Repeated contributions applied directly to the source
code from approved committers.
Contributor initiated
New Project Proposal
Pre-existing Project/Feature Contribution
Patches contributed via the issue trackers, pull requests
or mailing lists
An existing third party project / large codebase is
donated and joins the Foundation as a new Project or is
added to an existing Project
A project is proposed to the Foundation, including a list
of initial committers from Member and non Member
organizations
22. Proprietary and Confidential
22
Proprietary and Confidential
New Project Contribution Process
Contribution
proposal
ESCo approval IP Enforcement
Delivery
infrastructure
Anyone
can submit
a Contribution
Create “New
Contribution”
issue, with:
Scope, proposed
initial committers,
existing code assets
ESCo reviews
scope & technical
approach to ensure fit
and proposal
completeness
Appropriate
ICLA/CCLA
are filed. License
is added to existing
code assets
Project is created
in Github (and support
resources).
Committers are given
access
Project starts in
Incubation phase
23. Proprietary and Confidential
23
Proprietary and Confidential
The Foundation Umbrella
Classes of projects developed under the Foundation
FinServ
AnyEnterprise
OSS
Dev
PlatCore
Ext
Vertical
Horizontal
Shepherding and providing a lively
ecosystem to integrate Symphony
with FinServ OSS
Financial Services OSS
Samples, Clients, Dev & Ops
productivity tools
Dev Tools
Horizontal integrations with
3rd party platforms (e.g.
CRM / ECM / etc)
Platform Integrations
Developed in the open, self
standing, open governance
Symphony Platform
Generic features solving any
business communication
problem
Value Add
Common extensions to foster
interoperability and ease of
integration for Financial Services
FinServ Integrations
Add
24. Proprietary and Confidential
24
Structurally enabling Member contributions
Initiatives to enable proper participation
Supports open source readiness of the entire ecosystem
Enable productive 2-way participation to the open source process from Member organizations and Symphony, by sponsoring
open source readiness programs and new contribution/committer on-ramp
04
Engagement Driver Description Where are we?
Seamless Developer
Experience
Easy to use technology. Takes minutes, not hours, days to get started.
Open Source or API access to the Platform.
Open Source SDLC to be completed in Q2.
Open Source Contribution
compliance
Established Open Source / IP contribution policies.
Existence of an Open Source Program Office.
Starting a Working Groups with IT Risk / Compliance /
Member lawyers
Meritocratic path to influence
Positive reinforcement for Contribution of any kind (code, working groups, bugs,
documentation, help in Governance) via higher levels of influence in the Project.
ESCo members appointed by meritocracy. Positive
reinforcement through additional governance, e.g. PMC
council / similar bodies.
Awareness & Visibility
Symphony technology awareness. Foundation awareness as independent brand
targeted to Developers and technical personas.
First Member meeting done. Q2/Q3 to engage
in internal & external meetups. Starting an Awareness
Working Group / Board committee
25. Proprietary and Confidential
25
2016 H1 Overview
An overview of our achievements in 2016
Product
&
Technology
Organization
&
Governance
Community
&
Ecosystem
2 * Working Groups active
44 Working Groups Members
from 17 Organizations
Activated Board Committees
Organizational independency
(Finance, HR, Legal)
Solid pipeline for 2016 hires
Completed v0 of
Community &
Development infrastructure
ESCo active & weekly ratifying
Completed ESCo with 2 New
Member Leads
DB & BAML new Directors
First Foundation
Community Event full, 60
Attendees
60+ Leads, 10+ Qualified
opportunities
70+ Followers on Twitter
4 Committers Approved
(FactSet)
5 Committers in
process
(4 Symphony + 1
Markit)
5 Contributions approved
1 Project released
Contribution Process
ESCo ratified
Project Lifecycle ESCo
ratified
2 New Members ready to join
Hired Marketing Contractor
(Edward Yaeger)
ViabilityContributionAwarenessValue
New Office!
Membership prospectus
Primer Deck
Hired Director, Release Mgmt &
DevOps (Maurizio Pillitu)
Hired VP of Technology,
Peter Monks
27. Proprietary and Confidential
Q2 focus
Complete in-flight contributions
Community & Development infrastructure completion
Plan with Symphony LLC towards Open Sourcing
Start Working Groups on API & Security
Q3 focus
More Meetups & Hack-a-thons to foster extensions development
Project governance & automation
Support Member readiness (Legal & Awareness)
Onboarding new Community Members (OpenFin)
Q4 focus
Enable Symphony core platform ongoing contribution
Onboard additional large FinServ players
Foundation Roadmap
Help us shape our roadmap!
Send feedback on dev@symphony.foundation
28. Proprietary and ConfidentialProprietary and Confidential
Call to action!Get your organizations involved today!
Engage in Contributions early in the Dev cycle
If you are discussing internally about a non core Symphony integration, let us know!
All it takes to start a contribution is an issue at https://symphonyoss.atlassian.net/browse/CONTRIB
Develop directly in the Open!
Foster Open Collaboration
Join Member mailing lists and chats (Any Member of your organizations can join)
Discuss openly with other Members and gauge interest in Working Groups/Contributions
Give us your feedback / input on what you want to see in the Foundation and hurdles to contribution
Help us promote the Foundation!
Host Foundation Sponsored Meetups / Hack-a-thons
Follow us on Twitter @symphonyOSS
Use that swag!
28
29. Proprietary and Confidential
Open Source as collaborative ideationEngage with us since the inception phase
Contributing to Open Source doesn’t require code to start with!
If you are planning to do non-core development internally, propose a Project idea!
(all it takes is opening an issue at https://symphonyoss.atlassian.net/browse/CONTRIB)
Then work directly in the Foundation OSS repository toward your first release!
32. Proprietary and ConfidentialProprietary and Confidential
Thanks!
Gabriele Columbro
Executive Director, Symphony Software Foundation
@mindthegabz gab@symphony.foundation
32
@symphonyOSS
Notes de l'éditeur
I do no shave the logos for everyone, but I wanted to give you an impressive visual of the backigbn for this foundation.
I think it’s pretty exiting from a collaboration standpoint.
HOW
So when I am building a product, or a startup, albeit non profit, I am used to think about who am I doing this for and what problems I am trying to solve.
Dev + Ops
Security by many eyeballs means transparently reporting about security
WHAT
WHAT
BOARD
Corporation Strategy
Long term vision and growth strategy
Control over the bylaws
Fiduciary responsibility
Corporate Governance
Manages policies for BOD representation of the different classes of membership
Manages structure (but not election) of the different bodies (incl. ESCo)
Finance & Viability
Approve yearly budget
Approve membership fees
Legal and IP compliance
WHAT
If these numbers seem extremely conservative
WHAT
I know This is a bit of an eye chart, but I just wanted to show that whatever we have done up until today are in a framework of objectives and clearly defined tracks of the strategy a