Abstract
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.
Resources
- First, the slides
- The OpenStack 4 Opens
Licensing
The Open Source Initiative keeps a list of approved licenses that meet the open-source definition that includes free redistribution, non-discrimination, freely available source code, and other requirements.
The most popular open source licenses are (in no particular order):
Github provides choosealicense.com to help distinguish between different licenses when starting a project.
Foundations/Organizations
- The Linux Foundation
- The Apache Software Foundation which supports tons of projects including Hadoop, Spark, Kafka, Mesos, and more
- The Cloud Native Computing Foundation which is incubating Kubernetes and Prometheus
Code of Conduct
- The Contributor Covenant is itself open source, and is used by 15,000+ projects.
- The Capital One Open Code of Conduct that is used for Cloud Custodian and other projects.
- The Collective Code Construction Contract (C4) is part code of conduct, and part collaboration model for open-source projects and covers topics like the use of an issue tracker, and expectations of maintainers and contributors.
- The Citizen Code of Conduct
- The Open Code of Conduct