Sujet : Affero General Public License (AGPL) (Was: There is GNU Prolog)
De : janburse (at) *nospam* fastmail.fm (Mild Shock)
Groupes : comp.lang.prologDate : 24. Nov 2024, 00:43:46
Autres entêtes
Message-ID : <vhtpbg$j8c6$1@solani.org>
References : 1 2
User-Agent : Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Firefox/91.0 SeaMonkey/2.53.19
Hi,
What you don't find in GNU Prolog is library(misc/spin),
or open/3 that can work with http: or https: . I even
don't know whether GNU is still a good license for
Web 2.0/3.0. Like if you write server code or client code
with the licensed software. It seems there are some
loopholes in GNU concerning Web 2.0/3.0.
ChatGPT tells me the following:
---------------------- cut here -----------------------
The Affero General Public License (AGPL) is a variant of
the GNU General Public License (GPL) designed specifically
for software that is used over a network, such as web
applications or SaaS (Software-as-a-Service) platforms.
It ensures that users accessing the software via a network
have the same freedoms as those who receive it directly.
Key Features of the AGPL:
Network Interaction Clause:
The AGPL includes an additional requirement not found
in the standard GPL. If you modify AGPL-licensed software
and allow users to interact with it over a network (e.g.,
through a web application), you must make the source code
of the modified version available to those users.
Focus on SaaS:
The AGPL closes the "SaaS loophole" found in the standard
GPL. Under the standard GPL, if you run modified software
on a server without distributing it, you're not obligated
to share your modifications. The AGPL changes this: network
access to the software is treated as a form of distribution.
Same Four Freedoms:
Like the GPL, the AGPL provides users with the freedoms to
run, study, modify, and redistribute the software.
Compatibility with the GPL:
Software under the AGPL is compatible with the GPL. However,
when combining AGPL and GPL code, the resulting work must
be licensed under the AGPL to maintain the stronger network clause.
Common Use Cases:
Web-based software, such as content management systems (CMS),
databases, or frameworks. SaaS platforms or services that
incorporate open-source components but need to respect the
AGPL's requirements for source code transparency.
In essence, the AGPL ensures that even when software is used
over a network, its freedoms and obligations remain intact
for the end users.
---------------------- cut here -----------------------
Mild Shock schrieb:
Hi,
If you want something with a GNU license,
there is GNU Prolog:
http://www.gprolog.org/
According to wiki, it has these two licenses:
https://en.wikipedia.org/wiki/GNU_General_Public_License
https://en.wikipedia.org/wiki/GNU_Lesser_General_Public_License
Better use GNU Prolog if you want exactly some GNU license.
Bye
Julio Di Egidio schrieb:
I am looking for a *clean and mean* Prolog implementation: Dogelog at a cursory inspection (I have had a look at docs and code at www.xlog.ch) looks like a pretty good candidate.
>
Just it quite bothers me that it is not "free software", so I would not be able to fork it not even as an extreme measure. Rationale/any plans to open it say under GPL (i.e. free for non-commercial use)?
>
BTW, any plans to implement a library like SWI's prolog_trace?
<https://www.swi-prolog.org/pldoc/man?section=prologtrace>
I am finding that quite useful for debugging.
>
-Julio
>