Posted by davidam on October 16, 2014 at 11:38am
IMHO, it would be a good idea add a question in the faq about how to license a new drupal module. From my point of view, I understand that the the contributors are adding a file called LICENSE.txt with the gplv2. In
https://www.gnu.org/licenses/gpl-howto.html, suggest license all files to avoid troubles adding a small note. Perhaps, we can use an only file LICENSE.txt in the drupal site and add this note.
This file is part of Drupal.
Drupal is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 2 of the License, or
(at your option) any later version.
Drupal is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with Drupal. If not, see <http://www.gnu.org/licenses/>.
Opinions?
Comments
The LICENSE.txt is added by the packaging script
davidam wrote:
The contributor does not add the file
LICENSE.txt. This file is added by the packaging script.Please see § 4.1 in this checklist (part of tutorial package for new contributors).
We add the full text of the license. While it is the standard GPLv2, the contributed software is downloaded on its own (not bundled with Drupal). It must have its own license.
This is also covered by
This is also covered by Drupal Git Repository Usage policy. Even if you use git clone to get a copy of a project before the LICENSE.txt is added by packaging (or to a sandbox project that is never packaged), the contributor has already agreed that "all files checked into the repository (code and assets) must be licensed under GNU/GPL version 2 and later".
Thanks
Thanks to both!. Now I can reference this subject.
http://www.davidam.com