The document provides an overview of governance for OpenMAMA, an open source integration layer for capital markets. It notes existing pain points such as incumbent lock-in, increasing complexity, and limited resources. OpenMAMA aims to address these issues by providing a flexible, vendor-neutral platform that reduces costs and complexity while allowing collaboration. The governance structure includes a steering committee for leadership and a technical committee for implementation. Participation is encouraged to help guide the project.

1. GOVERNANCE OVERVIEW
Version 2.5

2. 1. The
primary
incumbents have you locked-­into their
technology.
2. Increasing
data
sources
and
disparate
technologies
are
driving up
complexity.
3. New and increasing regulation is
forcing
change.
4. Massive cost cutting is required,
unlike
ever
before.
5. Resourcing constraints are limiting your ability to
innovate
and
address
technology
challenges.
The Problem

3. OpenMAMA as an Open Platform
Open Platform
enabling the
Capital
Markets
Open
source
Integration
layerExisting
pain
points
§ Increasing
Regulation
§ Increasing
TCO
§ Limited
resourcing
§ Incumbent
Lock-­‐in
§ Increasing
Complexity
The Result
§ A flexible platform
§ Reduced TCO and time to market
§ Pool resources across community
§ Remove Incumbent Lock-In
§ Reduced Complexity
Compete
on
Innovation
Collaborate
on
the
Non-­‐Differentiating
Technology
Multi
Vendor
Open
Platform
OpenMAMA
Vendor
Neutrality
Community
Collaboration
Innovation

4. What is MAMA and OpenMAMA?
§ The Open Middleware Agnostic Messaging API
§ Fully open source and licensed under the LGPL 2.1
§ Supports a variety of MOM platforms
§ Provides a High performance consistent abstraction layer
§ Governed by a group of industry stakeholders
§ Over 10 years production usage inherited from MAMA
§ Hosted through the Linux Foundation at www.openmama.org

5. Open source including
OpenMAMA
Open Source
3rd Party
Legend
3rd
Party commercial
Products
OpenMAMA (C)
Redline
Inrush
Qpid / AMQP
OpenMAMDA
(C++ / Java / .NET)
OpenMAMA
(C++/Java/.NET)
Entitlements
V5 Wirecache
Middleware Bridge
Wombatmsg
Message Bridge
Exegy API
Avis
UPA Bridge
to TREP
Bridge to
Bloomberg API
Informatica
LBM
SR Labs
Data Fabric
Data Feed Data Feed
Feed
Handler
Algo Algo Cache Monitoring …..
OpenMAMA Architecture
Solace Appliance
RAI
Technologies
ActivAPI
QpodMessage …

6. OpenMAMA Community Goals
Our Mission Statement is “OpenMAMA to become the industry-­standard API for
all middleware systems and market data distribution platforms”
Our target market is “Market Data Distribution”.
Our core objectives are:
1. Breaking down monopolies and empowering users to chose solutions
without the risk of being locked into a specific vendor.
2. Take the friction and cost out of maintaining a market data distribution
platform while improving time to market.
3. Create an open market based on quality, functionality and innovation.
4. Encourage innovation and widen the portfolio of middlewares and
applications supported on OpenMAMA.
5. Ensure OpenMAMA reaches its full potential and remains a best of bread
solution.

7. Community Structure / Governance
§ Strategy and leadership
§ Voting members
§ Start new working groups
§ Project level decisions
§ Advocacy / Funding
§ Technical Direction
§ Design & implementation
§ QA & validation
§ Contributions
§ Community relationships
Linux Foundation
Project
Coordinator
Steering Committee
Technical Committee
Maintainer
Working
Group 3
Working
Group 1
Working
Group 2
Open Source
Community
Advisory
Group
§ User Representation
§ Non-­Voting members
§ Project advocacy

8. Why Participate
1. Reduce
Incumbent
lock-­‐in
and
ensure
the
integrity
of
the
project.
2. Enable
integration with
a
range
of
otherwise
incompatible
technologies.
3. Further
reduce
costs
by
pooling
your
resources
on
the
non-­‐
differentiating
technology.
4. Drive
the
collaborative
platform
strategy
to
the benefit
of
your
business.
5. Guide
how
participating
vendors
they
leverage
the
platform for
their
commercial
interest.

9. Expected Commitment
Steering Committee / Advisory Group Expected Commitments SC AG
Linux Foundation Membership dues (dependant on company size) ✔
Steering Committee dues (waived for financial institutions) ✔
Sign Steering Committee Agreement ✔
Commit resource to technical committee ✔
Publicly advocate OpenMAMA ✔ ✔
Company Logo on OpenMAMA website ✔ ✔
Commit resource to working groups (on items of interest) ✔ ✔
Attend steering committee and appropriate working group meetings ✔ ✔
Contribute to OpenMAMA ✔ ✔
Encourage other financial institutions and vendors to support OpenMAMA ✔ ✔
Support OpenMAMA in products and services (vendors only) ✔ ✔
Note:
• Any new Steering or Advisory Group members must be approved by the existing Steering Committee.
• All OpenMAMA Steering Committee dues will be waived until further notice.

