@c For double-sided printing, uncomment:
@c @setchapternewpage odd
@c This date is automagically updated when you save this file:
-@set lastupdate May 7, 2013
+@set lastupdate October 9, 2013
@c %**end of header
@dircategory GNU organization
@cindex down, when GNU machines are
@cindex outage, of GNU machines
-@cindex @url{http://identi.ca/group/fsfstatus}
+@cindex @url{https://pumprock.net/fsfstatus}
If you find that any GNU computer systems (@code{fencepost.gnu.org},
@code{ftp.gnu.org}, @code{www.gnu.org}, @code{savannah.gnu.org},
@dots{}) seem to be down, you can check the current status at
-@url{http://identi.ca/group/fsfstatus}. Most likely the problem, if
+@url{http://pumprock.net/fsfstatus}. Most likely the problem, if
it can be alleviated at the FSF end, is already being worked on.
@cindex sysadmin, FSF
@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.
-@strong{Before} incorporating significant changes, make sure that the
+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.
+
+@emph{Before} 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
electronic (usually PDF) copy of the assignment. This, or whatever
response is required, should happen within five business days of the
initial request. If no reply from the FSF comes after that time,
-please send a reminder. If you still get no response after an
+please send a reminder. If there is still no response after an
additional week, please write to @email{maintainers@@gnu.org} about it.
-After receiving the necessary form, all contributors then print it and
-sign it. Contributors located in the USA or Germany can then email or
-fax a scanned copy back to the FSF (or use postal mail, if they
-prefer). Contributors residing outside the USA or Germany must mail
-the signed form to the FSF via postal mail. To emphasize, the
-necessary distinction is between residents and non-residents of these
-countries; citizenship does not matter.
+After receiving the necessary form, the contributor needs to sign it.
+Contributors residing in the USA may use GPG in order to sign their
+assignment. Contributors located in the USA or Germany can print,
+sign, and then email (or fax) a scanned copy back to the FSF.
+(Specific instructions for both cases are sent with the assignment
+form.) They may use postal mail, if they prefer. Contributors
+residing outside the USA or Germany must mail the signed form to the
+FSF via postal mail. To emphasize, the necessary distinction is
+between residents and non-residents of these countries; citizenship
+does not matter.
For less common cases, we have template files you should send to the
contributor. Be sure to fill in the name of the person and the name
@item
In the @samp{My Account Conf} page on @code{savannah}, upload the GPG
-key you will use to sign your packages. If you haven't created one
-before, you can do so with the command @code{gpg --gen-key} (you can
-accept and/or confirm the default answers to its questions).
+key (in ASCII-armored format) that you will use to sign your packages.
+If you haven't created one before, you can do so with the command
+@code{gpg --gen-key} (you can accept and/or confirm the default
+answers to its questions). Then, to get the ASCII-armored version,
+run @samp{gpg --export --armor @var{your_key_id}}.
Optional but recommended: Send your key to a GPG public key server:
@code{gpg --keyserver keys.gnupg.net --send-keys @var{keyid}}, where
preferred email address, and your Savannah username.
@item
-An ASCII armored copy of your GPG key, as an attachment. (@samp{gpg
---export -a @var{your_key_id} >mykey.asc} should give you this.)
+The ASCII armored copy of your GPG key, as an attachment.
@item
A list of names and preferred email addresses of other individuals you
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
@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
Please don't host discussions about your package in a service that
requires nonfree software. For instance, Google+ ``communities''
-require running a nonfree Javascript program to post a message, so
+require running a nonfree JavaScript program to post a message, so
they can't be used in the Free World. To host discussions there would
be excluding people who live by free software principles.
We don't recommend any specific payment service. However, GNU
developers should not use a service that requires them to sign a
proprietary software license, such as Google's payment service.
+Please also avoid sites that requires users to run nonfree software in
+order to donate. (This includes JavaScript software, so try it with
+LibreJS or with JavaScript disabled.)
+
+In the text you post on the site, please pay attention to the
+terminological issues we care about (@pxref{Terminology}).
+
+We have no objections to using Bitcoin to receive donations.
The FSF can collect donations for a limited number of projects; if you
want to propose that for your project, write to
projects / gnulib.git / blobdiff