From: zimoun <zimon.toutoune@gmail.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Bioconductor package flowPeaks license Artistic 1.0?
Date: Thu, 19 Dec 2019 22:40:38 +0100 [thread overview]
Message-ID: <CAJ3okZ1k=qb8Cu_a3aN92xLYGQe1xvN1p2JxK8NkjpFiefLd5g@mail.gmail.com> (raw)
In-Reply-To: <87h81whxmw.fsf@nckx>
Hi Tobias,
On Thu, 19 Dec 2019 at 21:24, Tobias Geerinckx-Rice <me@tobias.gr> wrote:
[...]
> > piece of code, try to publish a paper, etc.. Well the
> > Reproducibility
> > of Science crisis.
>
> That is a shame. And that while other scientists (like you) are
> working hard to make research more ‘open’ and reproducible.
Here 'open' is not enough. ;-)
> However, even if they don't maintain the code they can still
> relicence it with no effort on their part. We can still hope.
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 author of this software is Steven Fortune. Copyright (c) 1994 by AT&T
* Bell Laboratories.
* Permission to use, copy, modify, and distribute this software for any
[...]
* This code was originally written by Stephan Fortune in C code. I,
Shane O'Sullivan,
* have since modified it, encapsulating it in a C++ class and, fixing
memory leaks and
* adding accessors to the Voronoi Edges.
* Permission to use, copy, modify, and distribute this software for any
[...]
>>
The most of the files claim:
<<
* The author of this software is Yongchao Ge.
* Permission to use, copy, modify, and distribute this software for any
* purpose without fee is hereby granted, provided that this entire notice
* is included in all copies of any software which is or includes a copy
* or modification of this software and in all copies of the supporting
* documentation for such software.
* THIS SOFTWARE IS BEING PROVIDED "AS IS", WITHOUT ANY EXPRESS OR IMPLIED
* WARRANTY. IN PARTICULAR, THE AUTHOR DOES NOT MAKE ANY
* REPRESENTATION OR WARRANTY OF ANY KIND CONCERNING THE MERCHANTABILITY
* OF THIS SOFTWARE OR ITS FITNESS FOR ANY PARTICULAR PURPOSE.
>>
Well, the only mention of the Artistic 1.0 license is these 3 files:
README, DESCRIPTION and vignettes/flowPeaks-guide.Rnw.
Does that mean I am allowed to reuse almost everything and repack in
another repo licensing with a "good" license?
[...]
> If I'm still not making myself clear, I apologise & capitulate.
I got it. Yes it is clear!
> > So I will appeal to FSF/GNU. ;-)
>
> I admire your tenacity. Good luck!
Before I need to assembling the file. :-)
For example, how many packages in Bioconductor use the Artistic 1.0?
Thank for all your explanation and your time.
All the best,
simon
next prev parent reply other threads:[~2019-12-19 21:40 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 [this message]
2019-12-20 9:28 ` Giovanni Biscuolo
2019-12-20 10:47 ` zimoun
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='CAJ3okZ1k=qb8Cu_a3aN92xLYGQe1xvN1p2JxK8NkjpFiefLd5g@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=me@tobias.gr \
/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).