unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Dave Love <fx@gnu.org>
Cc: 28946@debbugs.gnu.org
Subject: bug#28946: licence problem with cufflinks
Date: Sun, 22 Oct 2017 23:39:11 +0200	[thread overview]
Message-ID: <87sheauakg.fsf@elephly.net> (raw)
In-Reply-To: <87y3o3i0px.fsf@albion.it.manchester.ac.uk>


Hi Dave,

> I noticed that there's a package for cufflinks, but it has a non-free
> component.  It isn't packaged for Debian or Fedora because of that.  See
> <https://github.com/cole-trapnell-lab/cufflinks/issues/16>.

Thank you for the information! I’m going to investigate this.

I downloaded an original release of C locfit from

    http://web.archive.org/web/20070616194305/http://cm.bell-labs.com/cm/ms/departments/sia/project/locfit/dist/locfit.tgz

and compared it to the copy in the Cufflinks repository at commit
d402b182fabd9a831ccb4173e3cb3a2d2dd2e75e (May 2011).

After copying a couple of files from src-c to src they do seem rather
similar, but with about a thousand lines worth of differences (excluding
whitespace changes).  However, it doesn’t look like the code is based on
any of the GPL versions on CRAN[1], because the archives there do not
contain certain files (such as “ar_funs.c”).

If we could be reasonably sure that the code is a derivative of the
GPL’d locfit code from CRAN we essentially deal with a GPL violation,
and not a case of non-free software.

I’ll review this problem and will remove cufflinks by the end of this if
we come to the conclusion that it cannot be considered free.

[1]: https://cran.r-project.org/src/contrib/Archive/locfit/

--
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

  reply	other threads:[~2017-10-22 21:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-22 16:52 bug#28946: licence problem with cufflinks Dave Love
2017-10-22 21:39 ` Ricardo Wurmus [this message]
2017-10-24  7:10   ` Ricardo Wurmus
2017-10-24 10:03     ` Dave Love
2017-10-31  7:19       ` Ricardo Wurmus

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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sheauakg.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=28946@debbugs.gnu.org \
    --cc=fx@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/guix.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).