Repository navigation
Write script to ensure file copyright policy #630
Description
Activity
Actually, for GPL you are meant to have the header in every file.
I don't think it does.
So…
-
The copyright notice should include the year in which you finished preparing the release (so if you finished it in 1998 but didn't post it until 1999, use 1998). You should add the proper year for each release; for example, “Copyright 1998, 1999 Terry Jones” if some versions were finished in 1998 and some were finished in 1999. If several people helped write the code, use all their names.
-
Always use the English word “Copyright”; by international convention, this is used worldwide, even for material in other languages. The copyright symbol “©” can be included if you wish (and your character set supports it), but it's not necessary. There is no legal significance to using the three-character sequence “(C)”, although it does no harm.
-
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 version1 of the GPL. In GNU programs the license is usually in a file called COPYING.
-
It is very important for practical reasons to include contact information for how to reach you, perhaps in the README file, but this has nothing to do with the legal issues of applying the license.
-
The copying permission statement should come right after the copyright notices. For a one-file program, the statement (for the GPL) should look like this …
For programs that are more than one file, it is better to replace “this program” with the name of the program, and begin the statement with a line saying “This file is part of NAME”. For instance,
This file is part of Foobar. Foobar 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 3 of the License, or (at your option) any later version. Foobar 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 Foobar. If not, see <http://www.gnu.org/licenses/>.-
- changed the title
[-]File copyright policy[/-][+][Discussion] File copyright policy[/+]on Aug 30, 2015 - changed the title
[-][Discussion] File copyright policy[/-][+]Write script to ensure file copyright policy[/+]on Apr 11, 2016 So in every file we want a header like this:
;; This file is a part of Haskell Mode. ;; Haskell Mode 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 3, or (at your option) ;; any later version. ;; Haskell Mode 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 this program. If not, see <http://www.gnu.org/licenses/>.The next step will be to take care of Author/Copyright headers:
;; Copyright 2004, 2005, 2007, 2008, 2009 XXX ;; Copyright 1997-1998 XXX ;; Author: 1997-1998 Guy Lapalme <lapalme@iro.umontreal.ca> ;; Keywords: indentation Haskell layout-rule ;; URL: http://www.iro.umontreal.ca/~lapalme/layout/index.html- ensure that there is a corresponding
Copyright XXXX Haskell Modefor every commit touching the file in year XXXX - if somebody feels like adding their name to Authors I guess it is okay with larger changes
- we do not care about
Keywords - we leave
URLas is for historical purposes
- ensure that there is a corresponding
I do not feel like fixing this. If somebody feels that this is important then you can have a go at this.
The copyright and license notice can be put in a common COPYING file. There is no justifiable reason to also require that it be included in every file, since the individual files are not individually distributed except
as part of the entire package.
For similar discussions look for example at:
Problems:
haskell-decl-scan.elwill be merged intohaskell-mode.el. What to do with peoples names listed there?Good thing is that everything is GPL and that gives room to clean up. Does anybody have experience how to take attribution under control?