My slides from the NY Fintech Meetup (March 12, 2018) on the Why and How of creating an Open Source Program Office in your FinTech/FinServ company.

1. STARTING AN OPEN SOURCE
PROGRAM OFFICE (WHY AND HOW)
NY OPEN SOURCE FINTECH MEETUP

2. Jim Jagielski
@jimjag
© Jim Jagielski : Released under Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International
STARTING AN OPEN SOURCE OFFICE
AGENDA
▸ Introduction : Who am I?
▸ Open Source Offices
▸ Why you need and want one
▸ What they should do
▸ How to create and maintain one
▸ Gotchas and Lessons Learned (inline)
▸ Q & A

3. Jim Jagielski
@jimjag
© Jim Jagielski : Released under Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International
STARTING AN OPEN SOURCE OFFICE
INTRODUCTION
▸ About Me
▸ Co-founder, Director and Vice-
Chairman of the Apache Software
Foundation
▸ Emeritus Director: OSI, OuterCurve, …
▸ Developer, Advisor

4. Jim Jagielski
@jimjag
© Jim Jagielski : Released under Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International
STARTING AN OPEN SOURCE OFFICE
WHY YOU NEED AND WANT AN OPEN SOURCE OFFICE
▸ Some companies, but mostly FinTech/FinServ don’t think
they do
▸ “We already do open source fine”
▸ “We don’t use/leverage open source enough”
▸ “We aren’t an IT company”

5. Jim Jagielski
@jimjag
© Jim Jagielski : Released under Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International
STARTING AN OPEN SOURCE OFFICE
SO, HOW DO YOU ANSWER THAT
▸ There is always room for improvement (eg: OSAS)
▸ If you don’t think you use/leverage open source enough,
you are fooling yourself
▸ ALL companies today are IT companies: some just don’t
get it.

6. Jim Jagielski
@jimjag
© Jim Jagielski : Released under Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International
STARTING AN OPEN SOURCE OFFICE
SO WHY?
▸ Open Source is a strategic advantage; it requires
coordination and centralization and clear communication
▸ To truly benefit from Open Source, a culture of
transparency and collaboration is required
▸ It is a powerful “signal transmitter” internally and
externally

7. Jim Jagielski
@jimjag
© Jim Jagielski : Released under Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International
STARTING AN OPEN SOURCE OFFICE
WHY: STRATEGY AND COMPLIANCE
▸ Ownership and execution of strategy - Tactical advisors
▸ Determination of strategic Open Source consumption
▸ Process and strategy on Open Source releases
▸ License compliance : process, reviews, oversight
▸ Risk Assessment
▸ IP Governance

8. Jim Jagielski
@jimjag
© Jim Jagielski : Released under Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International
STARTING AN OPEN SOURCE OFFICE
WHY: ENGAGEMENT
▸ External Engagement
▸ Coordinated, organized efforts
▸ Marketing, conferences, …
▸ Open Source communities
▸ Building
▸ Engaging
▸ Cross team cooperation (“What is everyone else doing?”)

9. Jim Jagielski
@jimjag
© Jim Jagielski : Released under Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International
STARTING AN OPEN SOURCE OFFICE
WHY: INTERNAL
▸ Employee Impact
▸ Obtain the right calibre of employee
▸ You retain them as well
▸ Code Reuse / Collaboration : InnerSource
▸ Code Ownership / Better Quality Code
▸ Mentoring

10. Jim Jagielski
@jimjag
© Jim Jagielski : Released under Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International
STARTING AN OPEN SOURCE OFFICE
PREREQUISITES
▸ Upper management buy-in
▸ Air cover
▸ Funding
▸ Realistic expectations and metrics
▸ A true desire/need to make it successful

11. Jim Jagielski
@jimjag
© Jim Jagielski : Released under Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International
STARTING AN OPEN SOURCE OFFICE
HOW
▸ Find the right spot in the org structure
▸ CTO/CIO
▸ Unaligned business unit
▸ Top level of Engineering

12. Jim Jagielski
@jimjag
© Jim Jagielski : Released under Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International
STARTING AN OPEN SOURCE OFFICE
HOW
▸ Plan for the road-blocks
▸ Identify nay-sayers
▸ Anticipate set-backs
▸ Emphasize the journey

13. Jim Jagielski
@jimjag
© Jim Jagielski : Released under Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International
STARTING AN OPEN SOURCE OFFICE
HOW
▸ Find the right leader
▸ This person is the catalyst/crystal
▸ Jack/Jill of-all-trades
▸ Experience
▸ Reputation
▸ Passion
▸ Realize you will likely have to hire this person

14. Jim Jagielski
@jimjag
© Jim Jagielski : Released under Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International
STARTING AN OPEN SOURCE OFFICE
HOW » WHAT
▸ Build the relationships
▸ Engineering
▸ Legal
▸ IP / Security
▸ Marketing
▸ HR

15. Jim Jagielski
@jimjag
© Jim Jagielski : Released under Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International
STARTING AN OPEN SOURCE OFFICE
WHAT
▸ Define
▸ License compliance rules
▸ Contribution process
▸ Open Sourcing process
▸ Governance
▸ Community building

16. Jim Jagielski
@jimjag
© Jim Jagielski : Released under Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International
STARTING AN OPEN SOURCE OFFICE
WHAT
▸ Create
▸ Snapshot of current status
▸ s/w being used
▸ licenses, etc…
▸ Black Duck, WhiteSource, …
▸ Collaboration infrastructure
▸ Content and Expectations

17. Jim Jagielski
@jimjag
© Jim Jagielski : Released under Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International
STARTING AN OPEN SOURCE OFFICE
WHAT
▸ Define
▸ What is Success?
▸ How do we measure it?
▸ What are our Priorities?
▸ rinse and repeat
▸ Incentives

18. Jim Jagielski
@jimjag
© Jim Jagielski : Released under Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International
STARTING AN OPEN SOURCE OFFICE
HELP
▸ Me:
Jim Jagielski
jimjag@gmail.com / 443-324-8390
@jimjag
▸ The TODO Group
▸ The Symphony Software Foundation