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
I've configured my IDE to add this for me, but mostly out of an overabundance of caution. Google searches I have done on the topic suggest that we don't need to add them to every file, however that seems like it might conflict with the license itself (emphasis mine):
To apply the Apache License to specific files in your work, attach the following boilerplate declaration, replacing the fields enclosed by brackets "[]" with your own identifying information. (Don't include the brackets!) Enclose the text in the appropriate comment syntax for the file format. We also recommend that you include a file or class name and description of purpose on the same "printed page" as the copyright notice for easier identification within third-party archives.
because they don't point to a specific portion of the Apache license that states what needs to be at the top of every file.
What's not totally clear to me is if this file the first sentence only applies when some portion of a project is licensed under Apache 2.0, but not others, or if it should be applied to every file. I am not a lawyer and I shouldn't be interpreting legal documents, therefore before we remove the license, we should check with our legal department.
I've configured my IDE to add this for me, but mostly out of an overabundance of caution. Google searches I have done on the topic suggest that we don't need to add them to every file, however that seems like it might conflict with the license itself (emphasis mine):
What's not totally clear to me is if this file the first sentence only applies when some portion of a project is licensed under Apache 2.0, but not others, or if it should be applied to every file. I am not a lawyer and I shouldn't be interpreting legal documents, therefore before we remove the license, we should check with our legal department.
Brought up by @abhikuhikar in #74 (comment)_
The text was updated successfully, but these errors were encountered: