- Issue created by @rushiraval
- Assigned to Mohd Sahzad
- Status changed to Needs review
8 months ago 6:41am 27 October 2023 - @rushikesh-raval opened merge request.
- Issue was unassigned.
- Status changed to Needs work
8 months ago 11:02am 27 October 2023 - 🇮🇹Italy apaderno Brescia, 🇮🇹
There is no need to remove the license file. As long as the license is the same used by Drupal core, the license file can stay.
- Status changed to Needs review
8 months ago 12:54pm 27 October 2023 - 🇮🇳India rushiraval
license file is already there. There was two file licence and licence.txt. so licence.txt removed.
- Status changed to Needs work
8 months ago 4:05pm 27 October 2023 - 🇮🇹Italy apaderno Brescia, 🇮🇹
Yes, but it is removing the wrong file. LICENSE.txt is GPLv2; LICENSE is GPLv3.
Modules hosted on drupal.org can only be licensed using the same license used by Drupal core, which is not GPLv3. - 🇮🇹Italy apaderno Brescia, 🇮🇹
No. You can release your work under any GPL version 2 or later compatible license, however, you may only check it into Drupal's Git repositories if you are releasing it under the same license as Drupal itself, that is, GPL version 2 or later, allowing users to choose between the terms of the GPL version 2 or the terms in any new versions as updated by the FSF. If you are unable or unwilling to do so, do not check it into a Drupal Git repository.