diff options
| author | Glenn Morris | 2007-02-11 03:33:04 +0000 |
|---|---|---|
| committer | Glenn Morris | 2007-02-11 03:33:04 +0000 |
| commit | cf164db26630ec83719b6e9fa5e8dadf8a39b444 (patch) | |
| tree | b5ecc64e284675984e0b36f1ce2658f0f79ac0ee /admin | |
| parent | c14dd816ad23cbb544f561f104124b424db3c736 (diff) | |
| download | emacs-cf164db26630ec83719b6e9fa5e8dadf8a39b444.tar.gz emacs-cf164db26630ec83719b6e9fa5e8dadf8a39b444.zip | |
*** empty log message ***
Diffstat (limited to 'admin')
| -rw-r--r-- | admin/notes/copyright | 27 |
1 files changed, 27 insertions, 0 deletions
diff --git a/admin/notes/copyright b/admin/notes/copyright index 1aa354f03ac..1f536595f13 100644 --- a/admin/notes/copyright +++ b/admin/notes/copyright | |||
| @@ -25,6 +25,30 @@ a file is auto-generated (eg ldefs-boot.el) from another one in the | |||
| 25 | CVS, then it does not really matter about adding a copyright statement | 25 | CVS, then it does not really matter about adding a copyright statement |
| 26 | to the generated file. | 26 | to the generated file. |
| 27 | 27 | ||
| 28 | However, here is a quote from Matt Norwood (Software Freedom Law | ||
| 29 | Center) that suggests we should revise the above policy about trivial | ||
| 30 | files: | ||
| 31 | |||
| 32 | If FSF has a strong policy reason notices off of files it | ||
| 33 | considers "trivial", this will take a lot more bookkeeping; it | ||
| 34 | also runs the risk of these "trivial" files later growing into | ||
| 35 | non-trivial files, and being in the tree without any record of | ||
| 36 | authorship. All in all, I think it's a better policy to attach the | ||
| 37 | notice and let future authors decide if something is trivial when | ||
| 38 | they want to reuse it elsewhere. | ||
| 39 | [...] | ||
| 40 | In general, copyright law will step back and look at the overall "work" | ||
| 41 | consisting of all the assembled components working together as a system; | ||
| 42 | it will apply protection and permissions to this system, not to its | ||
| 43 | subcomponents. If parts of it are recombined into another system, it | ||
| 44 | will consider the protections and permissions for each of the source | ||
| 45 | components only in order to assess the overall status of the work again. | ||
| 46 | The assessment of whether a set of components is entitled to copyright | ||
| 47 | protection is the degree to which they display "creativity": not as | ||
| 48 | atomic units, but as parts of a system working in concert. Thus, several | ||
| 49 | "trivial" components working together in some coherent system might be | ||
| 50 | protectible. | ||
| 51 | |||
| 28 | The years in the copyright notice should be updated every year (see | 52 | The years in the copyright notice should be updated every year (see |
| 29 | file "years" in this directory). The PS versions of refcards etc | 53 | file "years" in this directory). The PS versions of refcards etc |
| 30 | should display copyright notices (an exception to the rule about | 54 | should display copyright notices (an exception to the rule about |
| @@ -290,6 +314,9 @@ src/s/aix3-2.h, bsd386.h, hpux8.h, hpux9.h, irix4-0.h, irix5-0.h, | |||
| 290 | isc2-2.h, netbsd.h, osf1.h, sol2-3.h, sunos4-0.h, umips.h, usg5-4-2.h | 314 | isc2-2.h, netbsd.h, osf1.h, sol2-3.h, sunos4-0.h, umips.h, usg5-4-2.h |
| 291 | - all these (not obviously trivial) files are missing copyrights. | 315 | - all these (not obviously trivial) files are missing copyrights. |
| 292 | rms: "I should talk about these with Matthew Norwood." | 316 | rms: "I should talk about these with Matthew Norwood." |
| 317 | The current legal advice seems to be that we should attach FSF | ||
| 318 | copyright and GPL for the time being, then review post-release. But it | ||
| 319 | is still under discussion. | ||
| 293 | 320 | ||
| 294 | 321 | ||
| 295 | This file is part of GNU Emacs. | 322 | This file is part of GNU Emacs. |