Opscode Sponsored Open Source Projects
There are a number of other smaller projects, such as the mixlib libraries, that we sponsor as dependencies of Chef.
Licensing and copyright
Why is your software Apache Licensed?
It allows you to:
It forbids you to:
It requires you to:
It does not require you to:
How should I update the header file of my contribution to properly credit earlier contributors and recognize copyrights?
You need to put attribution about the origins of some of the code in the NOTICE file for your app. On an individual header, you can add yourself as an author/copyright holder, placing text in the header file saying that your new work is based on previous work, and referencing the original header below.
Do I need the agreement of anyone else whose authorship/copyright I come across?
You can re-use the work without having to get the agreement of the original authors, as long as
The Apache License grants these rights to those who receive a copy of the software.
CLAs and CCLAs
Why do I need to fill out a CLA?
You should read and understand the entire CLA before signing it. Our description of it is not legally binding.
The CLA is beneficial to our contributors and users because:
The most important thing about the CLA is that it doesn't give Opscode any special rights - it just makes things more explicit.
Can you accept my contribution without a CLA (I'll sign it later, I promise!)?
No. We must have a signed CLA before we can merge your changes to any of our projects.
When do I need to have my company sign a CCLA?
If you are contributing to an Opscode project while doing work on company time, or utilizing company resources, you should have your company sign a CCLA.
How do I add additional employees to my existing CCLA?
How do I change the point of contact on my existing CCLA?
If you need to update the point of contact for the CCLA, the current contact should email email@example.com with the full name and email address of the new contact. If the existing contact is no longer available, please contact us and we will help you out.
Contribute Changes to Opscode-Managed Apache Licensed Cookbooks at the Community Site. All other cookbooks require no CLA
Once you have signed a CLA and have a ticket referencing your request, see How to Contribute to Opscode Cookbooks.
Opscode doesn't maintain all the cookbooks on the community site, and individual maintainers choose whatever license they like. Contact those authors to find out what their contribution process is.
If you have created your own cookbook you would like to share with the community, read about adding a cookbook to the community site.
Do I have to use GitHub for my fork of the repository?
Nope - but it makes everyone's lives easier if you do. We'll be happy to pull from any repository you like.
Why do I need to have a ticket associated with my patch?
When working on the code, having patches associated with tickets helps other contributors understand why a change was made. This is important in distributed software projects where you can't go over and ask a colleague about the code. It also helps us coordinate the changelog for future releases, and provides for recognizing community participation.
You use GitHub, why don't you use GitHub Pull Requests?
We use JIRA for our open source projects and for our own internal projects: managing all the details of the code base, and fulfilling license requirements for our joint benefit. We also interact regularly with the GitHub issues/pull request system. You are welcome to open a pull request, and link to that when updating the Jira ticket for a contribution.