Community Blog

Community Blog

Maurizio Pillitu

Find me on:

Recent Posts

Announcing the FINOS Project Sandbox

We're thrilled to announce the launch of the FINOS Project Sandbox, a dedicated environment designed to empower FINOS members and the broader open finance community to accelerate innovation and experimentation. 

The Sandbox provides access to public runtime environments running FINOS projects, enabling developers, technologists, and industry stakeholders to access and play with specific use cases with the click of a few buttons.

Technical Oversight Committee Candidacy

On July 19th 2023, the Technical Oversight Committee (TOC) became an official body of the FINOS charter. This group has a number of responsibilities including, shaping and growing the overall landscape of projects, and providing strategic direction to the board. There are currently 2 vacant seats at the TOC and today we’re announcing the opening for candidacies, starting on Monday 18th of September and closing on Monday 2nd of October.

Open Source in Financial Services: Security and Resilience in Times of Economic Uncertainty

The FINOS 2022 State of Open Source in Financial Services (OSinFSI) Report sheds light on the precarious security challenges in the financial services sector and the crucial role open source software plays in mitigating these risks. Though many business leaders may be unaware of the proper management of open source software, this article aims to provide high-level insights for secure consumption and contribution to open source.

Introducing FINOS Security Scanning

Today we’re very excited to present FINOS Security Scanning - a FINOS initiative for driving security best practices across our hosted projects. This helps FINOS project maintainers quickly enable continuous scanning on their hosted codebase, as an additional tool of security options.

Meet cla-bot, Our IP Compliance Minion

How the Symphony Software Foundation enforces IP Compliance of their hosted code

At the Symphony Software Foundation we care a lot about IP Compliance of the software we host, which is why we:

1. Define a  Contributor License Agreement (CLA, that must be either signed by the individual or his/her employer)
2. Securely s t ore data capturing user affiliations, employers and CLAs in our internal infrastructure
3. Require pro ject leaders to validate whether the contributors (or commit authors, in GitHub lingo) o f each code contribu tion are covered by a CLA signed with the Foundation

WEBINAR RECAP: Project Automation Series: NodeJS


On April 28, we hosted our very first Project Automation Panel, specifically tackling the NodeJS ecosystem.

Enterprise meets open source - Lessons from FOSDEM 2017




Run a Symphony bot in less than three minutes on Docker

Having fun with our community on bot-butler, Coffescript and CI/CD

No More Posts