From: Ricardo Wurmus <rekado@elephly.net>
To: Alex Vong <alexvong1995@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] gnu: Add kallisto.
Date: Wed, 18 Jan 2017 21:31:41 +0100 [thread overview]
Message-ID: <877f5s6rf6.fsf@elephly.net> (raw)
In-Reply-To: <87eg00mxp4.fsf@gmail.com>
Alex Vong <alexvong1995@gmail.com> writes:
> Looking at the license text:
>
> Copyright ©2015. The Regents of the University of California (Regents). All
> Rights Reserved. Permission to use, copy, modify, and distribute this software
> and its documentation for educational and research not-for-profit purposes,
> without fee and without a signed licensing agreement, is hereby granted,
> provided that the above copyright notice, this paragraph and the following two
> paragraphs appear in all copies, modifications, and distributions. Contact The
> Office of Technology Licensing, UC Berkeley, 2150 Shattuck Avenue, Suite 510,
> Berkeley, CA 94720-1620, (510) 643-7201, for commercial licensing
> opportunities.
>
>
> It seems the license is {fsf, dfsg} non-free because it does not allow
> commercial usage. More precisely, it violates freedom 0 (the freedom to
> run the program as you wish, for any purpose).
Correct. Kallisto is non-free software.
> Does anybody know of any fork or should we use an old version?
I don’t know of any version that is free software.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2017-01-18 20:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 10:09 [PATCH] gnu: Add kallisto Ra
2017-01-18 11:09 ` Alex Vong
2017-01-18 17:58 ` Ra
2017-01-18 19:41 ` Marius Bakke
2017-01-18 20:31 ` Ricardo Wurmus [this message]
2017-01-19 8:08 ` Ra
2017-01-19 8:17 ` 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=877f5s6rf6.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=alexvong1995@gmail.com \
--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).