- Issue created by @dydave
- Merge request !144Issue #3522518 by dydave: Removed file 'LICENSE.TXT' from module's code base. → (Merged) created by dydave
Based on 📌 Remove LICENSE.TXT file Active .
The file LICENSE.txt is not needed.
As per similar issue #141346: no need for license file → :
The packaging script will create the LICENSE.txt in your tarball - so there is no need to add your own file and it should be removed.
or issue 📌 Remove LICENSE.TXT file Closed: works as designed :
LICENSE.txt should be removed since Drupal will add the appropriate license file automatically during packaging.
https://www.drupal.org/node/1587704#licensingchecks →
More details also in issue #1663716: Drupal.org packaging script overwrite LICENSE.txt file → .
Remove file LICENSE.txt.
There doesn't seem to be a standard or specific rule about the License file:
It could very well be kept in the repo, as long as it complies with the one used by Drupal core.
See #3350759-7: Remove LICENSE.TXT file → :
Application checklist → is a documentation page on opting into security advisory coverage; it should have not been used to tell maintainers they need to remove the license file.
Drupal Git Contributor Agreement & Repository Usage Policy → does not forbid to add a license file in a project repository; it just says that projects hosted on drupal.org are licensed under the same license used by Drupal core. As long as the license is correct, the file can stay.
Since there is no particular reason the module should be using a license different from the one used by Drupal core, it doesn't seem necessary in this case and therefore should probably be removed.
Active
3.0
Miscellaneous