--- title: Coding in the Open - Symphony Integrations description: Daitan Group provides insight into the development process they've created on top of the Foundation's Open Developer Platform. image: https://www.finos.org/hubfs/pexels-photo-574070.jpeg --- [![FINOS](https://www.finos.org/hs-fs/hubfs/sofin%20assets/SOFIN%20LOGOS/finos-logo.png?width=543&height=126&name=finos-logo.png "FINOS")](https://finos.org) - [Projects](https://www.finos.org/projects) - [Artificial Intelligence (AI)](https://ai.finos.org/) - [Common Domain Model (CDM)](https://www.finos.org/common-domain-model) - [FDC3](https://www.finos.org/fdc3) - [Fluxnova](https://fluxnova.finos.org) - [FINOS Common Cloud Controls](https://www.finos.org/common-cloud-controls-project) - [High Performance Computing (HPC)](https://hpc.finos.org) - [OSERA](https://osera.finos.org/) - [Open Source Readiness Initiative](https://www.finos.org/open-source-readiness) - [OS-Climate](https://www.finos.org/os-climate) - [Try our Projects](https://www.finos.org/project-sandbox) - [All Projects Landscape](https://landscape.finos.org/) - [Community](https://www.finos.org/engage-with-our-community) - [FINOS Community Calendar](https://www.finos.org/calendar) - [Community Quickstart](https://www.finos.org/get-involved) - [FINOS Community Site](https://community.finos.org/) - [Contribute](https://community.finos.org/docs/governance/Software-Projects/contribution) - [Unable to Contribute?](https://www.finos.org/open-source-readiness) - [Join our Slack channel](https://finos-lf.slack.com/messages/finos-community/) - [Recognize a contributor](https://github.com/finos/community/issues/new?assignees=mcleo-d&labels=community-recognition&template=Community-Recognition.md&title=FINOS+Community+Recognition) - [Ambassador Program](https://www.finos.org/ambassador-program) - [Membership](https://www.finos.org/membership-benefits) - [Members](https://www.finos.org/members) - [Inquire](https://www.finos.org/membership-benefits#become-a-member) - [Join](https://joinnow.platform.linuxfoundation.org/?project=finos) - [Member ROI Summary & Calculator](https://www.finos.org/roi-report-calculator) - [Dependency Consumption Analysis](https://www.finos.org/dependency-consumption-analysis) - Resources - [2025 Mission & Vision](https://www.finos.org/2024-in-review-2025-vision) - [Research & Case Studies](https://www.finos.org/research-case-studies) - [Training](https://training.linuxfoundation.org/finos/) - [Open Source Maturity Model](https://osr.finos.org/docs/bok/OSMM/Introduction) - [Contributions Live Dashboard](https://metrics.finos.org) - [Our Github Organization](https://github.com/finos/) - [Our Developer Toolchain](https://odp.finos.org/) - [FINOS Store](https://store-finos.myshopify.com/) - News & Events - [This Week At FINOS](https://www.finos.org/this-week-at-finos) - [Community Blog](https://www.finos.org/blog) - [Newsletter](https://www.finos.org/newsletter) - [Podcast: Open Source in Finance](https://www.finos.org/open-source-in-finance-podcast) - [Press Releases](https://www.finos.org/press) - [FINOS Events](https://www.finos.org/hosted-events) - [Community Events](https://www.finos.org/featured-events) - [Community Spotlight](https://www.finos.org/community-spotlight) - [Stay Informed](https://www.finos.org/sign-up) - [About](https://www.finos.org/about-us) - [Stay Informed](https://www.finos.org/sign-up) - [FAQs](https://www.finos.org/faq) - [Contact Us](https://www.finos.org/contact-us) - [Governing Board](https://www.finos.org/governing-board) - [Technical Oversight Committee](https://www.finos.org/technical-oversight-committee) - [Team](https://www.finos.org/team) - [Governance](https://www.finos.org/governance) - [Code of Conduct](https://www.finos.org/code-of-conduct) - [OSFF + Videos](https://events.linuxfoundation.org/open-source-finance-forum) - [OSFF 2026](https://events.linuxfoundation.org/open-source-finance-forum/) - [OSFF Toronto 2026 Videos](https://www.finos.org/osff-toronto-2026-videos) - [OSFF New York 2025 Videos](https://www.finos.org/osff-nyc-2025-videos) - [OSFF London 2026 Videos](https://www.finos.org/osff-london-2026-videos) - [apidays Paris 2025 Videos](https://www.finos.org/apidays) - [Projects](https://www.finos.org/projects) - [Artificial Intelligence (AI)](https://ai.finos.org/) - [Common Domain Model (CDM)](https://www.finos.org/common-domain-model) - [FDC3](https://www.finos.org/fdc3) - [Fluxnova](https://fluxnova.finos.org) - [FINOS Common Cloud Controls](https://www.finos.org/common-cloud-controls-project) - [High Performance Computing (HPC)](https://hpc.finos.org) - [OSERA](https://osera.finos.org/) - [Open Source Readiness Initiative](https://www.finos.org/open-source-readiness) - [OS-Climate](https://www.finos.org/os-climate) - [Try our Projects](https://www.finos.org/project-sandbox) - [All Projects Landscape](https://landscape.finos.org/) - [Community](https://www.finos.org/engage-with-our-community) - [FINOS Community Calendar](https://www.finos.org/calendar) - [Community Quickstart](https://www.finos.org/get-involved) - [FINOS Community Site](https://community.finos.org/) - [Contribute](https://community.finos.org/docs/governance/Software-Projects/contribution) - [Unable to Contribute?](https://www.finos.org/open-source-readiness) - [Join our Slack channel](https://finos-lf.slack.com/messages/finos-community/) - [Recognize a contributor](https://github.com/finos/community/issues/new?assignees=mcleo-d&labels=community-recognition&template=Community-Recognition.md&title=FINOS+Community+Recognition) - [Ambassador Program](https://www.finos.org/ambassador-program) - [Membership](https://www.finos.org/membership-benefits) - [Members](https://www.finos.org/members) - [Inquire](https://www.finos.org/membership-benefits#become-a-member) - [Join](https://joinnow.platform.linuxfoundation.org/?project=finos) - [Member ROI Summary & Calculator](https://www.finos.org/roi-report-calculator) - [Dependency Consumption Analysis](https://www.finos.org/dependency-consumption-analysis) - Resources - [2025 Mission & Vision](https://www.finos.org/2024-in-review-2025-vision) - [Research & Case Studies](https://www.finos.org/research-case-studies) - [Training](https://training.linuxfoundation.org/finos/) - [Open Source Maturity Model](https://osr.finos.org/docs/bok/OSMM/Introduction) - [Contributions Live Dashboard](https://metrics.finos.org) - [Our Github Organization](https://github.com/finos/) - [Our Developer Toolchain](https://odp.finos.org/) - [FINOS Store](https://store-finos.myshopify.com/) - News & Events - [This Week At FINOS](https://www.finos.org/this-week-at-finos) - [Community Blog](https://www.finos.org/blog) - [Newsletter](https://www.finos.org/newsletter) - [Podcast: Open Source in Finance](https://www.finos.org/open-source-in-finance-podcast) - [Press Releases](https://www.finos.org/press) - [FINOS Events](https://www.finos.org/hosted-events) - [Community Events](https://www.finos.org/featured-events) - [Community Spotlight](https://www.finos.org/community-spotlight) - [Stay Informed](https://www.finos.org/sign-up) - [About](https://www.finos.org/about-us) - [Stay Informed](https://www.finos.org/sign-up) - [FAQs](https://www.finos.org/faq) - [Contact Us](https://www.finos.org/contact-us) - [Governing Board](https://www.finos.org/governing-board) - [Technical Oversight Committee](https://www.finos.org/technical-oversight-committee) - [Team](https://www.finos.org/team) - [Governance](https://www.finos.org/governance) - [Code of Conduct](https://www.finos.org/code-of-conduct) - [OSFF + Videos](https://events.linuxfoundation.org/open-source-finance-forum) - [OSFF 2026](https://events.linuxfoundation.org/open-source-finance-forum/) - [OSFF Toronto 2026 Videos](https://www.finos.org/osff-toronto-2026-videos) - [OSFF New York 2025 Videos](https://www.finos.org/osff-nyc-2025-videos) - [OSFF London 2026 Videos](https://www.finos.org/osff-london-2026-videos) - [apidays Paris 2025 Videos](https://www.finos.org/apidays) ![Community Blog](https://www.finos.org/hubfs/10.04.19.FINOS_WebsiteBanners_3.png) # Community Blog # Coding in the Open - Symphony Integrations December 18, 2017 [Daitan Group](https://www.finos.org/blog/author/daitan-group) ### Notes from Daitan Group on Symphony Integrations Development [![pexels-photo-574070.jpeg](https://www.finos.org/hs-fs/hubfs/pexels-photo-574070.jpeg?width=640&name=pexels-photo-574070.jpeg) Daitan Group](http://www.daitangroup.com/) provides software product development services to leading global technology companies including Symphony and contributed significantly to the [Symphony Integrations](https://symphonyoss.github.io/Integrations-Docs/) project, which is one of the [top 3 most active projects hosted by the Symphony Software Foundation](http://symphonyoss.github.io/). In the spirit of sharing experiences with the community around open source best practices, we want to describe the development process that the team has crafted on top of the [Open Developer Platform](http://symphony.foundation/odp) (ODP) delivered by the Foundation, walking through each step from the developer’s perspective. ### Source Code Management (SCM) The first step is to get (or update) the **project source code from** **GitHub**; the [configuration of the SCM](https://symphonyoss.atlassian.net/wiki/spaces/FM/pages/158924813/Code+Hosting) is crucial for the correct development of the project, as it delivers: 1. **A place to store all of the project’s code assets**, organize it in different GitHub repositories and have a landing documentation page on each of them (README.md) 2. **History and conflict management** across all team member activity. 3. The way to **configure and enforce the branching model** (We use feature-driven development, see [Github flow](https://guides.github.com/introduction/flow/) to know more about what the best fits your team). 4. **IP compliance checking**, using the [Foundation’s cla-bot](http://blog.symphony.foundation/meet-cla-bot-our-ip-compliance-minion). 5. **Full Admin access** (to preserve project self-governance) to project leads, so that they can configure anything in GitHub without the need of opening issues (and wait) for Foundation Staff. 6. [Documentation generation](https://symphonyoss.atlassian.net/wiki/spaces/FM/pages/80945878/Documentation), using Github Pages in combination with static website engines; you can check the [generated documentation](https://symphonyoss.github.io/Integrations-Docs/). ### Building the Code The first activity on top of a checked-out codebase is to run the **build process**, which must be ensured to **work in any circumstance and environment** (in the functional boundaries of the project). This is why it is crucial to define and maintain a working build process. For the Symphony Integrations project we used Java technologies and adopted [Apache Maven](http://maven.apache.org/) as our build tool, which allowed us to reuse the [Foundation’s Maven Parent Pom](https://github.com/finos/ssf-parent-pom). This gave us tons of plugin configurations for the following build features: 1. **Orchestrates Java and JavaScript builds** to allow deploying/releasing frontend and backend as a single component 2. Delivers **build-time integrations with** [code validation](https://symphonyoss.atlassian.net/wiki/spaces/FM/pages/73564187/Code+Validation) **tools** 3. Enforces **binary artifact versioning** (including nightly builds, aka *snapshot* artifacts) 4. **Configures binary artifact deployment** on [Maven Central](http://search.maven.org/#search%7Cga%7C1%7Csymphonyoss) (and [Sonatype OSS](https://oss.sonatype.org/#nexus-search;quick~symphonyoss) for snapshots) 5. Provides **easy-to-use release capabilities** Normally, the build process runs on developers workstations, which can be misconfigured or have configuration issues which leads to a build failure. To prevent this from happening, the Foundation provides documentation and infrastructure to easily set up a [continuous integration](https://symphonyoss.atlassian.net/wiki/spaces/FM/pages/73564181/Continuous+Integration) build process. We chose to use Travis CI, which delivers: 1. **Containerized and isolated builds** 2. **Advanced build configurations** (ie invoking mvn and npm on the same build) 3. **Authentication and authorization** inherited by GitHub (no need to sign up) ### Validating the Code Given the context of the project - integration for THE messaging platform for the financial world, we must **ensure that the quality, security and legal compliance** of the software is **continuously scanned and validated**. For this purpose, the Foundation [ODP provides several code validation tools](https://symphonyoss.atlassian.net/wiki/spaces/FM/pages/73564187/Code+Validation), depending on the language and use case you’re trying to solve. The main tool used for security and legal validation is [WhiteSource](https://symphonyoss.atlassian.net/wiki/spaces/FM/pages/150601733/WhiteSource), as it supports the majority of the use cases we are interested in and delivers integration with all the languages we use (Java and NodeJS), specifically: 1. Check libraries for **problematic/undefined licenses.** 2. Generates **legal reports.** 3. Check **libraries for** **security vulnerabilities.** 4. Check **libraries for bugs.** 5. Check **libraries for outdated versions.** 6. Check **libraries for release activity.** We enforce the security aspect by adopting [CoverityScan](https://symphonyoss.atlassian.net/wiki/spaces/FM/pages/152568180/CoverityScan), which adds static code analysis capabilities at build time: 1. Scans **code for security vulnerabilities.** 2. Scans **code for bad practices.** 3. Scans **code for bugs.** Last but not least, we enforce software quality - in terms of code activity and test coverage - by using [CodeCov](https://codecov.io/). ### Running the Code The **ultimate step** is to continuously deploy the code on a running service, which is normally referred to as [continuous delivery](https://symphonyoss.atlassian.net/wiki/spaces/FM/pages/73564183/Continuous+Delivery). The Foundation provides a containerized infrastructure that can be easily integrated with Travis CI to ensure that every successful build also triggers the deployment of the binaries. ### The Value of Open Source Foundations Working in open source environments has multiple benefits. For example, consider the differences between developing in a proprietary source environment versus going open source. In a proprietary environment we often find that systems code becomes more tightly coupled codebases and controlled by a few individuals leading to interdependencies that can slow release cycles, impacting efficiency and (potentially) a business’ competitiveness. In open source environments there is a higher adoption of best practices and community collaboration, leading to more modular designs which enables greater agility and independence to the development team. Second, the symbiotic structure provided by the the Symphony Software Foundation ensures neutral oversight for a Project Lifecycle and guidance toward key milestones that enforce quality assurance, validation and governance of all contributions. Within this collaborative framework, each contributor maintains full control over individual code assets while adding incremental value to the total project and community stakeholders. ### Conclusions It’s been a great experience to work with the Foundation and their ODP infrastructure, as it has **optimized our workflow efficiency** by adopting *cutting-edge* yet *industry-approved* services, tools and technologies and **offloaded several tedious infrastructure setup tasks** accelerated our performance, especially during the initial stages of the project. We **ensured quality by adopting automated testing from the very first day**, with multiple tools for code validation and security, Finally, Daitan Group has always **advocated open source and community-driven initiatives**, so we plan to continue our efforts with the Foundation, hoping we provide valuable contributions for others. Checkout the [Symphony Integrations documentation](https://symphonyoss.github.io/Integrations-Docs/) and drop a comment below if you have any questions. [![Learn about the Foundation's Open Developer Platform.](https://no-cache.hubspot.com/cta/default/2419532/0c1661e9-377b-4f72-84de-596e71d7eba0.png)](https://cta-redirect.hubspot.com/cta/redirect/2419532/0c1661e9-377b-4f72-84de-596e71d7eba0)  ### Share this: - [Tweet](https://twitter.com/share) [← The Case for an Open Source Ecosystem](https://www.finos.org/blog/the-case-for-an-open-source-ecosystem) [Building the Backbone of Open Source Development for Financial Services →](https://www.finos.org/blog/building-the-backbone-of-open-source-development-for-finserv) [![FINOS Logo](https://www.finos.org/hs-fs/hubfs/sofin%20assets/SOFIN%20LOGOS/FINOS_Icon_Wordmark_White.png?width=689&height=971&name=FINOS_Icon_Wordmark_White.png "FINOS Logo")](https://www.finos.org/) [![Twitter logo](https://finos.org/hubfs/2419532/FINOS/website/logos/social-logos/twitter-blue-social-panel.png)](https://twitter.com/finosfoundation) [![GitHub logo](https://finos.org/hubfs/2419532/FINOS/website/logos/social-logos/github-black-social-panel.png)](https://finos.github.io) [![LinkedIn logo](https://finos.org/hubfs/2419532/FINOS/website/logos/social-logos/linkedin-blue-social-panel.png)](https://www.linkedin.com/company/finosfoundation) [![SlideShare logo](https://finos.org/hubfs/2419532/FINOS/website/logos/social-logos/Homepage%20Social%20Panel/slideshare-logo.png)](https://www.slideshare.net/finosfoundation) [![YouTube logo](https://finos.org/hubfs/2419532/FINOS/website/logos/social-logos/Homepage%20Social%20Panel/youtube_logo-1.png)](https://www.youtube.com/channel/UCfJAdRALzJ7J7snubrb_Y-Q) [Contact Us](https://www.finos.org/contact-us) [info@finos.org](mailto:info@finos.org) +1 (650) 665-9773 [Privacy | ](https://www.finos.org/privacy-policy)[Terms of Service |](https://www.finos.org/terms-of-service)[Community Code of Conduct |](https://www.finos.org/code-of-conduct)[Email Preferences](https://www.finos.org/hs/manage-preferences/unsubscribe-simple) ![](https://px.ads.linkedin.com/collect/?pid=537250&fmt=gif)