SAMPLE OSS Repo with Splunk CLA (Apache 2.0)
[Instructions on how to make your Splunk OSS project license-compliant]
These guidelines provide information on how to comply with the various Apache 2.0 license requirements. It also answers a few FAQs at the bottom of this page.
In addition to a LICENSE file that should contain the full text of your project's chosen license, the other four files you need to know about are the:
- NOTICE file
- README file
- CODE OF CONDUCT file
- CONTRIBUTING file
NOTICE File (Required when a project redistributes any 3P code)
Apache 2.0 requires projects to provide copyright attribution for redistributed dependencies in a NOTICE file. Generally, the attribution must include the project's name, version number, license type, and project URL (if available). Click here for more information.
Here are examples of how you can provide attribution:
README File (Required)
In addition to the documentation for your project, please include the following Splunk copyright notice to the bottom of your project's README file – this is to ensure it is prominently displayed. Please update the year as appropriate.
Copyright 2022 Splunk Inc.
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and limitations under the License.
CODE OF CONDUCT File (Optional)
The Code of Conduct Splunk uses is adapted from the Contributor Covenant, version 2.0, which is available here. We suggest that you include this text in your project to ensure that our engagements with the community remain safe, productive and professional.
CONTRIBUTING File (Required in order to accept 3P contributions)
If you anticipate accepting contributions from the open-source community you must include one of these options, see the CONTRIBUTING File. These agreements serve two main functions – first, to ensure that a contributor is legally authorized to make their contribution, and second, that they grant Splunk a license to use and redistribute the underlying IP (copyright or relevant patents).
Two Options:
As an alternative to the HTML CLA, you may also include the Splunk CLA Agreement Tracker. The choice yours but it is your responsibility to ensure that the contributors have signed the Splunk CLA before you accept their contributions.
Frequently Asked Questions
Can I use a third-party's proprietary IP (e.g., trademarks and product screenshots)?
Generally not. This creates IP issues for us down the road. We want to mitigate any 3P claims against Splunk.
Unless we have express permission to commercially exploit a 3P’s logo and trademarks, we cannot use them.
Can I add Splunk-owned IP (e.g., UI screenshots or logos/trademarks) or other forms of confidential information to my project?
Generally not. Including screenshots of our products affects our ability to file design patents and dilutes the value of
our tradedress. When in doubt, check with your Splunk Legal partner.