comparison admin/notes/copyright @ 76330:de5af7fb87a1

*** empty log message ***
author Glenn Morris <rgm@gnu.org>
date Mon, 05 Mar 2007 08:01:01 +0000
parents 97ef6489b67a
children 24f9e7213c62
comparison
equal deleted inserted replaced
76329:97ef6489b67a 76330:de5af7fb87a1
14 14
15 15
16 Summary for the impatient: 16 Summary for the impatient:
17 17
18 1. Don't add code to Emacs written by someone other than yourself 18 1. Don't add code to Emacs written by someone other than yourself
19 without thinking about the legal aspect (make sure they have an 19 without thinking about the legal aspect. Even if the changes are
20 assignment, if adding a file adjust the copyright statements in the 20 trivial, consider if they combine with previous changes by the same
21 file). NB the ChangeLog entry should be in the name of the author of 21 author to make a non-trivial total. If so, make sure they have an
22 the code, not the person who installs it. 22 assignment. If adding a whole file adjust the copyright statements in
23 23 the file.
24 2. When installing code written by someone else, I think it is helpful 24
25 to: i) put the name of the author in the cvs log (as well as the 25 2. When installing code written by someone else, the ChangeLog entry
26 ChangeLog); and ii) not check-in any of your own changes to the same 26 should be in the name of the author of the code, not the person who
27 file in the same commit. 27 installs it. I think it is helpful to put the author (if not yourself)
28 in the CVS log as well; and to not install any of your own changes in
29 the same commit.
28 30
29 3. With images, add the legal info to a README file in the directory 31 3. With images, add the legal info to a README file in the directory
30 containing the image. 32 containing the image.
31 33
32 4. If you add a lot of text to a previously trivial file that had no 34 4. If you add a lot of text to a previously trivial file that had no