Symphony Software Foundation - Overview for Public Consumption


Published on

Learn what is the vision, mission and progress of the Symphony Software Foundation ( and discover the benefits for your organization to join the Foundation.

Help us build the most secure and compliant communications ecosystem on the Symphony ( Platform, through Open-ness (as in Open API, Open Architecture, Open Source, Open Standard, Open Communication, Open Governance).

Published in: Software
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Symphony Software Foundation - Overview for Public Consumption

  1. 1. Overview May 2016
  2. 2. Symphony Software Foundation Vision Fostering an open, collaborative, secure, and compliant communication ecosystem on the Symphony Platform
  3. 3. • Promote the adoption of the Symphony Open Source Project as the preferred messaging, communications, workflow, and productivity platform worldwide • Host an arena of innovation focused on addressing industry collaboration challenges with cooperative development and through openness, interoperability, and standardization of the Symphony Open Source Project • Deliver an enterprise-grade platform, in terms of both security and compliance; and produced within a community and under enterprise-friendly governance that fosters open-source contributions Symphony Software Foundation Mission
  4. 4. Symphony Software Foundation Purposes Enforces an enterprise-ready & trusted governance process Defines governance based on well-renowned successful open-source models, while ensuring IP cleanliness (i.e., 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-ramping 01 02 03 04
  5. 5. Symphony Software Foundation Guiding Principles Ingredients for a successful open-source ecosystem Leanness Validation driven, KISS, crawl/walk/run, focus on customer issues 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
  6. 6. Governance Framework 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
  7. 7. Symphony Software Foundation Code Contributions How contributed source code enters the Foundation 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
  8. 8. Symphony Software Foundation New Project Contribution Process Contribution Proposal ESCo Approval IP Enforcement Delivery Infrastructure Anyone can submit a contribution Create “New Contribution” Jira 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; Apache v2 is the outbound license Project is created in Github and Jira committers are given write access Project starts in incubation phase
  9. 9. Symphony Software Foundation IP Cleanliness License: Apache V2 In every release package On every source code file header ICLA/CCLA Individuals contributing code must sign ICLA In most cases, employee’s organization must also sign CCLA Organizations donating existing code sign CCLA Dependency Management Upstream code must be checked for license compatibility (e.g. BlackDuck scan) Acceptance criteria for contributed projects
  10. 10. Symphony Software Foundation Member Benefits Where the Foundation delivers value Global Visibility Presence and visibility in the Foundation global marketing footprint along with other industry leaders Member Programs Open-source readiness programs, industry adoption surveys, dedicated developer on- ramping Working Groups Cooperate with major players to solve common industry problems; and to foster adoption and interoperability Project Influence Impact the Project roadmap and technical choices of the Open Core platform
  11. 11. *List is not comprehensive. Founding Members Community Members Symphony Software Foundation Current Members*
  12. 12. Proprietary and Confidential Become A Member! Gabriele Columbro Executive Director, Symphony Software Foundation @mindthegabz © 2016 Symphony Software Foundation