10. Benefits of Membership
Steering Committee & Advisory Group Benefits SC AG
Access to Steering Committee meetings ✔
Access to Advisory Group meetings and OpenMAMA events * ✔ ✔
Voting member (every member regarded as a peer, equal control of the project) ✔
Feed your business needs directly into the OpenMAMA roadmap ✔ ✔
Approve project roadmap prepared by Technical Committee ✔
Controls use of OpenMAMA mark and logo (can also post on company collateral) ✔
Sets working groups and project initiatives ✔
Approves and decides how project funds are used ✔
Influence how other vendors are leveraging / supporting OpenMAMA ✔ ✔
Unique insight into customer requirements /emerging industry trends (vendor) ✔ ✔
Collaborate / pool resources on non-differentiating technology ✔ ✔
Open collaboration with your customers, industry peers and competitors ✔ ✔
* Advisory Group members will typically be invited to OpenMAMArelated events, however will not be invited to committee off-­
sites / portions of off-­sites where the agenda includes project level / funding decisions.

11. Role of Steering Committee
q Steering Committee:
§ Leadership + Strategy + Funding
§ Project level decisions
§ Sets the direction, tone, and vision of the project
§ Approves project roadmap prepared by Technical Committee
§ Invites other companies to the Steering Committee
§ Approve rights to use OpenMAMA mark and logo
§ Recommends starting new interest groups, project initiatives
q Steering Committee Coordinator:
§ Elected by Steering Committee for a period of 1 year
§ This is not a ceremonial role
§ The Coordinator is expected to devote adequate time and energy to make the project successful.
• Driving Steering Committee activities, agenda, calls, action items, planning, follow-­ups, etc.
• Interfacing between Steering and Technical Committee and interest groups
• Etc.
q Advisory Group: The purpose of the Advisory Group is to ensure organizations who add value to the
committee but cannot meet the criteria for full membership are not excluded.

12. Role of the Technical Committee
q Companies represented in the Steering Committee contribute
resources to Technical Committee
q Participants of the Technical Committee are responsible for:
§ Software architecture and implementation activities
§ Software QA and validation
§ Developing compliance test suites
§ Removing any technical inhibitors facing adoption of OpenMAMA
§ Reviewing submitted requests for new features, capabilities, prioritizing
them, aligning them with decided implementation roadmap
§ Defining compliance profile and implementation verification test suites
for 3rd party OpenMAMA-­based stacks
§ Release plan and roadmap
§ Working with other open source projects on which OpenMAMA
supported applications and solutions depend

13. Role of the Maintainer
q What is a software maintainer?
§ A software maintainer is the software developer who acts as a gate keeper to the
OpenMAMA source code repository.
§ The software maintainer ensures that submitted source code meets set criteria
(functional, quality, security, etc) and decides based on such factors to accept source
code inclusion into the project source code tree, which will be built into a binary
package for distribution.
q Responsibilities of the Maintainer:
§ Scheduling work efforts based on prioritization of the Steering Committee and the
needs of the project
§ Managing resources and their work items
§ Setting the criteria for accepted / rejected code
§ Reviewing submitted code / accept and reject based on pre-­defined rules
§ Tracking dependency issues
§ Notifying developers of source code changes that may affect their packages
§ Managing source code security issues
§ Working closely with technical team developing the source code
§ Working closely with QA team testing the source code
§ Dealing with reported bugs in a timely manner
§ Preparing binaries – packages of the source code

14. Role of the Linux Foundation
q About the Linux Foundation:
§ A technology non-­profit organization with hundreds of member companies
§ A vendor neutral environment for companies to collaborate on various
upstream open source projects that act as enablers for differentiation and
other technologies
§ Multiple experiences and success stories enabling industry leaders to
shape markets with open source in areas of: Enterprise, HPC, Carrier
Grade Telecommunication, Consumer Electronics and Mobile Computing.
q What do the Linux Foundation provide?
§ Neutral home for collaboration
§ Credible hosting partner
§ Awareness and reach
§ Neutral reputation infrastructure
§ Technical infrastructure
§ Marketing platform
§ Legal infrastructure
§ Continuous project guidance
§ Guidance on governance
§ Guidance on FOSS licensing

15. OpenMAMA™ is a trademark of the Linux Foundation.
OpenMAMA™ may be used in accordance with the Linux Foundation Trademark Policy and will
approval by the OpenMAMASteering Committee.