From: tomas@tuxteam.de (Tomas Zerolo)
Cc: Christian.Vogler@gallaudet.edu, Tomas Zerolo <tomas@tuxteam.de>,
emacs-devel@gnu.org
Subject: Re: lua mode
Date: Tue, 27 Sep 2005 09:51:16 +0200 [thread overview]
Message-ID: <20050927075116.GA2593@www.trapp.net> (raw)
In-Reply-To: <85br2fc6y8.fsf@lola.goethe.zz>
[-- Attachment #1.1: Type: text/plain, Size: 1886 bytes --]
Thanks, David for your comments.
On Tue, Sep 27, 2005 at 09:20:47AM +0200, David Kastrup wrote:
> tomas@tuxteam.de (Tomas Zerolo) writes:
>
> > I'm an user of Lua mode, written by Christian Vogler et
> > al. [...]
> You have to be aware that the package in the CVS will be distributed
> as part of Emacs, and thus it has to be under the GPL, and every
> contributor needs to have his copyright assigned to the FSF.
Yes, I am aware of that. Christian has already stated that it is OK with
him to sign papers. If there is interest in integrating lua-mode into
Emacs, I'd try to reach the other distributors mentioned in the
copyright notice and try to find out whether there are other,
unmentioned.
> XEmacs
> development headquarters in general does not bother about assignments
> too much. That means that if you have XEmacs-only contributors, they
> can't work even on the XEmacs parts of LUA-mode without assigning
> copyright to the FSF, and some XEmacs contributors/developers would
> rather refrain than do that (some prefer XEmacs for exactly that
> reason). So that's the downpoint.
I see. I'll write to the (known) contributors (the package is not that
large, so it seems very probable they are all).
> With regard to XEmacs support: the current maintainer of the mode (in
> this case, you) decides about the policies. That would mean it would
> be basically your responsibility to make reasonably sure the stuff
> continues working under XEmacs in case other Emacs developers make
> additions and fixes.
Yes, I'd try to do that.
> If you pass on maintainership at some point of
> time, finding an XEmacs-aware successor might be more difficult with
> the mode being maintained as part of Emacs.
Yes, I see the point.
Thanks
-- tomás
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 142 bytes --]
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2005-09-27 7:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-27 5:41 lua mode Tomas Zerolo
2005-09-27 7:20 ` David Kastrup
2005-09-27 7:51 ` Tomas Zerolo [this message]
2005-09-27 16:09 ` Stefan Monnier
2005-09-27 21:58 ` Richard M. Stallman
2005-09-28 0:23 ` Christian Vogler
2005-09-28 2:13 ` Daniel Brockman
2005-09-28 0:39 ` Christian Vogler
2005-09-29 2:42 ` Richard M. Stallman
2005-09-28 4:35 ` Tomas Zerolo
-- strict thread matches above, loose matches on Subject: below --
2008-01-04 23:56 Lua mode Miles Bader
2008-01-05 1:41 ` Glenn Morris
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=20050927075116.GA2593@www.trapp.net \
--to=tomas@tuxteam.de \
--cc=Christian.Vogler@gallaudet.edu \
--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.