Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Licence and copyright information are missing #103

Closed
ghost opened this issue Apr 26, 2011 · 2 comments
Labels
bug

Comments

@ghost
Copy link

@ghost ghost commented Apr 26, 2011

Hello,

There is a problem with the Pelican's license:
According to this page, «a copyright notice» and «a statement of copying permission» must be present in the header of all files of Pelican, like this:

#!/usr/bin/env python
# -*- coding: utf-8 -*- #
#
#    Copyright (c) 20XX-2011   XXXXXX XXXXXXX
#
#    This file is part of Pelican.
#
#    Pelican is free software: you can redistribute it and/or modify
#    it under the terms of the GNU Affero General Public License as published by
#    the Free Software Foundation, either version 3 of the License, or
#    (at your option) any later version.
#
#    Pelican 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 Affero General Public License for more details.
#
#    You should have received a copy of the GNU Affero General Public License
#    along with Pelican.  If not, see <http://www.gnu.org/licenses/>. 
#

But this text is only present in the LICENSE file, instead of the complete license

@almet

This comment has been minimized.

Copy link
Member

@almet almet commented Apr 26, 2011

Having a header like this one in all pelican's files seems more than annoying to me. After some search, it seems that the recommended practice is to to add the notice in every file, but not doing so will not invalidate the license or change the meaning of it (http://stackoverflow.com/questions/153148/adding-the-gpl-license-to-c-projects).

Anyway, I will change the LICENSE text.

@ghost

This comment has been minimized.

Copy link
Author

@ghost ghost commented Apr 26, 2011

After some search, it seems that the recommended practice is to to add the notice in every file, but not doing so will not invalidate the license

Interesting, I did not know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.