unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
Cc: Richard Stallman <rms@gnu.org>, emacs-devel@gnu.org
Subject: Re: Pages of the Tramp package.
Date: 15 Apr 2004 21:33:24 +0200	[thread overview]
Message-ID: <x54qrlyr23.fsf@lola.goethe.zz> (raw)
In-Reply-To: <nqllkxm5cm.fsf@alcatel.de>

Michael Albinus <Michael.Albinus@alcatel.de> writes:

> Richard Stallman <rms@gnu.org> writes:
> 
> >     > Maybe the Tramp web pages should go into the Emacs web pages.
> >
> >     I don't believe so. Tramp exists outside Emacs 21.3.50 as well, for
> >     older Emacsen and for XEmacs.
> >
> > I see no connection between that and the issue.
> 
> The Tramp web pages contain parts which might be not desirable in
> the Emacs web:
> 
> - There is a chapter about Tramp installation. Not needed if Tramp
>   is inside Emacs; therefore this chapter is discarded when
>   tramp.texi is uploaded to Emacs CVS.

That explains why tramp has its own CVS apart from what is in Emacs.

> - Tramp has different syntax for Emacs and XEmacs. I don't like it,
>   but that's the status. Therefore, there are TWO web pages for
>   Tramp, each linked to the other.

Two _web_ pages or two _info_ pages?

> I guess both reasons make it reasonable to have Tramp web pages
> outside Emacs.

There is nothing to be said against having Tramp web pages out of
Emacs.  Since tramp is integrated with Emacs, one should also take a
look at how to integrate documentation to it.  But as long as tramp
is also a separate project, the focus of interest it has as a
separate project should certainly also be documented separately.

What I was originally asking was why tramp is not a GNU project,
which is surprising when you see it also as a part of Emacs and (c)
FSF.  There would be some valid answers:

a) tramp explicitly condones nonfree software.  I don't see this here
(and nonfree is not the same as non-GNU, or non-GPL).

b) there are parts of tramp that are problematic to be distributed by
the FSF, perhaps related to encryption or something.  But then the
issue is not GNU or non-GNU, but the distribution by the FSF.  If we
have a problem in that area (which I certainly don't hope), nothing
will help except ripping tramp from Emacs and all servers in the
U.S., and have it copyrighted and distributed by someone outside of
U.S.A. and the FSF.

There might be other reasons I overlook.  I just mentioned that it is
surprising for people looking for information about tramp that it
is categorized as non-GNU instead of GNU.  There might be reasons for
this, and it is ok if there are, but maybe it is only a historical
accident.  If that is all that is there, then one could correct it.
If there is more to it, then one can leave things as they are.

I have no clue.  That's why I was asking.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2004-04-15 19:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-10 17:25 Pages of the Tramp package David Kastrup
2004-04-12  3:52 ` Richard Stallman
2004-04-12  4:23   ` David Kastrup
2004-04-13 17:44     ` Richard Stallman
2004-04-14 12:11       ` Michael Albinus
2004-04-14 12:48         ` David Kastrup
2004-04-14 12:59           ` Michael Albinus
2004-04-15 16:45         ` Richard Stallman
2004-04-15 19:03           ` Michael Albinus
2004-04-15 19:33             ` David Kastrup [this message]
2004-04-15 19:57               ` Michael Albinus
2004-04-16 20:25               ` Kai Grossjohann
2004-04-16 21:06                 ` David Kastrup
2004-04-17  7:15             ` 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=x54qrlyr23.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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).