Apache 2.0 License template is incorrect

The template for the Apache 2.0 license when creating a LICENSE file in a repository is not correct. If you read the tail end of the Apache 2.0 license it indicates “how to apply the Apache 2.0 license to your work”, and the template provided by GitHub is not as it should be. In fact, at the bottom of the template you can even see some of the placeholder template data.

The end of the existing Apache 2.0 reads:

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.

This indicates that a proper application of the Apache 2.0 license should be as follows:

Copyright 2020 ACME, LLC.

   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.

I’m worried that this may have an effect on repositories that have adopted the Apache 2.0 license via the template provided by GitHub

Hi @nathan-fiscaletti,

Thanks for being here! If you  include a detectable license such as Apache, user’s can see this on the top on your repository for example:

Screen Shot 2020-05-21 at 2.53.03 PM.png

If you’ve created the repo and need to apply the license post creation, you can do so by following this instructions: https://help.github.com/en/github/building-a-strong-community/adding-a-license-to-a-repository

Hi!

If you develop license managers, you can try to publish some of your extensions on this site: https://www.openlm.com/developers/

GitHub uses the Ruby Gem Licensee for systematically detecting the license of repositories (GitHub documentation). It detects among 38 different licenses out of which 29 are OSI-approved licenses (28 active licenses and 1 superseded). These licenses include the most commonly used ones.

See https://github.com/licensee/licensee/issues/393 for an explanation about the Apache-2.0 boilerplate by @mlinksva.

1 Like