From: Giovanni Biscuolo <g@xelera.eu>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: [OT] Re: Guix and Bioconductor.
Date: Sat, 21 Dec 2019 11:06:22 +0100 [thread overview]
Message-ID: <871rsy6li9.fsf@roquette.mug.biscuolo.net> (raw)
In-Reply-To: <875zibqczb.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 2582 bytes --]
[A quick and dirty off topic rant... forgive me!]
Hello Ricardo,
thank you for the info!
...and thank you all for working on resolving this class of problems
through Guix!
Ricardo Wurmus <rekado@elephly.net> writes:
> Giovanni Biscuolo <g@xelera.eu> writes:
[...]
>> 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).
This confirms that licensing is an integral part of reproducibility and
replicability, unfortunately a very neglected part even in academia (not
to mention "industry") :-( . This is also part of the current science
crisis... OK stop ranting :-D
> It’s a pretty frustrating process to weed out these packages.
Let them know! (Do they know?)
«Dear Bioconductor Team, you state you are committed to bla bla
reproducible research but *some* of the research you host is
unreproducible for the simple reason some authors are ignoring licensing
issues...»
>> 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.
I'm out from academia, but every time I talk to friends involved in
academia I'm pretty astonished by the general lack of scientific method
[1] [2] applied in academia :-O. A little bit of metascience would help.
...and more Guix in academia is part of the solution :-D
Thanks! Gio'
[1] https://en.wikipedia.org/wiki/Reproducibility#Reproducible_research
«In 2016, Nature conducted a survey of 1,576 researchers who took a
brief online questionnaire on reproducibility in research. According to
the survey, more than 70% of researchers have tried and failed to
reproduce another scientist's experiments, and more than half have
failed to reproduce their own experiments.»
[2] https://en.wikipedia.org/wiki/Replication_crisis
--
Giovanni Biscuolo
Xelera IT Infrastructures
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-12-21 10:06 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
2019-12-21 10:06 ` Giovanni Biscuolo [this message]
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=871rsy6li9.fsf@roquette.mug.biscuolo.net \
--to=g@xelera.eu \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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).