Open Source in Finance Forum New York 2024

In the rapidly evolving landscape of ESG data, financial institutions face the dual challenges of data fragmentation and security. This session will explore OS-Climate's innovative use of open source technologies, including Apache Iceberg, Apache Spark and the Unity Catalog, the industry's only universal catalog for data and AI, to enable secure and efficient ESG data sharing across financial institutions. Through this session, participants will gain insights into the strategic benefits of leveraging open source tools for ESG data management, including enhanced data security, governance, and interoperability. In particular we will demonstrate how Unity Catalog Unity's multimodal interface supporting various data formats and engines supports compatibility across diverse data ecosystems to facilitate seamless integration and governance of data assets, allowing financial institutions to not only meet regulatory compliance but also to harness ESG data for strategic advantage.

Financial Services Institutions (FSIs) face unique challenges in measuring and reducing their technology carbon footprint due to the scale and complexity of their IT estates. This session provides a broad overview of the challenges and existing standards and resources (including Green Software Foundation SCI, CNCF Kepler etc) - including challenges in terms of trust and comparability. To address many of these challenges the Technology Carbon Standard (TCS) has been created. TCS is an open source framework inspired by the GHG Protocol, provides a standardized approach for FSIs to classify, analyze, and benchmark their tech-related emissions. In this session, we'll discuss how FSIs can apply the TCS to identify carbon-intensive areas, prioritize reduction efforts, and align with regulatory requirements and voluntary commitments. We'll share case studies demonstrating the practical application of the TCS in the financial services context and explore how open collaboration can accelerate the adoption of sustainable IT practices across the industry.

InnerSource is a movement that is gathering momentum all across various technical industries, including FINTECH. This panel of experts will share their accomplishments, insights, lessons learned, challenges and what the future holds from 3 different perspectives. By hearing from experts at different levels of their experience, participants will gain valuable insights and practical guidance to enhance their own InnerSource practices within their own organizations.

Like Open Source, InnerSource relies on self-motivation and personal interests even if it is happening within a company. How then do you start an InnerSource movement that people want to join of their own volition and get a flywheel spinning? This lightning talk will touch on several ways Capital One is testing and learning to apply innersourcing at scale. These include: Culture challenges and ways to think about them, Tooling as a marketplace of buyers and sellers, Marketing by leveraging the community, Process Consulting, Motivation, and Career Planning

What does it take to provide a seamless experience for governing architecture - from creating and approving architecture to measuring compliance. How does architecture-as-code help in delivering a measurable and objective approach to align architecture with target roadmaps? How to manage tactical shortcuts and time-to-market decisions? Can architecture-as-code help keep architecture evergreen and can it identify and highlight architecture drift? These and other questions are discussed with a case study of Breeze - an architecture-as-code solution built by Morgan Stanley. It provides an extensible framework to support modules for various tasks such as creating and reviewing architecture, identifying adherence to architecture patterns, capturing immutable architecture snapshots, validating releases against approved architecture, etc. It is in the works to be open sourced and captures architecture-as-code in an open-source format, using CALM (https://github.com/finos/architecture-as-code).

Join the Open Source Governance Team at JPMorgan Chase (JPMC) for a panel discussion about how we do open source at the world's largest bank. The panel will discuss a wide range of topics including best contribution practices for banks, what we've found works for keeping contributions compliant, best consumption practices and risks associated with consumption, as well as improving the developer experience while navigating the tightly regulated world of software development in finance. Join our discussion of the A to Zs of all it takes to consume and contribute to open source at the nation's largest bank, and world' largest bank by market cap.

Open-source software has transformed technology, but many projects struggle with sustainability and user satisfaction due to the absence of structured product management. Despite their technical excellence, projects often fail to achieve broad adoption because they do not adequately understand or address users' needs. Product managers can fill this gap by developing user personas, creating journey maps, improving onboarding, evangelizing the project, and managing development processes. This talk highlights how product management can play an critical role in open source, by addressing issues like resource constraints, adoption, governance, and volunteer reliance with strong product management principles. Attendees walk out with a good understanding of how product professionals fill a crucial gap in open source through real life examples and actionable strategies of integrating product management into open source, which will help in fostering community engagement, ensuring sustainability, and driving project success. Embracing product practice can unlock an untapped stream of contributors of product professionals resulting in thriving, user + goal focused open source projects.

Banking and finance companies are realizing they need to integrate the same success formulas as large tech enterprises to further their Open Source journey & remain competitive. With increasing regulatory pressures, demanding customer expectations, evolving technologies & an agile economy, decision-makers are exploring new, forward-thinking ways for continued growth in today’s technological landscape. These strategic technology decisions must be made together with IP management strategy. This presentation will share how companies that have made this tech-focused cultural shift in parallel with making shifts to their IP strategy.

For many years, the landscape of open source licensing seemed stable and predictable. However, the advent of large language models (LLMs) has introduced new licenses and raised numerous questions about the application of existing open source licenses. At Fidelity, our Open Source Program Office (OSPO) and legal team have evolved our processes to navigate these changes and better understand what they require of us. This session will provide a practical case study and an accessible discussion on how OSPOs and legal teams can collaborate effectively in this evolving landscape.

InnerSource is a common topic in many organizations, often discussed in the context of enhancing team collaboration and resource utilization. While numerous teams have embraced this model from a product perspective, we recognized an opportunity to focus on a different set of assets aimed at component reuse. Our approach at Discover goes beyond the traditional product approach. We noticed a gap where valuable reusable components are created, yet they fall outside the scope of any single product team. To address this, we have implemented an internal open-source model, encouraging a community-driven development framework. 
 
Discover has pioneered a Foundation model, inspired by open-source principles, designed to foster collaboration, incubate innovation, and govern the development of reusable components built and shared across organizational boundaries. This model includes our internal requirements for maintaining products and libraries, standardizing delivery through pipelines, and community-driven governance structure that ensure the sustainability and scalability of these assets across the organization.  
 
Our strategy focuses on building a culture that supports InnerSource development within the company, encouraging collaboration beyond individual product teams. By leveraging open-source principles, we aim to create elasticity in resource capacity and cultivate a thriving ecosystem of reusable components that benefit the entire company.

The Common Architecture Language Model (CALM) offers a novel solution, embodying the principles of Architecture as Code (AasC)