unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: wsdl test files and licensing
Date: Wed, 12 Nov 2014 13:47:55 +0100	[thread overview]
Message-ID: <87oascr3es.fsf@fencepost.gnu.org> (raw)
In-Reply-To: 87oasc62mu.fsf@gmx.de

Michael Albinus <michael.albinus@gmx.de> writes:

> the soap-client people have written a test suite shich is obviously
> useful. I would like to merge it into Emacs. This will take time,
> because before this happens it shall use ert for running the
> tests. But that's another story.
>
> As test data, there are several *.wsdl files as well as soap request
> examples (these are *.xml files). All of them are not licensed, except
> Debbugs.wsdl taken from the GNU ELPA debbugs package.

What does "are not licensed" mean?  If it means "there is no license to
distribute them", obviously we cannot distribute them.  That's a
no-brainer.

> Would it be necessary to bring all those files under GPLv3? As said, I
> regard them as test data.

If we distribute them as part of Emacs, the standard threshold is
"copyright assignment to FSF".  The FSF will then generally distribute
under GPLv3 or later, but that may change at some time subject to the
constraints spelled out in the copyright assignment contract.

Outside of a copyright assignment, stuff becomes more complex and
requires separate ok/go-ahead from Richard and/or the FSF copyright
clerk.  Off the cuff I'll be pretty sure that GPLv3 only won't cut it,
something like X11 license (or BSD without advertising clause) might
work, GPLv3+ might barely work.  But it's up to an individual decision
by Richard/copyright clerk whether a particular licensing of
non-assigned software can be accepted into the Emacs distribution.

For test data, it might be possible (if one cannot get the copyright
holders to sign a copyright assignment) to get a long with a copyright
disclaimer where the copyright holder will disclaim all copyright
interest in the respective files.  Again, this needs individual approval
by Richard/clerk.

-- 
David Kastrup




  reply	other threads:[~2014-11-12 12:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-12 12:10 wsdl test files and licensing Michael Albinus
2014-11-12 12:47 ` David Kastrup [this message]
2014-11-12 13:42   ` Tassilo Horn
2014-11-12 13:45   ` Alex Harsanyi
2014-11-12 14:07     ` David Kastrup
2014-11-12 14:42       ` Michael Albinus
2014-11-12 14:50         ` David Kastrup
2014-11-12 15:05           ` Michael Albinus
2014-11-12 23:58             ` Alex Harsanyi
2014-11-13 14:34               ` Michael Albinus
2014-11-12 14:20 ` Stefan Monnier
2014-11-12 14:50   ` Stephen J. Turnbull

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=87oascr3es.fsf@fencepost.gnu.org \
    --to=dak@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).