Latest thoughts on Open Sourcing technology - why, why not, what works, what doesn't. Where we're taking NetflixOSS next.

1. Ruslan Meshenberg
Andrew Spyker
4/2/2015

2. In a world of only OSS...

3. Why NOT to Open Source?
• Competitive advantage

4. Why NOT to Open Source?
• Embarrassing quality

5. Why NOT to Open Source?
• Too much bureaucracy

6. Why NOT to Open Source?
• Low value to others

7. Why do we Open Source?
• Tech Brand / Hiring

8. Why do we Open Source?
• Collaboration with the community

9. Why do we Open Source?
• Feedback Loop

10. Why do we Open Source?
• Avoid NIH Syndrome

11. What do we Open Source?

12. What do we Open Source?

13. What do we Open Source?

14. What do we Open Source?

15. We’ve been at it for 3 years
• 51 projects later, what have we learned?

16. It works well
• Hiring / Tech Brand
• Collaboration
• Feedback loop

17. It does come at some cost
• Tending to PRs, Issues
• Forums, questions, discussions
• Balance: internal vs external priorities
• Extensibility to support internal systems

18. Making it better
• Workshops: Zero 2 Cloud
• Packaging: Zero 2 Docker
• Deploying at smaller scale

19. Making it better
• Transparency
– Where are we investing
– What’s in maintenance / sunset mode?

20. Making it better
• Metrics – improve the feedback loop

21. Project Snoopdog
• Work in progress!
• Collect overall Netflix
and project by project
“health” metrics (snoops)
• Visualize to owners
and management
the metrics (dogs)
“scraper” cron job
Netflix Employee
Whitepages
snoopdog webapp

22. Overall Stats
W
ork
In
Progress

23. Project Ownership

24. Linking GitHub to Internal

25. Per repository stats

26. Making it better
• Ongoing support
Credit: http://words.steveklabnik.com/how-to-be-
an-open-source-gardener

27. Making it better
• No branches - Use what you Open Source

28. How you can get involved

29. Use NetflixOSS

30. Send us your feedback

31. Contribute!

32. Questions?
@netflixoss
@aspyker
@rusmeshenberg