From: Simon Tournier <zimon.toutoune@gmail.com>
To: Sharlatan Hellseher <sharlatanus@gmail.com>, 68159@debbugs.gnu.org
Cc: Tobias Geerinckx-Rice <me@tobias.gr>
Subject: [bug#68159] [PATCH] gnu: Add python-camb.
Date: Wed, 17 Jan 2024 16:19:38 +0100 [thread overview]
Message-ID: <87h6jcugvp.fsf@gmail.com> (raw)
In-Reply-To: <CAO+9K5oxAongwMd5uO9p_kKV=CArO0P0Go0H1ybmOTRP52g-mQ@mail.gmail.com>
Hi,
On Tue, 16 Jan 2024 at 19:09, Sharlatan Hellseher <sharlatanus@gmail.com> wrote:
> I would appreciate your expertise in this license case. It is a maintained
> fork of an older project written in Python and Fortran.
Well, I do not feel an expert on the topic. From my point of view,
there is two points:
1. As mentioned, an unclear license of the current product because it
is adapted from previous codes.
--8<---------------cut here---------------start------------->8---
Portions of this software were originally based on
CMBFAST by Uros Seljak and Matias Zaldarriaga, itself based on Boltzmann code written by Edmund
Bertschinger, Chung-Pei Ma and Paul Bode.
Original CMBFAST copyright and disclaimer:
Copyright 1996 by Harvard-Smithsonian Center for Astrophysics and
the Massachusetts Institute of Technology. All rights reserved.
THIS SOFTWARE IS PROVIDED "AS IS", AND M.I.T. OR C.f.A. MAKE NO
REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED.
By way of example, but not limitation,
M.I.T. AND C.f.A MAKE NO REPRESENTATIONS OR WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT
THE USE OF THE LICENSED SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE
ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.
portions of this software are based on the COSMICS package of
E. Bertschinger. See the LICENSE file of the COSMICS distribution
for restrictions on the modification and distribution of this software.
--8<---------------cut here---------------end--------------->8---
For this point #1, my understanding is:
a) The license applied by copyright holders is not clear. However,
since the license of the modifications is LGPL (with exceptions), we
could assume that people modifying (and redistributing) the code
have the right to do.
b) It is not dual-licensed and not explicitly ’expat’. Somehow, MIT is
the copyright holder but that does not imply the license is ’expat’.
2. It is not plain LGPL but considering 3 exceptions.
--8<---------------cut here---------------start------------->8---
LICENSING
-------------------------------
You are licensed to use this software free of charge within the terms of the LGPL (see below), with
these additional conditions:
- Any publication using results of the code must be submitted
to arXiv.org at the same time as, or before, submitting to a
journal. arXiv must be updated with a version equivalent to
that accepted by the journal on journal acceptance.
- If you identify any bugs you report them as soon as confirmed
- This license, the above copyright notices and disclaimer appear
on ALL copies of the software and documentation, including
modifications that you make for internal use or for distribution
--8<---------------cut here---------------end--------------->8---
And from my understanding, these exceptions make the software license
non-free.
Well, I am not a lawyer (IANAL). :-)
Cheers,
simon
next prev parent reply other threads:[~2024-01-17 20:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-30 23:23 [bug#68159] [PATCH] gnu: Add python-camb Troy Figiel
2023-12-30 23:49 ` [bug#68159] (no subject) Troy Figiel
2024-01-16 18:56 ` [bug#68159] [PATCH] gnu: Add python-camb Sharlatan Hellseher
2024-01-16 19:09 ` Sharlatan Hellseher
2024-01-17 15:19 ` Simon Tournier [this message]
2024-01-18 11:04 ` Sharlatan Hellseher
2024-01-17 11:14 ` Troy Figiel
2024-01-18 11:42 ` Troy Figiel
2024-01-24 15:07 ` bug#68159: " Maxim Cournoyer
2024-01-21 10:42 ` [bug#68159] " Sharlatan Hellseher
2024-01-21 12:11 ` Troy Figiel
[not found] <mailman.71232.1705523462.1170.guix-patches@gnu.org>
2024-01-17 23:04 ` Troy Figiel
2024-01-18 10:45 ` Simon Tournier
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=87h6jcugvp.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=68159@debbugs.gnu.org \
--cc=me@tobias.gr \
--cc=sharlatanus@gmail.com \
/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).