Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add license notices in source code #157

Merged
merged 3 commits into from
Aug 9, 2022

Conversation

lopopolo
Copy link
Member

@lopopolo lopopolo commented Aug 9, 2022

Per the Apache 2.0 License, a boilerplate notice must be included in all
source files to apply the license to this work:

   APPENDIX: How to apply the Apache License to your work.

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright [yyyy] [name of copyright owner]

   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.

Several of the Rust sources in src have such a notice, which
communicates the dual license of this crate as either Apache 2.0 OR MIT.

This commit fixes up the file paths referred to in these comments and
adds notice to source files that do not have one.

Per the Apache 2.0 License, a boilerplate notice must be included in all
source files to apply the license to this work:

```
   APPENDIX: How to apply the Apache License to your work.

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright [yyyy] [name of copyright owner]

   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.
```

Several of the Rust sources in `src` have such a notice, which
communicates the dual license of this crate as either Apache 2.0 OR MIT.

This commit fixes up the file paths referred to in these comments and
adds notice to source files that do not have one.
@lopopolo lopopolo added the A-packaging Area: Packaging releases for distribution. label Aug 9, 2022
@lopopolo lopopolo merged commit 8f57330 into trunk Aug 9, 2022
@lopopolo lopopolo deleted the lopopolo/source-notice-apache-2.0 branch August 9, 2022 05:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-packaging Area: Packaging releases for distribution.
Development

Successfully merging this pull request may close these issues.

1 participant