Alef event - going open source

672 views

Published on

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
672
On SlideShare
0
From Embeds
0
Number of Embeds
17
Actions
Shares
0
Downloads
6
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • XAP, Why Cloudify, Java infra, geared for high perf, short detection times -->scales up to a few hundred of nodes legacy protocols 
  • Componentize and generalize
  • It’s not just about the code, it’s about the way you run things
    4 million projects on github, no one will know you’re there.
  • Support, devs, marketing, management
    Daily standups include community status
    Weekly meetings with marketing,
    events,
    blogs,
    discussions all the way up to CEO about goals, hurdles etc.
  • devops - larger scales, dynamic languages, a lot of choices 
  • Use github,
    Small
    Readme,
    build,
    dependencies,
    changelog,
    State maturity,
    supported envs,
    license,
    docs,
    tags,
    announce,
    milestones…
  • Contributor agreement
    Pull request
    License
  • Share Your Roadmap
    Share Your Darkest Secrets
  • Move from windows mostly to linux mostly, eat our own dog food and use what are users will be using
  • devops - larger scales, dynamic languages, a lot of choices 
  • OpenStack is here to stay, that’s why we’re all here. Most of the orgs we talked with have an openstack initiative, we wanted to be aligned with it, cactus/diablo
    Options to get in: contribute to projects, donate code – stackforge or not
  • Alef event - going open source

    1. 1. Going Open Source Tales of a (ex-) closed source company Uri Cohen Head of Product @ GigaSpaces @uri1803 Nir (don’t call me "Devops") Cohen Prospers@Gigaspaces @thinkops http://www.slideshare.net/uri1803/alef-event-going-open-source
    2. 2. What This Talk Won’t Cover
    3. 3. How to Manage an Open Source Project
    4. 4. When / What to Open Source https://www.madison.k12.wi.us/files/Calendar_0.jpg
    5. 5. Which License to Choose
    6. 6. And I won’t say “Software is eating the world” Really, I Promise…
    7. 7. What I Will Talk about Our Journey as a company, moving from closed to open source
    8. 8. Some Background
    9. 9. Why Open Source? Aside from the obvious reasons, it’s become a precondition
    10. 10. Why Open Source? It makes your software better
    11. 11. So Here’s What You Shouldn’t Do
    12. 12. This Developers, Developers, Developers, Developers, Developers, Developers
    13. 13. Put It on Github and Think You’re Done http://octodex.github.com/hipster-partycat/
    14. 14. Have a “Community Guy” that Handles All This OSS Stuff…
    15. 15. Check the Mailing Lists Once a Week http://www.cetofnc.com/images/2009/angry_user.jpg
    16. 16. What Worked for Us
    17. 17. Get Everyone Involved It’s not a developer thing, it’s a company mindset
    18. 18. Know Your Eco-System
    19. 19. Make It Easy to Consume
    20. 20. Cut the Bureaucracy, Make It Easy for People to Contribute
    21. 21. Be Transparent
    22. 22. Adapt Your Skill Set
    23. 23. Go Linux…
    24. 24. Adopt a Community
    25. 25. Some of the Projects We Own/Contribute to
    26. 26. Cloudify
    27. 27. Packman
    28. 28. pylog
    29. 29. OpenStack
    30. 30. jclouds
    31. 31. libcloud
    32. 32. Flask to Swagger
    33. 33. References • Cloudify: getcloudify.org • Cloudify on github: github.com/cloudify-cosmo • Packman: packman.readthedocs.org/en/latest/ • Pylog: pylog.readthedocs.org/en/latest/
    34. 34. Thank You!

    ×