Created by: grokify
PR checklist
-
Read the contribution guidelines. -
Ran the shell script under ./bin/to update Petstore sample so that CIs can verify the change. (For instance, only need to run./bin/{LANG}-petstore.shand./bin/security/{LANG}-petstore.shif updating the {LANG} (e.g. php, ruby, python, etc) code generator or {LANG} client's mustache templates). Windows batch files can be found in.\bin\windows\. -
Filed the PR against the correct branch: master,3.1.x,4.0.x. Default:master. -
Copied the technical committee to review the pull request if your PR is targeting a particular programming language.
Description of the PR
Update the Apache 2.0 LICENSE file to a more standard format to support GitHub license display and GitHub license search. This format is more standard for GitHub and Apache Foundation. The file used here is the exact file GitHub provides for a new Apache 2.0 repo with the exception of updates for copyright holders.
GitHub license display:
https://blog.github.com/2016-09-21-license-now-displayed-on-repository-overview/
GitHub license search:
https://help.github.com/articles/licensing-a-repository/
This file uses the license provided by GitHub when creating a new repo with the Apache 2.0 license with changes limited to copyright year and owners. It is similar to the one Apache Foundation uses for httpd:
https://github.com/apache/httpd/blob/trunk/LICENSE
This is what this LICENSE file looks like on my fork:
