guix-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug#68159] [PATCH] gnu: Add python-camb.


From: Sharlatan Hellseher
Subject: [bug#68159] [PATCH] gnu: Add python-camb.
Date: Thu, 18 Jan 2024 11:04:48 +0000

Hi,

Thank you Simon for details licence check!

Troy, if you still want to contribute your patch for wide audience of Guix
users, please take a look at maintained by Ricardo channels for
Scientific software:

https://github.com/guix-science/guix-science
https://github.com/guix-science/guix-science-nonfree

Thanks,
Oleg

On Wed, 17 Jan 2024 at 20:25, Simon Tournier <zimon.toutoune@gmail.com> wrote:
>
> 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



-- 
VCS: https://github.incerto.xyz/; https://git.sr.ht/~hellseher/
GPG: 9847 81DE 689C 21C2 6418 0867 76D7 27BF F62C D2B5

… наш разум - превосходная объяснительная машина которая способна
найти смысл почти в чем угодно, истолковать любой феномен, но
совершенно не в состоянии принять мысль о непредсказуемости.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]