LICENSE.txt gets added automatically by the Drupal.org packaging script, so shouldn't be included in the Git repository in any of your branches.

Comments

CZ’s picture

CZ commented
Category: bug » task
CZ’s picture

CZ commented
Status: Active » Closed (won't fix)

A COPYING or LICENSE file with the GPL text[1] should be included in a GPL program.

"You should also include a copy of the license itself somewhere in the distribution of your program. All programs, whether they are released under the GPL or LGPL, should include the text version of the GPL. In GNU programs the license is usually in a file called COPYING." [2].

So I can not delete the license file. The way of downloading (terminal or browser) is not critical.

[1] www.gnu.org/licenses/gpl.txt

[2] www.gnu.org/licenses/gpl-howto.en.html

tr’s picture

tr commented

It's really not a matter for interpretation. The entire Drupal repository is licensed under a uniform license, and individual projects should not store license information in the project's repository. That's always been the rule in Drupal, and if you look at other projects you'll see that literally 99% of the 10,000+ projects hosted in the Drupal repository follow this rule. The fewer than 100 projects that don't, like this one, are wrong.

Distributions of Drupal modules have the correct license attached automatically, which you can verify by looking in any of the .tar.gz archives available for download from your project page. The license file in those archives is the Drupal standard license file (look at the creation date!) which REPLACED your license file. Your license file DOESN'T get distributed, it gets overwritten by the Drupal standard.

CZ’s picture

CZ commented

The contributed modules on drupal.org are not part of Drupal "Drupal repository" (witch have a license file). I am not happy about the Drupal.org packaging script, because for example the themebuilder module is licensed under GPLv3 and not GPLv2.

This is not a "bug" (or issue) of Page Style module or Text Size, this is a "bug" or "issue" of the Drupal.org packaging script. Please stop the adding of wrong "bugs".

tr’s picture

tr commented

Correction - contributed modules on drupal.org ARE part of the Drupal repository. That's the point.

CZ’s picture

CZ commented

No. Contributed modules (the name say it) are not part of "Drupal" or the "drupal repository" ("project/drupal"), if so, they are in the core of Drupal. Contributed modules are hosted on drupal.org like GitHub, but drupal.org is not the (project) CMS Drupal.

ron williams’s picture

ron williams commented
Status: Closed (won't fix) » Active

Hi Christian,
I see you closed this task and left the license.txt file in place. I understand you license your code under a different version of GPL than Drupal.org, but this is not allowed.

For reference, please review section 4.1 "Ensure the repository does not contain a ‘LICENSE.txt’ file". In addition, it would be helpful to also review section Hosting code at Drupal.org which explicitly states the license used is "the same as Drupal itself."

Thanks for your help keeping software properly licensed on Drupal.org. By using a standard license, every contributor makes it easier for their code to be incorporated into Drupal Core.

mgifford’s picture

mgifford
he/him
Primary language English
commented
Issue summary: View changes
Issue tags: +gpl, +license issues

Tagging to get some clarity from folks looking at how to deal with the GPL3.

CZ’s picture

CZ commented
Status: Active » Fixed

GPLv2 is ok (GPLv3 also).

  • CZ committed 23d6cee on 7.x-1.x 
    Issue #1481364 by TR. Fixed, Issue #1931584 by mgifford. Fixed, Issue #...

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.