unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jean Louis <bugs@gnu.support>
To: Glenn Morris <rgm@gnu.org>
Cc: 37267@debbugs.gnu.org
Subject: bug#37267: 27.0.50; Menus About GNU and GNU and Freedom to be made offline
Date: Tue, 3 Sep 2019 06:56:18 +0200	[thread overview]
Message-ID: <20190903045618.GA20783@protected.rcdrun.com> (raw)
In-Reply-To: <o0ef0y9sdw.fsf@fencepost.gnu.org>

* Glenn Morris <rgm@gnu.org> [2019-09-03 01:43]:
> 
> We made the opposite decision 5+ years ago, ref eg 00156f9549.

Sure somebody made such decision in past. Is that to keep up with the
ever changing online page?

I think that Emacs version is changing more often then the referenced
pages. And I am thinking for dissemination of the message that is
referenced by those URLs, in fact I am worried for that, as I know
from first hand that so many students do not have access to
Internet. At least not always and not from every computer. I also know
they use Emacs from relation with some of those students in East
Africa. Speaking just out of personal experience.

I can see that those files were removed out of the offline
distribution:

* etc/CENSORSHIP, etc/GNU, etc/LINUX-GNU, etc/THE-GNU-PROJECT, etc/WHY-FREE:

This happened, so it seems to me, out of the idea that everybody has
Internet.

It would be more beneficial would it stay in the distribution, and
that menus are offline available.

Or that menus would point to online links only when there is Internet
available, that could be double option.

Files like GNU-PROJECT and those others, they need not be Emacs
specific to be with the Emacs, there is nothing wrong it it. It is
spreading free software idea.

Does the removal of those files point to some statistics that files
were not contributive to free software idea? I remember myself reading
similar files in /etc back in 1999 and "getting the idea", and I did
not find it on Internet neither looked for it on Internet.

Think about what is beneficial to spread the message of free software.

Even if you made decision in past, you can still make new decision in
present.

Jean





  reply	other threads:[~2019-09-03  4:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-02  6:12 bug#37267: 27.0.50; Menus "About GNU" and "GNU and Freedom" to be made offline Jean Louis
2019-09-02 23:43 ` Glenn Morris
2019-09-03  4:56   ` Jean Louis [this message]
2019-09-03  5:35 ` Richard Stallman
2019-09-03  6:01   ` bug#37267: 27.0.50; Menus About GNU and GNU and Freedom " Jean Louis
2019-09-13 12:26   ` bug#37267: 27.0.50; Menus "About GNU" and "GNU and Freedom" " Stefan Kangas
2019-09-17  1:17     ` Glenn Morris
2019-09-17  5:30       ` bug#37267: 27.0.50; Menus About GNU and GNU and Freedom " Jean Louis
2019-09-17  6:27       ` bug#37267: 27.0.50; Menus "About GNU" and "GNU and Freedom" " Richard Stallman
2022-02-10  7:41       ` Lars Ingebrigtsen
2022-02-10  8:52         ` Jean Louis
2022-02-12  3:57           ` 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=20190903045618.GA20783@protected.rcdrun.com \
    --to=bugs@gnu.support \
    --cc=37267@debbugs.gnu.org \
    --cc=rgm@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).