From: nigko <nigko.yerden@gmail.com>
To: guix-devel@gnu.org
Subject: Can ALPS be included in the Guix repo? The question is about the licenses.
Date: Sat, 12 Aug 2023 16:03:31 +0500 [thread overview]
Message-ID: <f8dc822a-75bc-44d8-8775-65dedc6991be@gmail.com> (raw)
Hello Guix!
The ALPS project* (Algorithms and Libraries for Physics Simulations)
https://web.archive.org/web/20210508050408/https://alps.comp-phys.org/mediawiki/index.php/Main_Page
is an open source effort aiming at providing simulation codes for
strongly correlated quantum mechanical systems as well as C++ libraries
for simplifying the development of such code.
According to https://alps.comp-phys.org/mediawiki/index.php/Licensing
the ALPS _Libraries_ are available for _academic and non-commercial_ use
under the terms of the ALPS _Library_ License version 1.0,
https://web.archive.org/web/20210506121129/https://alps.comp-phys.org/static/software/ALPS/LICENSE.txt/,
the ALPS _Applications_ under the ALPS _Application_ License version 1.0,
https://web.archive.org/web/20210512081507/https://alps.comp-phys.org/static/software/applications/LICENSE.txt/.
I wonder can ALPS be included in the Guix repo? My concern is in the
licenses. In particular, the ALPS licenses state that the ALPS is for
"non-commercial academic use", but according to
https://www.gnu.org/philosophy/free-sw.html "a free program must be
available for commercial use, commercial development, and commercial
distribution", which are in the contradiction.
Regards,
N Y
*Since 2022-10-21 the project is being dormant,
https://green.physics.lsa.umich.edu/alps_legacy/index.php?title=Main_Page
next reply other threads:[~2023-08-13 13:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-12 11:03 nigko [this message]
2023-08-13 14:31 ` Can ALPS be included in the Guix repo? The question is about the licenses Efraim Flashner
2023-08-19 8:42 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f8dc822a-75bc-44d8-8775-65dedc6991be@gmail.com \
--to=nigko.yerden@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.