From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [gnu.org #194297] Re: Emacs-devel list IS slow
Date: Wed, 02 Jun 2004 13:37:01 -0400 [thread overview]
Message-ID: <E1BVZfh-0006VV-7S@fencepost.gnu.org> (raw)
In-Reply-To: <874qpvgfpd.fsf@mail.jurta.org> (message from Juri Linkov on Tue, 01 Jun 2004 23:57:29 +0300)
> | Emacs: The Sacred Editor
> | Category: Computers > Open Source > Software > Editors > Emacs
This is another flaw in Google categorization: Emacs is placed
under Open Source category.
Of all the problems, this one hurts us the worst--but they have surely
done this intentionally, so it is unlikely that they would change it
for us.
It makes no sense to ask them to make a separate "free software"
category. It is clearly right to have just one category containing
GNU Emacs, Apache, and Linux; splitting it in two would be unhelpful
for the users.
What we would want them to do is to label this one category with "free
software" as well as "open source". I suppose they will say that is
too long.
So people will keep coming to the GNU Project and our software,
thinking that we agree with the open source movement. We therefore
must continue to find frequent opportunities to say "Open source? We
disagree completely with open source!" And as they recognize
that part of what they were told is untrue, we can explain about
free software.
next prev parent reply other threads:[~2004-06-02 17:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <rt-194297@gnu.org>
2004-05-29 17:49 ` [gnu.org #194297] Re: Emacs-devel list IS slow Paul Fisher via RT
2004-05-30 6:03 ` Eli Zaretskii
2004-05-30 23:05 ` Kim F. Storm
2004-05-30 23:12 ` Kim F. Storm
2004-05-31 13:44 ` Juri Linkov
2004-06-01 14:57 ` Richard Stallman
2004-06-01 16:40 ` Lawrence Mitchell
2004-06-01 20:57 ` Juri Linkov
2004-06-02 17:37 ` Richard Stallman [this message]
2004-05-30 5:02 ` eliz via RT
2004-05-30 23:07 ` (Kim F. Storm) via RT
2004-05-30 23:13 ` (Kim F. Storm) via RT
2004-05-30 23:31 ` Paul Fisher via RT
2004-05-31 6:40 ` Eli Zaretskii
2004-05-31 5:39 ` eliz via RT
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=E1BVZfh-0006VV-7S@fencepost.gnu.org \
--to=rms@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 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).