unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Leake <stephen_leake@stephe-leake.org>
To: emacs-devel@gnu.org
Subject: Re: bug#19299: 25.0.50; "Contributing" button in *About GNU Emacs* no longer works
Date: Wed, 10 Dec 2014 11:15:06 -0600	[thread overview]
Message-ID: <85sign5sv9.fsf@stephe-leake.org> (raw)
In-Reply-To: <E1XyjyM-0003Wa-5k@fencepost.gnu.org> (Richard Stallman's message of "Wed, 10 Dec 2014 11:18:42 -0500")

Richard Stallman <rms@gnu.org> writes:

> [[[ To any NSA and FBI agents reading my email: please consider    ]]]
> [[[ whether defending the US Constitution against all enemies,     ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>
>   > You mean, we shouldn't be concerned that this information will not be
>   > available to users of a popular platform?
>
> I don't know exactly what practical question is at issue here,

The issue is the "contributing" link from the Emacs Help | About Emacs
buffer.

In 24.4, that link brings up the file etc/CONTRIBUTE, which is installed
by the Emacs binary install.

We've moved .../etc/CONTRIBUTE to .../CONTRIBUTE, on the theory that
this would make it more visible, forgetting about the About page.

We've also put developer information in there, forgetting about the
original intent of the file (which was to encourage users to contribute
bug reports and patches to Emacs).

In order to resolve these issues, I proposed moving the non-developer
information into the Emacs manual (info "(emacs)Contributing"), and
changing the link on the About page to point to that.

I then asked whether we could rely on the Emacs manual being installed,
and someone pointed out that on Debian (and possibly derived
distributions), it takes extra user steps to install the Emacs manual,
due to the free/non-free policy issue. 


However, I now see that one of the other links in About already points
to the manual: Ordering Manuals

So we could just follow that precedent.


-- 
-- Stephe



  reply	other threads:[~2014-12-10 17:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <21636.57684.129193.880930@a1i15.kph.uni-mainz.de>
     [not found] ` <l7egsaulbz.fsf@fencepost.gnu.org>
2014-12-09  0:06   ` bug#19299: 25.0.50; "Contributing" button in *About GNU Emacs* no longer works Stephen Leake
     [not found]   ` <slsigpq0hz.fsf@fencepost.gnu.org>
2014-12-09  0:12     ` Stephen Leake
2014-12-09  0:21       ` Alexis
2014-12-09  4:43         ` Glenn Morris
2014-12-09  8:37           ` Stephen Leake
2014-12-09 16:22           ` Eli Zaretskii
2014-12-09 17:55             ` Glenn Morris
2014-12-09 18:12               ` Eli Zaretskii
2014-12-10  9:34                 ` Stephen Leake
2014-12-10 16:18             ` Richard Stallman
2014-12-10 17:15               ` Stephen Leake [this message]
2014-12-15  8:39                 ` Richard Stallman

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=85sign5sv9.fsf@stephe-leake.org \
    --to=stephen_leake@stephe-leake.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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).