Skip to content

Correct copyright notices to reflect Copyright OpenSearch Contributors #21

@dblock

Description

@dblock

Update: the correct copyright is Copyright OpenSearch Contributors, without All Rights Reserved, without years for the OpenSearch part (leave years if any Elastic copyright is needed), and no Amazon-related stuff. See #24 for an example.

  1. Do you have a Copyright OpenSearch Contributors in README?
  2. Does copyright Copyright OpenSearch Contributors match between NOTICE.txt or NOTICE and README?
  3. Did you remove the year from Copyright 2021 OpenSearch Contributors in README and NOTICE?
  4. Do you have other copyrights properly represented in NOTICE, such as Elastic, if your code was forked?
  5. Did you remove all Copyright Amazon and Affiliates?
  6. Did you remove any other .md files that say anything about copyright?
  7. Is your CONTRIBUTING.md up-to-date saying to use short versions?
  8. Are you using short versions in your files? See Update OpenSearch LicenseHeaders to use the short version #29

FAQ

What source header should be on new OpenSearch files?

Assuming an Apache-2.0 project, new OpenSearch files should state the following:

# Copyright OpenSearch Contributors
# SPDX-License-Identifier: Apache-2.0

What if the file is a modified Apache-2.0 file from another project, and what if it already has a source header?

If files have any existing headers keep them. Add this OpenSearch license header to the top of the file. Note that it has additional lines to indicate the file has been modified, and the copyright is identified at the end of the header:

# SPDX-License-Identifier: Apache-2.0
#
# The OpenSearch Contributors require contributions made to this file be licensed 
# under the Apache-2.0 license or a compatible open source license.
# 
# Modifications Copyright OpenSearch Contributors. See
# GitHub history for details.
What if the file is an OpenDistro file and it includes an OpenDistro for ElasticSearch project Amazon copyright header?

Amazon employees may remove the OpenDistro for ElasticSearch Amazon copyright header when bringing code into OpenSearch; Amazon are an OpenSearch Contributor. For example, the source header on this opendistro file.

    * /*
         * Copyright 2020 Amazon.com, Inc. or its affiliates. All Rights Reserved.
         *
         * Licensed under the Apache License, Version 2.0 (the "License").
         * You may not use this file except in compliance with the License.
         * A copy of the License is located at
         *
         *     http://www.apache.org/licenses/LICENSE-2.0
         *
         * or in the "license" file accompanying this file. This file 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.
         */

After removing the OpenDistro for ElasticSearch header as seen above, use the OpenSearch header:

# Copyright OpenSearch Contributors
# SPDX-License-Identifier: Apache-2.0

What goes in the NOTICE file?

The NOTICE file should contain the name of the project, a top level copyright statement, and any additional required notices (such as copyright statements) that the source within the project requires be communicated to users. This would include any NOTICE files that apply to other Apache-2.0 licensed code within the project’s source.

Note that the NOTICE file only covers the content of the project. It should not contain notices related to dependencies that are provided separately from that project (for example, dependencies within a Gradle build file).


Via https://twitter.com/IntranetFocus/status/1414878242721476610:

Screen Shot 2021-07-14 at 4 40 46 PM

On our site we say:

Screen Shot 2021-07-14 at 4 41 24 PM

In this project and OpenSearch core we don't include "contributors":

Screen Shot 2021-07-14 at 4 41 53 PM

Let's figure out what the right way of saying all these things is and make sure it's both explained and aligned.

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions