unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Giovanni Biscuolo <g@xelera.eu>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Bioconductor package flowPeaks license Artistic 1.0?
Date: Fri, 20 Dec 2019 11:47:16 +0100	[thread overview]
Message-ID: <CAJ3okZ00MhGfunGJzr2srW0qRc2yqWjoXj6v5dqKNkRbwjWP6w@mail.gmail.com> (raw)
In-Reply-To: <87o8w373d7.fsf@roquette.mug.biscuolo.net>

Hi Giovanni,


On Fri, 20 Dec 2019 at 10:28, Giovanni Biscuolo <g@xelera.eu> wrote:

> zimoun <zimon.toutoune@gmail.com> writes:
>
> [...]
>
> > The issue is really to be able to contact the author. And I am not
> > sure this person is even the copyright holder. (In some country, the
> > company/institute own the copyright even the code is not written in
> > office's hours.)
> >
> >
> > For example, 2 files contains:
>
> [...]
>
> > The most of the files claim:
>
> [...]
>
> > For example, how many packages in Bioconductor use the Artistic 1.0?
>
> Sorry you have to struggle with this tedious work of sorting out YALM
> (Yet Another Licensing Mess), but the first thing to do in this case is
> to have a list of licenses for each file/folder and see if there is a
> way to **workaround** the disappearing of upstream and if needed do some
> sort of _soft_ forking just to fix the missing licensing-bits
>
> If we are lucky enough maybe the 95% of this package is free and the
> remainging 5% easily replaceable with a free rewrite

1.
This is my hope for the package flowPeak. Because it blocks my workflow at work.
Now, this package is in a personal channel but nothing provides a
guarantee that this channel would not disappear so the paper I am
working on would not be easily reproducible (in theory and
principles).
Be in the Guix tree affords more chance.

2.
This fix -- reuse all the free available code and replace the non-free
one -- do not scale.
So the question is: What is the scale we are talking about? How many
packages in Bioconductor?
If it is, say, a couple then it is doable. Or see with the people
managing Bioconductor.
If it is more, then the option is lobbying. :-)




> P.S.: like Tobias, I suggest you not to spend time trying to appeal FSF
> on the Artistic Licence v.1 ;-)

I have used frenchy bad faith rhetoric argument. ;-)

As I said, if a couple on Bioconductor are Artistic 1.0, that's ok.
Otherwise, it is an issue.
Right now, there is too much *if*. :-)


Thanks,
simon

  reply	other threads:[~2019-12-20 10:47 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-24 15:02 Bioconductor package flowPeaks license Artistic 1.0? zimoun
2019-07-24 21:15 ` Ricardo Wurmus
2019-07-25  9:58   ` zimoun
2019-07-25 12:47     ` Ricardo Wurmus
2019-12-19 16:38       ` zimoun
2019-12-19 17:17         ` Ricardo Wurmus
2019-12-19 17:29           ` zimoun
2019-12-19 20:10             ` Ricardo Wurmus
2019-12-19 21:18               ` zimoun
2019-12-19 17:18         ` Tobias Geerinckx-Rice
2019-12-19 17:29           ` Tobias Geerinckx-Rice
2019-12-19 18:04             ` zimoun
2019-12-19 17:56           ` zimoun
2019-12-19 20:24             ` Tobias Geerinckx-Rice
2019-12-19 21:40               ` zimoun
2019-12-20  9:28                 ` Giovanni Biscuolo
2019-12-20 10:47                   ` zimoun [this message]
2019-12-20 14:40                     ` Ricardo Wurmus
2019-12-20 11:55               ` Guix and Bioconductor Giovanni Biscuolo
2019-12-20 14:38                 ` Ricardo Wurmus
2019-12-21 10:06                   ` [OT] " Giovanni Biscuolo
2019-12-19 18:18           ` Bioconductor package flowPeaks license Artistic 1.0? zimoun
2019-12-20 10:24             ` Perl modules dual licensing (was Re: Bioconductor package flowPeaks license Artistic 1.0?) Giovanni Biscuolo

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=CAJ3okZ00MhGfunGJzr2srW0qRc2yqWjoXj6v5dqKNkRbwjWP6w@mail.gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=g@xelera.eu \
    --cc=guix-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/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).