FINOS Financial Services Open Source Developer study plan
FINOS Financial Services Open Source Developer · Give each week a clear focus.
8 weeks · About 7 hours per week
Open source fundamentals and governance in financial services
Define open source, free software, and source-available licensing in your own words and distinguish them from proprietary distribution
Compare permissive (Apache-2.0, MIT, BSD) and copyleft (GPL, LGPL, AGPL) licenses on obligations, patent grants, and compatibility
Explain how open source governance models (foundation-led, single-vendor, meritocratic, do-ocracy) affect contribution and roadmap control
Identify the compliance risks a regulated firm faces when using copyleft code in client-facing systems
Your checkpoint
A one-page license comparison table covering at least six licenses with columns for patent grant, copyleft scope, notice obligations, and internal-use implications, plus a 200-word summary of governance model trade-offs
Open source fundamentals and governance in financial services & FINOS and the financial services open source ecosystem
Map the FINOS project landscape into categories such as desktop interoperability, data, compliance, and cloud
Explain FINOS membership tiers and how the foundation's IP policy, contribution agreements, and licensing rules differ from a typical GitHub project
Describe how open source is used in trading, risk, and regulatory reporting workflows without naming any single vendor product
Trace one FINOS project's governance documents to identify its maintainer model and decision process
Your checkpoint
A landscape diagram or annotated list of at least eight FINOS projects grouped by domain, each with one sentence on the business problem it addresses and its license
FINOS and the financial services open source ecosystem
Summarize the FINOS mission and how it interacts with regulators and industry consortia
Explain the roles of maintainers, committers, contributors, and the foundation in a FINOS-hosted project
Compare FINOS governance with other financial-adjacent foundations and standards bodies
Draft questions you would ask before adopting a FINOS project in production
Your checkpoint
A 400-word briefing note on FINOS governance written for a non-technical compliance stakeholder, ending with five adoption due-diligence questions
Contributing to open source projects (workflow, licensing, IP compliance)
Walk through the fork, branch, commit, pull request, and review cycle on a real repository
Write a commit message and pull request description that satisfy common contribution guidelines
Identify what a Contributor License Agreement or Developer Certificate of Origin requires and when each applies
Explain how to check that a contribution does not introduce license-incompatible or improperly attributed code
Your checkpoint
A merged or submitted pull request (documentation fix is acceptable) with a link or diff, plus a short reflection on review feedback received
Contributing to open source projects (workflow, licensing, IP compliance) & Consuming and building open source in a regulated financial institution
Perform a license scan and produce an SBOM for a small sample application using open source tooling
Classify dependencies by license obligation and flag any that need legal review before production use
Describe how a firm sets policy for approving, pinning, and upgrading third-party open source components
Explain the security review path for a new dependency, including vulnerability disclosure and CVE handling
Your checkpoint
An SBOM plus a risk register listing at least ten dependencies with license, version, approval status, and remediation action
Consuming and building open source in a regulated financial institution
Outline the controls a regulated institution needs around open source: inventory, approval, patching SLAs, and audit evidence
Explain how export control, data residency, and outsourcing rules can constrain open source adoption
Draft an inner-source contribution policy covering employee contributions to external projects and IP ownership
Describe how to respond to a critical vulnerability in a widely used dependency within a regulated change-management process
Your checkpoint
A two-page open source consumption policy draft with sections on approval workflow, patching timelines, prohibited license categories, and employee contribution rules
DevOps, tooling, and community collaboration practices
Set up a local development environment and run the test suite for an open source project
Configure CI checks such as linting, license headers, and dependency scanning on a sample repository
Explain how code review, issue triage, and community communication norms support healthy collaboration
Practice writing an issue report with reproduction steps and a proposed fix
Your checkpoint
A working repository with at least three automated CI checks passing, plus a filed issue or review comment on an upstream project
Open source fundamentals and governance in financial services & FINOS and the financial services open source ecosystem & Contributing to open source projects (workflow, licensing, IP compliance) & Consuming and building open source in a regulated financial institution & DevOps, tooling, and community collaboration practices
Rehearse explanations of license obligations, FINOS governance, and regulated consumption under time pressure
Review weak areas from earlier weeks and close gaps with targeted reading
Assemble a personal reference sheet covering license types, governance roles, and compliance checkpoints
Complete a full timed practice set and analyze every missed question by domain
Your checkpoint
A scored practice exam attempt with a written error log mapping each miss to a domain and a corrective action, plus a final one-page reference sheet
Milestones
Week 2: Can explain the difference between permissive and copyleft obligations and name at least six FINOS projects with their business purpose, without notes
Week 4: Has submitted a real pull request and can describe the CLA/DCO requirement and the license-compatibility check performed before contributing
Week 6: Can produce an SBOM and defend a written open source consumption policy covering approval, patching, and employee contribution rules
Week 8: Scores at least 80 percent on a timed practice set with no domain below 70 percent, and the error log shows every miss mapped to a corrective action