Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.
Open Community
hello! Ryan Scott Brown tweets @ryan_sb
1. Landscape Where we are
Open Platforms
Projects OpenWhisk
OSS Checklist □ Open license □ Pay the rent □ Work with contributors □ Feedback loops
Agenda □ Open licenses □ Business models □ Opening your community □ Diversity and Inclusion
2. Licensing The rules for sharing
GNU Public License □ Share Improvements □ Disclose source □ State changes □ Patents ok
MIT License □ Modify at will □ Simple □ Resale allowed
Apache License □ Patents ok □ Withholds trademark use □ State changes
Amazon License □ Not actually open - beware! “The Work and any derivative works thereof only may be used or intended for u...
3. Business Keeping the lights on
Extra Services □ Part of the Red Hat model ■ Support ■ Consulting ■ Testing & Verification ■ Packaging □ Staff to scale
Dual License □ MongoDB model □ Ability to pay matters □ Developer adoption
Open Core □ Ansible core/Tower □ Closed extras □ Can’t stop contributors
Don’t Sell □ Netflix model □ Use your own tools □ Save time □ Better your own services
4. Openness Playing well with others
Four Opens Source Development Design Community
Source □ Everything ■ Source ■ Docs ■ Tests □ No accounts □ Visible license
Development □ Pull requests □ Issue tracker □ Docs (again!) □ Examples
Development □ Issue templates □ README.md □ CONTRIBUTING.md
Design □ OpenStack specs □ Ansible proposals □ Show where you’re going
Community □ Be easy to find □ Have sync and async contacts □ Recognize every contribution
Contributor On-Ramp □ Evaluate □ Learn □ Use □ Contribute
5. Inclusion Everyone deserves a say
Including Everyone □ No jerks □ Respect volunteers □ Really, no jerks
“ Diversity is having a seat at the table. Inclusion is having a voice.
Code of Conduct □ Visible □ Readable □ Real
Options Galore □ Collective Code Construction Contract □ Contributor Covenant □ Citizen Code of Conduct □ Open Code of Con...
Valuing Contributions □ Someone made this □ They deserve recognition □ Code is not “better”
thanks! Questions to @ryan_sb Resources at oss.serverless.zone Creative Commons theme courtesy of SlidesCarnival ?
Próxima SlideShare
Cargando en…5
×

Ryan Brown - Open Community

941 visualizaciones

Publicado el

Presented at ServerlessConf NYC 2016.

There are a number of open source projects built around closed platforms like AWS Lambda/Google Cloud Functions and open serverless projects like OpenWhisk and LeverOS. In this talk we'll cover what motivates contributors, what sends them running the other direction, and how you can help your project grow. Building a project on top of closed technology is an extra challenge without insight into where it's going. Learn how to manage continuous integration with your project against your (closed) dependencies and make sure bugs stay fixed.

Publicado en: Internet
Licencia: CC Attribution License
no profile picture user

  • Inicia sesión para ver los comentarios

  • Sé el primero en recomendar esto

Ryan Brown - Open Community

  1. 1. Open Community
  2. 2. hello! Ryan Scott Brown tweets @ryan_sb
  3. 3. 1. Landscape Where we are
  4. 4. Open Platforms
  5. 5. Projects OpenWhisk
  6. 6. OSS Checklist □ Open license □ Pay the rent □ Work with contributors □ Feedback loops
  7. 7. Agenda □ Open licenses □ Business models □ Opening your community □ Diversity and Inclusion
  8. 8. 2. Licensing The rules for sharing
  9. 9. GNU Public License □ Share Improvements □ Disclose source □ State changes □ Patents ok
  10. 10. MIT License □ Modify at will □ Simple □ Resale allowed
  11. 11. Apache License □ Patents ok □ Withholds trademark use □ State changes
  12. 12. Amazon License □ Not actually open - beware! “The Work and any derivative works thereof only may be used or intended for use with the web services, computing platforms or applications provided by Amazon.com, Inc. or its affiliates, including Amazon Web Services, Inc.” https://aws.amazon.com/asl/
  13. 13. 3. Business Keeping the lights on
  14. 14. Extra Services □ Part of the Red Hat model ■ Support ■ Consulting ■ Testing & Verification ■ Packaging □ Staff to scale
  15. 15. Dual License □ MongoDB model □ Ability to pay matters □ Developer adoption
  16. 16. Open Core □ Ansible core/Tower □ Closed extras □ Can’t stop contributors
  17. 17. Don’t Sell □ Netflix model □ Use your own tools □ Save time □ Better your own services
  18. 18. 4. Openness Playing well with others
  19. 19. Four Opens Source Development Design Community
  20. 20. Source □ Everything ■ Source ■ Docs ■ Tests □ No accounts □ Visible license
  21. 21. Development □ Pull requests □ Issue tracker □ Docs (again!) □ Examples
  22. 22. Development □ Issue templates □ README.md □ CONTRIBUTING.md
  23. 23. Design □ OpenStack specs □ Ansible proposals □ Show where you’re going
  24. 24. Community □ Be easy to find □ Have sync and async contacts □ Recognize every contribution
  25. 25. Contributor On-Ramp □ Evaluate □ Learn □ Use □ Contribute
  26. 26. 5. Inclusion Everyone deserves a say
  27. 27. Including Everyone □ No jerks □ Respect volunteers □ Really, no jerks
  28. 28. “ Diversity is having a seat at the table. Inclusion is having a voice.
  29. 29. Code of Conduct □ Visible □ Readable □ Real
  30. 30. Options Galore □ Collective Code Construction Contract □ Contributor Covenant □ Citizen Code of Conduct □ Open Code of Conduct
  31. 31. Valuing Contributions □ Someone made this □ They deserve recognition □ Code is not “better”
  32. 32. thanks! Questions to @ryan_sb Resources at oss.serverless.zone Creative Commons theme courtesy of SlidesCarnival ?

×