unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Derek Zhou <derek@shannon-data.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Holger Hans Peter Freyther <holger@freyther.de>,
	Paolo Bonzini <bonzini@gnu.org>,
	Wilfred Hughes <me@wilfred.me.uk>, Richard Stallman <rms@gnu.org>,
	emacs-devel@gnu.org
Subject: Re: [ELPA] New package: smalltalk-mode
Date: Tue, 26 Mar 2019 09:05:48 +0800	[thread overview]
Message-ID: <87d0mea1hv.fsf@mail.shannon-data.com> (raw)
In-Reply-To: <83va07lzfp.fsf@gnu.org>


Eli Zaretskii writes:

>> From: Derek Zhou <derek@shannon-data.com>
>> Date: Mon, 25 Mar 2019 22:59:10 +0800
>> 
>> smalltalk-mode is the emacs editing mode for GNU smalltalk. Attached is
>> the version copied verbatim from GNU smalltalk current git HEAD, last
>> commit is:
>> commit 8141da457870e24b0e04684213637b7c4435a2a5
>> Author: Wilfred Hughes <me@wilfred.me.uk>
>> Date:   Wed Nov 29 21:22:34 2017 +0000
>> 
>> GNU smalltalk itself is copyrighted by FSF, so I think it is qualified
>> to be included in the ELPA. If the format need changing please let me
>> know.
>> 
>
> Not sure what this all means from the legal POV.  Lately, Richard
> asked us to make sure people who contribute code to ELPA and have
> copyright assignments for Emacs to say clearly that they contribute
> the code for Emacs, in order for the assignment to be effective.
>
> OTOH, you are saying this is part of GNU Smalltalk, which has separate
> assignments.
>
> On the third hand, I'm not sure who should be the author of the
> commit, should we decide to put this on ELPA.
>
> Richard, can you please advise?
>
> Thanmks.

GNU Smalltalk was maintained by Paolo Bonzini <bonzini@gnu.org> until
around 2012, then he passed the torch to Holger Hans Peter Freyther
<holger@freyther.de>. The smalltalk mode was originally written by Steve
Byrne whose email I cannot find. Various people made changes along the
way, including Paolo. Latest commit to the file was done by Wilfred
Hughes <me@wilfred.me.uk>. I put all 3 people on the CC: list to
comment.

I am not a lawyer, but this code is owned by FSF, just like emacs
itself. I don't see how it can be a legal problem to move changes from
one pocket to the other. All authors already gave up their copyright by
the original assignment. We can ask again and I am pretty sure all
authors will be thrilled to have a broader audience for the free
software they created.

Derek







  parent reply	other threads:[~2019-03-26  1:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-25 14:59 [ELPA] New package: smalltalk-mode Derek Zhou
2019-03-25 15:57 ` Eli Zaretskii
2019-03-25 19:01   ` Stefan Monnier
2019-03-25 19:27   ` Stefan Monnier
2019-03-26  1:05   ` Derek Zhou [this message]
2019-03-26 15:47     ` 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=87d0mea1hv.fsf@mail.shannon-data.com \
    --to=derek@shannon-data.com \
    --cc=bonzini@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=holger@freyther.de \
    --cc=me@wilfred.me.uk \
    --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).