You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To apply the Apache License to specific files in your work, attach the following boilerplate declaration [...]
The problem is that the Github template basically suggests that using the "boilerplate notice" is mandatory in all files. This would raise questions like "how do you license a [standards compliant] JSON file?!" (remember the Apache 2.0 license explicitly include configuration files as licensed material).
Ideally the GH template should be made more in line with the official information.
The text was updated successfully, but these errors were encountered:
I was using these license templates to add an Apache 2.0 license to a project. Happens that I was faced with a problem, namely the
APPENDIX
section.The Github template reads:
While the official information reads:
The problem is that the Github template basically suggests that using the "boilerplate notice" is mandatory in all files. This would raise questions like "how do you license a [standards compliant] JSON file?!" (remember the Apache 2.0 license explicitly include configuration files as licensed material).
Ideally the GH template should be made more in line with the official information.
The text was updated successfully, but these errors were encountered: