Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Ruslan Meshenberg
Andrew Spyker
4/2/2015
In a world of only OSS...
Why NOT to Open Source?
• Competitive advantage
Why NOT to Open Source?
• Embarrassing quality
Why NOT to Open Source?
• Too much bureaucracy
Why NOT to Open Source?
• Low value to others
Why do we Open Source?
• Tech Brand / Hiring
Why do we Open Source?
• Collaboration with the community
Why do we Open Source?
• Feedback Loop
Why do we Open Source?
• Avoid NIH Syndrome
What do we Open Source?
What do we Open Source?
What do we Open Source?
What do we Open Source?
We’ve been at it for 3 years
• 51 projects later, what have we learned?
It works well
• Hiring / Tech Brand
• Collaboration
• Feedback loop
It does come at some cost
• Tending to PRs, Issues
• Forums, questions, discussions
• Balance: internal vs external priori...
Making it better
• Workshops: Zero 2 Cloud
• Packaging: Zero 2 Docker
• Deploying at smaller scale
Making it better
• Transparency
– Where are we investing
– What’s in maintenance / sunset mode?
Making it better
• Metrics – improve the feedback loop
Project Snoopdog
• Work in progress!
• Collect overall Netflix
and project by project
“health” metrics (snoops)
• Visualiz...
Overall Stats
W
ork
In
Progress
Project Ownership
Linking GitHub to Internal
Per repository stats
Making it better
• Ongoing support
Credit: http://words.steveklabnik.com/how-to-be-
an-open-source-gardener
Making it better
• No branches - Use what you Open Source
How you can get involved
Use NetflixOSS
Send us your feedback
Contribute!
Questions?
@netflixoss
@aspyker
@rusmeshenberg
Upcoming SlideShare
Loading in …5
×

Netflix oss past-present-future

1,617 views

Published on

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

Published in: Technology
  • Be the first to comment

Netflix oss past-present-future

  1. 1. Ruslan Meshenberg Andrew Spyker 4/2/2015
  2. 2. In a world of only OSS...
  3. 3. Why NOT to Open Source? • Competitive advantage
  4. 4. Why NOT to Open Source? • Embarrassing quality
  5. 5. Why NOT to Open Source? • Too much bureaucracy
  6. 6. Why NOT to Open Source? • Low value to others
  7. 7. Why do we Open Source? • Tech Brand / Hiring
  8. 8. Why do we Open Source? • Collaboration with the community
  9. 9. Why do we Open Source? • Feedback Loop
  10. 10. Why do we Open Source? • Avoid NIH Syndrome
  11. 11. What do we Open Source?
  12. 12. What do we Open Source?
  13. 13. What do we Open Source?
  14. 14. What do we Open Source?
  15. 15. We’ve been at it for 3 years • 51 projects later, what have we learned?
  16. 16. It works well • Hiring / Tech Brand • Collaboration • Feedback loop
  17. 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. 18. Making it better • Workshops: Zero 2 Cloud • Packaging: Zero 2 Docker • Deploying at smaller scale
  19. 19. Making it better • Transparency – Where are we investing – What’s in maintenance / sunset mode?
  20. 20. Making it better • Metrics – improve the feedback loop
  21. 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. 22. Overall Stats W ork In Progress
  23. 23. Project Ownership
  24. 24. Linking GitHub to Internal
  25. 25. Per repository stats
  26. 26. Making it better • Ongoing support Credit: http://words.steveklabnik.com/how-to-be- an-open-source-gardener
  27. 27. Making it better • No branches - Use what you Open Source
  28. 28. How you can get involved
  29. 29. Use NetflixOSS
  30. 30. Send us your feedback
  31. 31. Contribute!
  32. 32. Questions? @netflixoss @aspyker @rusmeshenberg

×