Mercurial > hg > octave-lojdl > gnulib-hg

comparison doc/maintain.texi @ 17454:9b8de09b2e2e

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
autoupdate
author Karl Berry <karl@freefriends.org>
date Fri, 19 Jul 2013 15:08:53 -0700
parents bffc406a6390
children
comparison
equal deleted inserted replaced
17453:d6a1c46258ab 17454:9b8de09b2e2e
3 @setfilename maintain.info 3 @setfilename maintain.info
4 @settitle Information for Maintainers of GNU Software 4 @settitle Information for Maintainers of GNU Software
5 @c For double-sided printing, uncomment: 5 @c For double-sided printing, uncomment:
6 @c @setchapternewpage odd 6 @c @setchapternewpage odd
7 @c This date is automagically updated when you save this file: 7 @c This date is automagically updated when you save this file:
8 @set lastupdate May 7, 2013 8 @set lastupdate July 19, 2013
9 @c %**end of header 9 @c %**end of header
10 10
11 @dircategory GNU organization 11 @dircategory GNU organization
12 @direntry 12 @direntry
13 * Maintaining: (maintain). Maintaining GNU software. 13 * Maintaining: (maintain). Maintaining GNU software.
1521 maintain the web pages at @url{http://www.gnu.org} for your project 1521 maintain the web pages at @url{http://www.gnu.org} for your project
1522 (@pxref{Web Pages}). 1522 (@pxref{Web Pages}).
1523 1523
1524 @item 1524 @item
1525 In the @samp{My Account Conf} page on @code{savannah}, upload the GPG 1525 In the @samp{My Account Conf} page on @code{savannah}, upload the GPG
1526 key you will use to sign your packages. If you haven't created one 1526 key (in ASCII-armored format) that you will use to sign your packages.
1527 before, you can do so with the command @code{gpg --gen-key} (you can 1527 If you haven't created one before, you can do so with the command
1528 accept and/or confirm the default answers to its questions). 1528 @code{gpg --gen-key} (you can accept and/or confirm the default
1529 answers to its questions). Then, to get the ASCII-armored version,
1530 run @samp{gpg --export --armor @var{your_key_id}}.
1529 1531
1530 Optional but recommended: Send your key to a GPG public key server: 1532 Optional but recommended: Send your key to a GPG public key server:
1531 @code{gpg --keyserver keys.gnupg.net --send-keys @var{keyid}}, where 1533 @code{gpg --keyserver keys.gnupg.net --send-keys @var{keyid}}, where
1532 @var{keyid} is the eight hex digits reported by @code{gpg 1534 @var{keyid} is the eight hex digits reported by @code{gpg
1533 --list-public-keys} on the @code{pub} line before the date. For full 1535 --list-public-keys} on the @code{pub} line before the date. For full
1543 @item 1545 @item
1544 Name of package(s) that you are the maintainer for, your 1546 Name of package(s) that you are the maintainer for, your
1545 preferred email address, and your Savannah username. 1547 preferred email address, and your Savannah username.
1546 1548
1547 @item 1549 @item
1548 An ASCII armored copy of your GPG key, as an attachment. (@samp{gpg 1550 The ASCII armored copy of your GPG key, as an attachment.
1549 --export -a @var{your_key_id} >mykey.asc} should give you this.)
1550 1551
1551 @item 1552 @item
1552 A list of names and preferred email addresses of other individuals you 1553 A list of names and preferred email addresses of other individuals you
1553 authorize to make releases for which packages, if any (in the case that you 1554 authorize to make releases for which packages, if any (in the case that you
1554 don't make all releases yourself). 1555 don't make all releases yourself).
2292 serious about the need for free documentation, we must not contradict 2293 serious about the need for free documentation, we must not contradict
2293 our position by recommending use of documentation that isn't free. 2294 our position by recommending use of documentation that isn't free.
2294 2295
2295 Please don't host discussions about your package in a service that 2296 Please don't host discussions about your package in a service that
2296 requires nonfree software. For instance, Google+ ``communities'' 2297 requires nonfree software. For instance, Google+ ``communities''
2297 require running a nonfree Javascript program to post a message, so 2298 require running a nonfree JavaScript program to post a message, so
2298 they can't be used in the Free World. To host discussions there would 2299 they can't be used in the Free World. To host discussions there would
2299 be excluding people who live by free software principles. 2300 be excluding people who live by free software principles.
2300 2301
2301 Of course, you can't order people not to use such services to talk 2302 Of course, you can't order people not to use such services to talk
2302 with each other. What you can do is not legitimize them, and use your 2303 with each other. What you can do is not legitimize them, and use your
2552 @end smallexample 2553 @end smallexample
2553 2554
2554 We don't recommend any specific payment service. However, GNU 2555 We don't recommend any specific payment service. However, GNU
2555 developers should not use a service that requires them to sign a 2556 developers should not use a service that requires them to sign a
2556 proprietary software license, such as Google's payment service. 2557 proprietary software license, such as Google's payment service.
2558 Please also avoid sites that requires users to run nonfree software in
2559 order to donate. (This includes JavaScript software, so try it with
2560 LibreJS or with JavaScript disabled.)
2561
2562 In the text you post on the site, please pay attention to the
2563 terminological issues we care about (@pxref{Terminology}).
2564
2565 We have no objections to using Bitcoin to receive donations.
2557 2566
2558 The FSF can collect donations for a limited number of projects; if you 2567 The FSF can collect donations for a limited number of projects; if you
2559 want to propose that for your project, write to 2568 want to propose that for your project, write to
2560 @email{maintainers@@gnu.org}. The FSF is required to supervise the 2569 @email{maintainers@@gnu.org}. The FSF is required to supervise the
2561 spending of these funds. 2570 spending of these funds.