gnustandards-commit
[Top][All Lists]
Advanced

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

gnustandards maintain.texi


From: karl
Subject: gnustandards maintain.texi
Date: Fri, 19 Jul 2013 22:07:03 +0000

CVSROOT:        /sources/gnustandards
Module name:    gnustandards
Changes by:     karl <karl>     13/07/19 22:07:03

Modified files:
        .              : maintain.texi 

Log message:
        gpg instruction tweaks + typo + JavaScript capitalization

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/gnustandards/maintain.texi?cvsroot=gnustandards&r1=1.238&r2=1.239

Patches:
Index: maintain.texi
===================================================================
RCS file: /sources/gnustandards/gnustandards/maintain.texi,v
retrieving revision 1.238
retrieving revision 1.239
diff -u -b -r1.238 -r1.239
--- maintain.texi       19 Jul 2013 16:05:12 -0000      1.238
+++ maintain.texi       19 Jul 2013 22:07:02 -0000      1.239
@@ -1523,9 +1523,11 @@
 
 @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
address@hidden --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
@@ -1545,8 +1547,7 @@
 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
@@ -2294,7 +2295,7 @@
 
 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.
 
@@ -2555,11 +2556,11 @@
 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.)
+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 (@pref{Terminology}).
+terminological issues we care about (@pxref{Terminology}).
 
 We have no objections to using Bitcoin to receive donations.
 



reply via email to

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