From 353606f9b73911aff68420707db0174641873a3e Mon Sep 17 00:00:00 2001 From: Christopher Allan Webber Date: Wed, 30 Dec 2015 11:04:28 -0600 Subject: [PATCH] doc: More tweaks to the comments on copyleft section * doc/8sync.texi: Tweaked documentation and added a new paragraph --- doc/8sync.texi | 17 +++++++++++++++-- 1 file changed, 15 insertions(+), 2 deletions(-) diff --git a/doc/8sync.texi b/doc/8sync.texi index b5be59c..bf7484c 100644 --- a/doc/8sync.texi +++ b/doc/8sync.texi @@ -155,12 +155,25 @@ Though it is not a requirement, we request you use 8sync to build free software rather than use it to contribute to the growing world of proprietary software. -The choice of the LGPL for 8sync was a strategic one, though in general, - we encourage stronger copyleft. +The choice of the LGPL for 8sync was a strategic one. +This is not a general recommendation to use the LGPL instead of the GPL + for all libraries. +In general, we encourage stronger copyleft. (For more thinking on this position, see @uref{https://www.gnu.org/licenses/why-not-lgpl.html, Why you shouldn't use the Lesser GPL for your next library}.) +Although 8sync provides some unique features, its main functionality is as + an asynchronous event loop, and there are many other asynchronous event + loop systems out there such as Node.js for Javascript and Asyncio for + Python (there are others as well). +It is popular in some of these communities to hold anti-copyleft positions, + which is unfortunate, and many community members seem to be adopting + these positions because other developers they look up to are holding + them. +If you have come from one of these communities and are exploring 8sync, we + hope reading this will help you reconsider your position. + In particular, if you are building a library or application that uses 8sync in some useful way, consider releasing your program under the GNU GPL or GNU AGPL! -- 2.31.1