Curious about FINOS programs and membership benefits? Want to learn more on how you can contribute to the organization that is bringing open source to financial services and fintech? And most importantly, want to know what's in it for you, whether you are large financial institution, a large or small fintech tech or data vendor or an individual? Check out this deck and start contributing today!
11. WHAT DOES FINOS TODAY?
Transparent Governance
Established collaboration methodology
Container for IP clean, secure OSS
Established Policies and legal framework
High productivity developer platform
Collaboration infrastructure and tooling
Consumer and contributor growth
Product management and marketing
Events and Community awareness
14. Join our bi-weekly Working Group calls
at finos.org/osr or email
aaron@finos.org, everyone is welcome!
Ad Hoc
Tracked
Managed
Standardized
Consume Contribute Lead
Strategic
Awareness
Policy
Technology
OSS Readiness
Assessment
Business Value of OSS
Whitepaper
Open Source
Engagement
Strategies
Reference FOSS
policy for FinServ
OSS Executive
Councils
How to set up OSS
Program Office
Surveillance solutions
for open source
engagement
OSS events & basic
trainings
Compliant OSS
engagement
infrastructure
FinServ OSS program
office knowledge
sharing
Continuous IP
compliance / security
validation tools
Compliant
infrastructure for
FINOS projects
Open source license
guidance
Open source project
governance guidance
Programs Community
Self-Promotion tools
Legend
Ongoing
Released
Future
15. JOIN OUR COMMUNITY!1
(H1 2018)
(H2 2018)
License Compliance Guide (target GA early March)
State of OSS in Financial Services, survey & whitepaper w/Aite (H1)
Goldman Sachs shares their GS-OSS process (03/27) - join here!
OSS Readiness Assessment Survey (complete for Members in H1)
OSS Readiness Member specific recommendations (H1)
Implementation of OSS readiness recommendations (H2)
2 Focused Roundtables US / EMEA (H1)
16.
17. fully hosted developer platform
to all our software contributors
communication and software development tools
18. JOIN OUR COMMUNITY!1
Reference architecture and sandbox for organizational OSS-ready surveilled development workflow
Secure standardized person to person, person to machine, machine to machine text and voice communication
Traders desktop UI, interoperability and app stores
Decentralized technologies ecosystem growth on financial services use cases (2019)
Developer access to standardized Open Data Flows (future)
19. cohesive open
industry-wide business problem
solely
everyone
transparent
governance
trust efficiency
growth
Board of Directors
PROGRAM A
PROJECTS
WORKING
GROUPS
PROGRAM A PMC
PROJECTS
WORKING
GROUPS
PROGRAM B
PROGRAM B PMC
20. RetailCapital Markets / Investment Banking
Front Office
Grow liquidity and reduce risk
Mid / Back Office
Gain workflow efficiency
(e.g. IHSM + Symphony MTM Bot)
Technology Organization
Talent attraction / retention, Lower TCO, No Vendor Lock-in
23. INDUSTRY
NETWORK
Engage with industry
leaders
Collaborate with technology and business leaders with extensive expertise
and the vision to drive the future of Open Source in Financial Services.
Head of
Innovation
CIO Global
Markets
Director of Data
Science
Head of
Strategy &
Solutions
Head of
Platform
Director Cloud
Infrastructure
Head of Client
Technology
MEMBER
SUCCESS
Focus on achieving
member goals
Benefit from our member-only initiative dedicated to maximizing
member value from all stages of engagement with FINOS.
OSS strategy
High-value
opportunities
Policy advice
Readiness
assessment
Member OSS
metrics
Training
sessions and
workshops
Bespoke
member
reports
Exert significant influence over the strategic direction of
FINOS programs and future focus areas.
STRATEGIC
DIRECTION
Steer Programs and
focus areas Open Data
Distributed
Ledgers
Common
financial
objects
Signals and
Hashtags
Voice enabled
technology
Bots, bots and
more bots
Application
interop
31. desktop applications
plug-and-play
Overview
▪
▪
Focus Areas Working Groups/Projects
API
App Directory
Context Data
Intents
Use Cases
Participants
Active participants include
Adaptive, Citadel, Factset,
Tick42, Green Key, IHS Markit,
JP Morgan, OpenFin, Refinitiv,
Scott Logic, Wellington
Business Value
▪
▪
Join the Program
fdc3+subscribe@finos.org
wiki.finos.org/fdc3
github.com/fdc3
32. high-productivity end-to-end development
tooling
▪
▪
▪
Working Groups / Projects
Developer Experience
Open Developer Platform
Foundation Dev Toolchain
GitHub Chatops Bot
Participants
GitHub, Red Hat, Morgan
Stanley, FINOS
▪
▪
Join the Program
fdx+subscribe@finos.org
wiki.finos.org/fdx
github.com/finos-fdx
finos.org/odp
33. Drive adoption of new and existing Financial
Objects Standards
▪
▪
▪
▪
Working Groups
Financial Objects
▪
▪
Participants
Citibank, FactSet, Goldman
Sachs, HSBC, JP Morgan,
Portware, Refinitiv, UBS
Join the Program
fo+subscribe@finos.org
wiki.finos.org/fo
github.com/finos-fo
34. ▪
▪
▪
▪
▪
Working Groups / Projects
Technical Steering
Committee
Symphony Integration,
Application Templates,
Layout Service, Notifications
Service, Desktop Services,
Core
Participants
OpenFin, Red Hat, Citadel,
Eikos Partners
▪
▪
▪
Join the Program
hadouken+subscribe@finos.org
wiki.finos.org/had
github.com/hadoukenIO
35. fully enable
corporate open source
engagement
▪
▪
▪
Working Groups / Projects
Open Source Readiness
FINOS Policy for Financial
Services
Participants
Active participants include
FINOS, Deutsche Bank,
GitHub, HSBC, Morgan
Stanley, Redhat, UBS▪
▪
Join the Program
osr+subscribe@finos.org
wiki.finos.org/osr
github.com/finos-osr
36. open standard for
desktop application interoperability
▪
▪
▪
▪
▪
Projects
Plexus interop
Participants
Deutsche Bank, Refinitiv,
Glue42
▪
▪
▪
Join the Program
plexus+subscribe@finos.org
wiki.finos.org/plx
github.com/finos-plexus
37. collaborative
ecosystem
Symphony
messaging and collaboration
▪
▪
Working Groups / Projects
61 projects across API
Clients; Bots, Apps and
Integrations; Utilities;
Containers; Core Platform
Participants
60+ contributors including
individuals from Symphony,
Goldman Sachs, IHS Markit,
FinTech Studios, Glue42,
ScottLogic, Brevan Howard,
FactSet, Blackrock, Daitan▪
▪
Join the Program
symphony+subscribe@finos.org
wiki.finos.org/sym
github.com/symphonyOSS
38. voice
technologies, voice metadata, voice
APIs
▪
▪
▪
▪
▪
▪
▪
▪
Working Groups / Projects
Call Metadata
Standardization
Greenkey SDK
Greenkey Discovery SDK
Greenkey ASR toolkit
Participants
GreenKey, Cloud9
Technologies
▪
▪
▪
▪
Join the Program
voice+subscribe@finos.org
wiki.finos.org/voice
github.com/finos-voice
39. open
collaboration for technology and tools
data across
the full lifecycle
▪
▪
Working Groups / Projects
Kdb+ working group
Kdb+ project
Security Reference Data
working group
Participants
AQR, Citibank, JP Morgan,
Morgan Stanley, Nomura,
UBS
▪
▪
▪
Join the Program
data-tech+subscribe@finos.org
wiki.finos.org/dt
github.com/finos-data-tech
40. Robust and flexible data visualization
tools
open collaboration on technology and
tooling
▪
▪
Working Groups / Projects
TBD WG
Perspective project
Participants
JP Morgan
▪
▪
Join the Program
dav+subscribe@finos.org
wiki.finos.org/dav
41. facilitate
coordination of decentralized applications
▪
▪
Working Groups / Projects
TBD
Participants
Clovyr, IHS Markit
▪
▪ Join the Program
deg+subscribe@finos.org
wiki.finos.org/deg
43. ▪ Technical Infrastructure.
▪ Migration.
▪ Governance.
▪ Legal and Licensing.
▪ Ready Made and Growing Community.
▪ Product Management and Product Marketing Support.
44. Target (Expected) Operations At Risk Intervention/Action Required
Diversity &
Viability
● Program PMC is composed of individuals from 3+ organizations, ideally of 2+
org types, and including 1 bank
● Women represent 50%+ of active participants
● Program leadership is actively seeking new participants and contributions
across different channel, forums, and organizations
● Contributed projects are “seconded” - additional organizations other than
the contributor commit to contributing to the code base
● Program PMC is composed of individuals from just two organizations
● Less than 35% of the program’s active participants are women
● Less than 50% of the program’s active participants are members of
traditionally underrepresented demographic groups
● Program PMC is composed of individuals all from the same organization
● PMC membership itself is in transition, incomplete, or in doubt
● Less than 25% of the program’s active participants are members of
traditionally underrepresented* demographic groups
● One or more project or working groups are missing a lead / chair, and have
been for > 1 month
Roadmap &
Resources
● Programs and projects work to a public roadmap; programs consider the
releases from all component workgroups and projects and how they fit
together
● Programs are actively supported with appropriate resources needed as they
move through project lifecycle, e.g. from incubating to operating
● Program has committed resources from participating firms who
themselves have permission to work on the program as part of their “day
job”
● No requirement exists for developers to create a separate “work” /corporate
github ID
● 2019 Roadmap exists but is not published on the wiki and/or is
incomplete (e.g., does consider work activities of all projects and work
groups)
● Roadmap milestones were missed in the previous quarter
● Projects are staying in incubating status for >6 months
● Participants in the program largely do so “on the side”, fitting time for
FINOS and other OSS work amongst their official job duties on which
their performance review and incentive comp plan depends
● No 2019 roadmap exists
● No roadmap was used in the last quarter of 2018
● Projects are staying in incubating status for >12 months
● Participants in the program do so from home, on home networks using
their personal computer; OSS work is not an official or even officially
permitted part of most participants’ “day jobs”
● No plausible path to a production ready, publicly available, product/release
can be identified amongst the program’s projects and working groups
Hygiene &
Operations
● Meeting agenda developed and shared via the mailing list >24 hours in
advance
● Minutes are kept including all action items, resolutions and attendees and
where/if a policy exists the policy is followed; minutes are distributed within
a week of the meeting
● PMC meets at least once a month
● Questions/Inquiries to the general list are answered intermittently
● Minutes are kept for most but not all meetings and/or minutes are
sometimes incomplete
● PMC meets at least once a quarter
● PMC members, especially PMC leads, have difficulty using collaboration
infrastructure (e.g., Google Groups)
● Questions/Inquiries to the general list often go unanswered
● Communication is ad hoc, infrequently using program mailing lists, and is
largely dependent on 1:1 phone calls and emails (and thus opaque to the
larger community)
● PMC and/or general meetings are not happening
Quality &
Security
● Code is well written, demonstrably proven to be secure, and follows best
practices
● Code in program projects is written consistent with foundation legal and
licensing requirements
● Projects build test cases as they code, integrating test cases into the build
process
● Use of CI/CD tooling is common but not consistent across all code
producing projects
● Code of programs projects’ is uses differing coding standards, idioms,
and design patters
● Testing of program’s projects’ codebases is intermittent and haphazard
● Coding standards are idiosyncratic
● One or more projects introduce a dependency that has a non-compliant
license
● Use of CI/CD tools is not consistent and dependent solely in personal
preferences of individual developers
● License inspection of code is not occurring or haphazard
Growth &
Adoption
● There is QoQ growth in active participants
● The program has projects or working groups that have released code or
other work products that are being used in production, and that usage is
growing
● How the program’s projects’ released code and work products create/will
create business value can be quantified and easily explained in layperson
terms
● Active participation is flat
● The potential/expected business value to be derived from projects is
generally understood through not known for sure, and yet to be
quantified
● Active participants are declining QoQ
● The connection between what projects and working groups are working on
and how that work could create value for financial services users/consumers
of project/WG work products is not understood
* Traditionally underrepresented groups in both financial services and technology; including women and people of color