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

Use full Apache License 2.0 text in LICENSE #5746

Closed
wants to merge 1 commit into from

Conversation

BigBlueHat
Copy link

Description

This PR adds the full license text of the Apache License 2.0 per the license application guidelines from the Apache Software Foundation:
https://www.apache.org/foundation/license-faq.html#Apply-My-Software

The current contents of the LICENSE file is meant for source file headers, not the LICENSE file.

Motivation and Context

This properly applies the Apache License 2.0 to this repository. Though, a more thorough application of the license would be to apply the license notice to each source file in this repository--see "How should I apply the Apache License to my own software?" for more information.

How Has This Been Tested?

Years of OSS compliance work and study. 😄

Checklist

My PR contains...

  • No code changes (src/ is unmodified: changes to documentation, CI, metadata, etc.)
  • Dependency changes (any modification to dependencies in package.json)
  • Bug fixes (non-breaking change which fixes an issue)
  • Improvements (misc. changes to existing features)
  • Features (non-breaking change which adds functionality)

My changes...

  • are breaking changes to a public API (config options, System API, major UI change, etc).
  • are breaking changes to a private API (Redux, component props, utility functions, etc.).
  • are breaking changes to a developer API (npm script behavior changes, new dev system dependencies, etc).
  • are not breaking changes.

Documentation

  • My changes do not require a change to the project documentation.
  • My changes require a change to the project documentation.
  • If yes to above: I have updated the documentation accordingly.

Automated tests

  • My changes can not or do not need to be tested.
  • My changes can and should be tested by unit and/or integration tests.
  • If yes to above: I have added tests to cover my changes.
  • If yes to above: I have taken care to cover edge cases in my tests.
  • All new and existing tests passed.

@hkosova
Copy link
Contributor

hkosova commented Dec 13, 2019

This PR looks like a duplicate of #5470.

@webron
Copy link
Contributor

webron commented Jan 9, 2020

Closing in favor of #5470.

@webron webron closed this Jan 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants