gnustandards-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

gnustandards ChangeLog maintain.texi


From: karl
Subject: gnustandards ChangeLog maintain.texi
Date: Wed, 09 Oct 2013 20:38:23 +0000

CVSROOT:        /sources/gnustandards
Module name:    gnustandards
Changes by:     karl <karl>     13/10/09 20:38:22

Modified files:
        .              : ChangeLog maintain.texi 

Log message:
        GNU packages need not be FSF-copyrighted; explicitly warn that a GPG 
key update must happen in two places

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/gnustandards/ChangeLog?cvsroot=gnustandards&r1=1.184&r2=1.185
http://cvs.savannah.gnu.org/viewcvs/gnustandards/maintain.texi?cvsroot=gnustandards&r1=1.241&r2=1.242

Patches:
Index: ChangeLog
===================================================================
RCS file: /sources/gnustandards/gnustandards/ChangeLog,v
retrieving revision 1.184
retrieving revision 1.185
diff -u -b -r1.184 -r1.185
--- ChangeLog   13 Sep 2013 22:24:23 -0000      1.184
+++ ChangeLog   9 Oct 2013 20:38:22 -0000       1.185
@@ -1,3 +1,13 @@
+2013-10-09  Karl Berry  <address@hidden>
+
+       * maintain.texi (FTP Upload Directive File): reword to avoid
+       underfull hbox.
+
+2013-10-08  Karl Berry  <address@hidden>
+
+       * maintain.texi (Copyright Papers): make clear that GNU packages
+       need not be FSF-copyrighted.
+
 2013-09-13  Karl Berry  <address@hidden>
 
        * make-stds.texi (Directory Variables): new variable runstatedir.

Index: maintain.texi
===================================================================
RCS file: /sources/gnustandards/gnustandards/maintain.texi,v
retrieving revision 1.241
retrieving revision 1.242
diff -u -b -r1.241 -r1.242
--- maintain.texi       13 Sep 2013 22:21:04 -0000      1.241
+++ maintain.texi       9 Oct 2013 20:38:22 -0000       1.242
@@ -5,7 +5,7 @@
 @c For double-sided printing, uncomment:
 @c @setchapternewpage odd
 @c This date is automagically updated when you save this file:
address@hidden lastupdate September 7, 2013
address@hidden lastupdate October 9, 2013
 @c %**end of header
 
 @dircategory GNU organization
@@ -292,13 +292,19 @@
 @cindex assignments, copyright
 @cindex disclaimers
 
-If you maintain an FSF-copyrighted package
-certain legal procedures are required when incorporating legally significant
-changes written by other people.  This ensures that the FSF has the
-legal right to distribute the package, and the standing to defend its
-GPL-covered status in court if necessary.
+If you maintain an FSF-copyrighted package, certain legal procedures
+are required when incorporating legally significant changes written by
+other people.  This ensures that the FSF has the legal right to
+distribute the package, and the standing to defend its GPL-covered
+status in court if necessary.
+
+GNU packages need not be FSF-copyrighted; this is up to the author(s),
+generally at the time the package is dubbed GNU.  When copyright is
+assigned to the FSF, the FSF can act to stop GPL violations about the
+package.  Otherwise, legal actions are up to the author(s).  The rest
+of this section is about the case when a package is FSF-copyrighted.
 
address@hidden incorporating significant changes, make sure that the
address@hidden incorporating significant changes, make sure that the
 person who wrote the changes has signed copyright papers and that the
 Free Software Foundation has received and signed them.  We may also
 need an employer's disclaimer from the person's employer, which
@@ -1569,6 +1575,10 @@
 The upload system will email receipts to the given email addresses
 when an upload is made, either successfully or unsuccessfully.
 
+Should you later have to update your GPG key, you'll have to re-submit
+it to both Savannah and @email{ftp-upload@@gnu.org}, as these systems
+are not connected.
+
 
 @node Automated Upload Procedure
 @subsection Automated Upload Procedure
@@ -1705,8 +1715,9 @@
 @t{comment: let's hope this works!}
 @end table
 
-Putting the above together, the complete contents of the directive
-file @file{foo-1.0.tar.gz.directive} for our example would be:
+Putting all of the above together, the complete contents of the
+directive file @file{foo-1.0.tar.gz.directive} for our example would
+be:
 
 @example
 version: 1.2



reply via email to

[Prev in Thread] Current Thread [Next in Thread]