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.

1. Open
Community

2. hello!
Ryan Scott Brown
tweets @ryan_sb

3. 1. Landscape
Where we are

4. Open Platforms

5. Projects
OpenWhisk

6. OSS Checklist
□ Open license
□ Pay the rent
□ Work with contributors
□ Feedback loops

7. Agenda
□ Open licenses
□ Business models
□ Opening your community
□ Diversity and Inclusion

8. 2. Licensing
The rules for sharing

9. GNU Public License
□ Share Improvements
□ Disclose source
□ State changes
□ Patents ok

10. MIT License
□ Modify at will
□ Simple
□ Resale allowed

11. Apache License
□ Patents ok
□ Withholds trademark use
□ State changes

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. 3. Business
Keeping the lights on

14. Extra Services
□ Part of the Red Hat model
■ Support
■ Consulting
■ Testing & Verification
■ Packaging
□ Staff to scale

15. Dual License
□ MongoDB model
□ Ability to pay matters
□ Developer adoption

16. Open Core
□ Ansible core/Tower
□ Closed extras
□ Can’t stop contributors

17. Don’t Sell
□ Netflix model
□ Use your own tools
□ Save time
□ Better your own services

18. 4. Openness
Playing well with others

19. Four Opens
Source Development Design Community

20. Source
□ Everything
■ Source
■ Docs
■ Tests
□ No accounts
□ Visible license

21. Development
□ Pull requests
□ Issue tracker
□ Docs (again!)
□ Examples

22. Development
□ Issue templates
□ README.md
□ CONTRIBUTING.md

23. Design
□ OpenStack specs
□ Ansible proposals
□ Show where you’re going

24. Community
□ Be easy to find
□ Have sync and async
contacts
□ Recognize every
contribution

25. Contributor On-Ramp
□ Evaluate
□ Learn
□ Use
□ Contribute

26. 5. Inclusion
Everyone deserves a say

27. Including Everyone
□ No jerks
□ Respect volunteers
□ Really, no jerks

28. “ Diversity is having a
seat at the table.
Inclusion is having a
voice.

29. Code of Conduct
□ Visible
□ Readable
□ Real

30. Options Galore
□ Collective Code Construction
Contract
□ Contributor Covenant
□ Citizen Code of Conduct
□ Open Code of Conduct

31. Valuing Contributions
□ Someone made this
□ They deserve recognition
□ Code is not “better”

32. thanks!
Questions to @ryan_sb
Resources at
oss.serverless.zone
Creative Commons theme courtesy of SlidesCarnival
?