Improper Apache 2.0 license application

[char0n]

Hello everybody,

I've noticed that the Apache 2.0 license is applied to this repository in probably improper way. The license text has been changed in license appendix to provide an explicit copyright notice. This is IMHO an improper application of the license, and by doing this the license looses the Reusable without rewording attribute.

Apache 2.0 license appendix is design to be copied to individual files and only in this case the copyright notice should be changed. But this repo is not using appendix so the best option here would be to create a NOTICE file containing explicit copyright notice. The license itself recommends this in 4. d). The NOTICE file can contain following:

AsyncAPI Specification
Copyright The Linux Foundation

I've written more extensive elaboration on this topic here: https://vladimirgorej.com/blog/how-to-apply-apache2-license-to-your-open-source-software-project/

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity :sleeping:

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience :heart:

[char0n]

https://github.com/asyncapi/spec/pull/783 has been merged directly to master. Closing.

[smoya]

@char0n I guess this change should be propagated to each individual repository that applies wrongly the Apache 2.0 license. Right?

cc @derberg @fmvilas

[char0n]

@smoya yes, ideally. I can handle it after the release effort is over.

[smoya]

@smoya yes, ideally. I can handle it after the release effort is over.

I think we could use the file replicator action from https://github.com/asyncapi/.github/blob/master/.github/workflows/global-replicator.yml#L3-L9

cc @derberg wdyt?

[derberg]

@smoya good catch, definitely we should do it through global workflow so it is synchronized everywhere in the same form