From: Ricardo Wurmus <rekado@elephly.net>
To: Giovanni Biscuolo <g@xelera.eu>
Cc: guix-devel@gnu.org
Subject: Re: Guix and Bioconductor.
Date: Fri, 20 Dec 2019 15:38:00 +0100 [thread overview]
Message-ID: <875zibqczb.fsf@elephly.net> (raw)
In-Reply-To: <87fthf6wk7.fsf@roquette.mug.biscuolo.net>
Giovanni Biscuolo <g@xelera.eu> writes:
> To all Guix interested in Bioconductor,
>
> forgive me if I raise this question here and not to "upstream", but IMHO
> this issue should escalate to Bioconductor and Guix community could do
> better than single package maintainers, zimoun in this case
>
> I'm not a user of Bioconductor packages so I have no "weight" on this
> matter, but I guess in Guix community there are **many** (potential?)
> users of Bioconductor packages: could you please organize a "pressure
> group" to convince Bioconductor be strict in their package acceptance
> rules?
>
> I fear flowPeacks will not be the last package with this kind licensing
> problems
It sure isn’t. In the past I have tried to do a mass import from
Bioconductor and what slows me down the most is incorrect or non-free
licensing. There are some packages that declare to be licensed under
Artistic 2.0, but then actually they contain data from databases that
do not permit commercial use. Or they contain a copy of non-free tools,
or only work when those tools are present (e.g. kent tools, of which we
provide a package containing the few free tools).
It’s a pretty frustrating process to weed out these packages.
> Since «Bioconductor is committed to open source, collaborative,
> distributed software development and literate, reproducible research.» [1]
CRAN appears to be stricter about licenses (even though “strict” is
probably much too strong a word…). Bioconductor people appear to care a
little less.
--
Ricardo
next prev parent reply other threads:[~2019-12-20 14:38 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
2019-12-20 14:40 ` Ricardo Wurmus
2019-12-20 11:55 ` Guix and Bioconductor Giovanni Biscuolo
2019-12-20 14:38 ` Ricardo Wurmus [this message]
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=875zibqczb.fsf@elephly.net \
--to=rekado@elephly.net \
--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).