all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Thien-Thi Nguyen <ttn@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: Volunteering for Emacs documentation
Date: Sat, 18 Apr 2015 10:36:46 +0200	[thread overview]
Message-ID: <87d231estd.fsf@zigzag.favinet> (raw)
In-Reply-To: <83wq1b8b5c.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 17 Apr 2015 10:30:23 +0300")

[-- Attachment #1: Type: text/plain, Size: 1076 bytes --]

() Eli Zaretskii <eliz@gnu.org>
() Fri, 17 Apr 2015 10:30:23 +0300

   Yet another way is to read the discussions which indicate
   that some piece of documentation needs to be improved, and do
   that.

Very true!  Don't forget that for many people, an important
piece of the document is its index.  IMHO improving a document's
index is qualitatively different enough to warrant mentioning as
a task on its own.  Bonus: it's easy to do and often does not
trigger copyright assignment hair at the onset...

(I have recently begun reading a lot of non-GNU documentation
and appreciate all the more Emacs' well-indexed manuals -- some
of the stuff i'm reading has no index at all!  [Insert grumbling
about blithe abdication of control to the panopticon here.])

-- 
Thien-Thi Nguyen -----------------------------------------------
  (if you're human and you know it) read my lisp:
    (defun responsep (type via)
      (case type
        (technical (eq 'mailing-list via))
        ...))
---------------------------------------------- GPG key: 4C807502

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

      parent reply	other threads:[~2015-04-18  8:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-17  7:15 Volunteering for Emacs documentation Gian Uberto Lauri
2015-04-17  7:30 ` Eli Zaretskii
2015-04-17  8:20   ` Gian Uberto Lauri
2015-04-17 11:07     ` Daniel Pimentel
2015-04-17 12:37       ` Eli Zaretskii
2015-04-18  8:36   ` Thien-Thi Nguyen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d231estd.fsf@zigzag.favinet \
    --to=ttn@gnu.org \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.