Mercurial > emacs
comparison admin/notes/copyright @ 75934:5fa0ec2c14d1
lisp/term/README dealt with.
author | Glenn Morris <rgm@gnu.org> |
---|---|
date | Fri, 16 Feb 2007 08:05:35 +0000 |
parents | b32ceebb6e78 |
children | 6cbb395e88b0 |
comparison
equal
deleted
inserted
replaced
75933:e95762f4a9a2 | 75934:5fa0ec2c14d1 |
---|---|
70 (eg Gnus, MH-E), but I think in every case this happens automatically | 70 (eg Gnus, MH-E), but I think in every case this happens automatically |
71 (?). | 71 (?). |
72 | 72 |
73 All README (and other such text files) that are non-trivial should | 73 All README (and other such text files) that are non-trivial should |
74 contain copyright statements and GPL license notices, exactly as .el | 74 contain copyright statements and GPL license notices, exactly as .el |
75 files do (see e.g. README in the top-level directory). (Before 2007, | 75 files do (see e.g. README in the top-level directory). Before 2007, |
76 we used a simple, short statement permitting copying and modification | 76 we used a simple, short statement permitting copying and modification |
77 provided legal notices were retained. In Feb 2007 we switched to the | 77 provided legal notices were retained. In Feb 2007 we switched to the |
78 standard GPL text, on legal advice.) | 78 standard GPL text, on legal advice. Some older text files in etc/ |
79 should, however, keep their current licenses (see below for list). | |
79 | 80 |
80 For image files, the copyright and license details should be recorded | 81 For image files, the copyright and license details should be recorded |
81 in a README file in each directory with images. (Legal advice says | 82 in a README file in each directory with images. (Legal advice says |
82 that we need not add notices to each image file individually, if they | 83 that we need not add notices to each image file individually, if they |
83 allow for that.). It is recommended to use the word "convert" to | 84 allow for that.). It is recommended to use the word "convert" to |
219 if you can clarify its legal status. | 220 if you can clarify its legal status. |
220 | 221 |
221 | 222 |
222 ** Some notes on resolved issues, for historical information only | 223 ** Some notes on resolved issues, for historical information only |
223 | 224 |
225 lisp/term/README | |
226 - had no copyright notice till Feb 2007. ChangeLog.3 suggests it was | |
227 written by Eric Raymond. When asked by rms on 14 Feb 2007 he said: | |
228 | |
229 I don't remember writing it, but it reads like my prose and I believe | |
230 I wrote the feature(s) it's describing. So I would have been the | |
231 likeliest person to write it. | |
232 | |
233 Odds are that I did, but I'm not certain. | |
234 | |
235 Accordingly, FSF copyright was added. | |
236 | |
224 | 237 |
225 *** These are copyright issues that need not be fixed until after | 238 *** These are copyright issues that need not be fixed until after |
226 Emacs 22 is released (though if they can be fixed before, that is | 239 Emacs 22 is released (though if they can be fixed before, that is |
227 obviously good): | 240 obviously good): |
228 | 241 |
278 here that anyone can work on without further input from rms. | 291 here that anyone can work on without further input from rms. |
279 | 292 |
280 | 293 |
281 Maybe some relevant comments here? | 294 Maybe some relevant comments here? |
282 <http://groups.google.com/group/linux.debian.legal/browse_thread/thread/123547ea95437a1f> | 295 <http://groups.google.com/group/linux.debian.legal/browse_thread/thread/123547ea95437a1f> |
283 | |
284 | |
285 All non-trivial README (and other such files) need copyright and | |
286 license statements. Use GPL in most cases, rather than the short | |
287 notices we have been using till now. NB but see above for some | |
288 exceptions in etc/ that should stay unchanged. | |
289 rms: "If a README file is under 60 lines long, using the long version | |
290 [of the GPL notice] might be ugly. Please tell me if you encounter one | |
291 that is under 60 lines." | |
292 | |
293 lisp/term/README (ChangeLog.3 suggests was written by Eric Raymond) | |
294 borderline "trivial" cases | |
295 | 296 |
296 | 297 |
297 etc/gnus-logo.eps, gnus-booklet.ps, gnus-refcard.ps | 298 etc/gnus-logo.eps, gnus-booklet.ps, gnus-refcard.ps |
298 just to be safe, papers are on the way for the "Gnus logo", even | 299 just to be safe, papers are on the way for the "Gnus logo", even |
299 though it is very similar to the already-assigned "Emacs logo". | 300 though it is very similar to the already-assigned "Emacs logo". |