unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jackson Hamilton <jackson@jacksonrayhamilton.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Requesting review before pushing patch to ELPA
Date: Wed, 4 Feb 2015 01:32:53 -0800	[thread overview]
Message-ID: <CAGiE8AytOkaMoz=0BgAurzph+susyeQc4ev9jeLk-_r=aJ_ntw@mail.gmail.com> (raw)
In-Reply-To: <jwvlhkehont.fsf-monnier+emacs@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1732 bytes --]

There are a whole bunch of people who claim copyright on those files; their
names are listed in the files' headers. I'll note that when I requested
copyright assignment, I alerted the clerk that I was using these libraries.
The plugin doesn't work without them.

I could probably externalize those files into an "npm" package and instruct
users to install a separate executable to run the JavaScript portion of the
plugin. But I'd much rather just include them in the package, because then
it "works out-of-the-box".

As for ert-async, what would be our course of action if he does not agree?
Will we add a copyright exception, or will I not be able to include the
file in the repo?

On Tue, Feb 3, 2015 at 9:51 AM, Stefan Monnier <monnier@iro.umontreal.ca>
wrote:

> > On the "Copyright (C) 2014 Johan Andersson", are you suggesting I change
> > the copyright notice in ert-async.el myself, or that I should contact the
> > author and tell him to change it?
>
> Asking him is the right way.  The question to ask is whether he wants to
> contribute this code to Emacs and/or GNU ELPA: if he does, then that
> means his copyright assignment does cover this file and so that means
> that the "Copyright (C) 2014 Johan Andersson" should be changed to
> "Copyright (C) 2014 Free Software Foundation, Inc".
>
> Of course, you want to keep his name as an "Author:" and/or "Maintainer:".
>
> > context-coloring/languages/javascript/libraries/ also includes 3
> JavaScript
> > libraries with their own copyright notices.  These appear to be licensed
> > under the FreeBSD license.  Should they be handled specially?
>
> The problem is not just the license but the copyright.  Who owns the
> copyright to those files?
>
>
>         Stefan
>

[-- Attachment #2: Type: text/html, Size: 2339 bytes --]

  reply	other threads:[~2015-02-04  9:32 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-02  7:49 Requesting review before pushing patch to ELPA Jackson Hamilton
2015-02-02 17:58 ` Stefan Monnier
2015-02-03  5:57   ` Jackson Hamilton
2015-02-03 12:13     ` Artur Malabarba
2015-02-04  9:24       ` Jackson Hamilton
2015-02-04 11:15         ` Artur Malabarba
2015-02-04 11:16           ` Artur Malabarba
2015-02-03 17:51     ` Stefan Monnier
2015-02-04  9:32       ` Jackson Hamilton [this message]
2015-02-04 15:14         ` Stefan Monnier
2015-02-04 19:46           ` Jackson Hamilton
2015-02-04 19:48             ` Dmitry Gutov
2015-02-04 21:58             ` Stefan Monnier
2015-02-05  8:05               ` Jackson Hamilton
2015-02-05 14:10                 ` Stefan Monnier
2015-02-05 18:17                   ` Jackson Hamilton
2015-02-05 18:39                     ` Matthew Carter
2015-02-05 18:48                     ` Jackson Hamilton
2015-02-05 20:22                     ` Stefan Monnier
2015-02-04 15:13 ` Stefan Monnier

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='CAGiE8AytOkaMoz=0BgAurzph+susyeQc4ev9jeLk-_r=aJ_ntw@mail.gmail.com' \
    --to=jackson@jacksonrayhamilton.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).