Mercurial > emacs
changeset 76329:97ef6489b67a
*** empty log message ***
| author | Glenn Morris <rgm@gnu.org> |
|---|---|
| date | Mon, 05 Mar 2007 07:50:52 +0000 |
| parents | ba37b237dffb |
| children | de5af7fb87a1 |
| files | admin/notes/copyright |
| diffstat | 1 files changed, 12 insertions(+), 7 deletions(-) [+] |
line wrap: on
line diff
--- a/admin/notes/copyright Mon Mar 05 07:00:16 2007 +0000 +++ b/admin/notes/copyright Mon Mar 05 07:50:52 2007 +0000 @@ -15,19 +15,24 @@ Summary for the impatient: -1. Don't add a file to Emacs written by someone other than yourself +1. Don't add code to Emacs written by someone other than yourself without thinking about the legal aspect (make sure they have an -assignment, adjust the copyright statements in the file). NB the -ChangeLog entry should be in the name of the author of the code, not -the person who installs it. +assignment, if adding a file adjust the copyright statements in the +file). NB the ChangeLog entry should be in the name of the author of +the code, not the person who installs it. -2. With images, add the legal info to a README file in the directory +2. When installing code written by someone else, I think it is helpful +to: i) put the name of the author in the cvs log (as well as the +ChangeLog); and ii) not check-in any of your own changes to the same +file in the same commit. + +3. With images, add the legal info to a README file in the directory containing the image. -3. If you add a lot of text to a previously trivial file that had no +4. If you add a lot of text to a previously trivial file that had no legal notices, consider if you should add a copyright statement. -4. Please don't just add an FSF copyright without checking that is the +5. Please don't just add an FSF copyright without checking that is the right thing to do.