docs: improve license application

[char0n]

• use canonical version of the license from https://www.apache.org/licenses/LICENSE-2.0.txt
• use license without rewording
• use NOTICE file to provide copyright notice

Refs #711

---

I understand that changing anything around the license is always very precarious. Nevertheless I've created this PR to demonstrate what I describe in #711.

[dalelane]

IANAL so this is a very hesitant "approve", but #711 makes a convincing argument :-)

[derberg]

NOTICE looks consistent with the official statement -> https://infra.apache.org/apply-license.html. I made only one small suggestion

I'm not sure about modifications in LICENSE file though. Official document is not clear and I see OpenAPI and CloudEvents folks do it the way we do it 🤔

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[char0n]

NOTICE looks consistent with the official statement -> https://infra.apache.org/apply-license.html. I made only one small suggestion

Suggestion accepted, thanks.

I'm not sure about modifications in LICENSE file though. Official document is not clear and I see OpenAPI and CloudEvents folks do it the way we do it thinking

Yes many projects do it like that. They modify the canonical license text, specifically the appendix which is intended to be copied to source file headers and then be modified. By doing this modification one can say that copyright notice is specific to the license text modification and not the creative work it tries to license. But again, I'm not a layer, I just proposed a way how to enhance the license application as recommended by Apache Foundation.

[derberg]

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.

it's just that ☝🏼 sounds like we should actually modify the license file with info about Linux Foundation.
I haven't found any official info from Apache that we should do it your proposed way, except for the NOTICE

[char0n]

Right, so what is says is that if you have file called index.js with following content:

export const variable = 1;

and want to apply the Apache 2.0 license to it explicitly, you take boilerplate from the license appendix, amend the copyright notice:

   Copyright 2021-2022 AsyncAPI Initiative

   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.

and apply it to the index.js file in following way:

//   Copyright 2021-2022 AsyncAPI Initiative
//
//   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.

export const variable = 1;

---

This is usually done in Java and C, C++ projects. Every file in the source code has a license header. That's why the licence talk about the file comment format: The text should be enclosed in the appropriate comment syntax for the file format. Every source file has different comment mechanism in different languages.

[derberg]

oh yes, now I get it!!! thanks so much @char0n for your patience.

LGTM 🚀

@dalelane please have a look again
@fmvilas have a look sir

[fmvilas]

/au

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[fmvilas]

/rtm

[asyncapi-bot]

🎉 This PR is included in version 2.5.0-next-major-spec.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[fmvilas]

Forget about the last comment saying it was released in version 2.5.0-next-major-spec.1. I made a mistake and it created this version but it should actually be 3.0.0-next-major-spec.1. There's a notice in the release. Apologies for the noise.

[asyncapi-bot]

🎉 This PR is included in version 2.5.0-next-spec.5 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[derberg]

Recent comments about the release from the bot were added by mistake. More details in #899