LibrePlanet discussion list archive (unofficial mirror)
 help / color / mirror / Atom feed
From: andrew via libreplanet-discuss <libreplanet-discuss@libreplanet.org>
To: libreplanet-discuss@libreplanet.org
Subject: People calling the GPLs 'evil licenses' - action plan?
Date: Tue, 17 May 2022 23:52:50 +0800	[thread overview]
Message-ID: <20220517155250.q65vcyqtujvhutec@gentoo-dell> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2060 bytes --]

Andrew  Would https://git.andrewyu.org/pygame-multiplayer/ suffice to indicate extending an existing Expat (MIT) project into a project based on the original work but licensed under the (A)GPL?
Andrew  ugh, forgot to place the agpl in it         
ChrisWarrick    ask a lawyer
ChrisWarrick    (and consider a less evil license)  
Andrew  Not asking for legal advice, just general practice
Andrew  And I don't consider the GPLs to be evil, I use  them for bigger projects while I use public domain (unlicense) for smaller ones
ChrisWarrick    licenses are legal stuff, so you are asking for legal advice
Andrew  asking stuff like 'does the US have any laws' is legal but isn't asking for legal advice imo
ChrisWarrick    your question is “am I interpeting and using the license correctly”
Andrew  i guess                                     
Andrew  and why do you think the gpl is evil?        
ChrisWarrick    GPL, and especially AGPL, makes your code less free than MIT/BSD
nedbat  Andrew: this is a classic debate            
Andrew  ChrisWarrick: PM me, thanks
Andrew  because I want to prevent people from proprietizing it
ChrisWarrick    but at the same time, you’re benefitting from Brandon Nguyen’s work
Andrew  yes
ChrisWarrick    but he isn’t able to benefit from yours
Andrew  they could use the AGPL/GPL, and they could ask me for an exception
Andrew  the greater danger is people taking expat code and proprietizing it, hindering free use altogether
ChrisWarrick    what is wrong with proprietary use though?
Andrew  i'll get back to you with an article tomorrow, thanks on your thoughts
Andrew  meanwhile, https://lukesmith.xyz/articles/why-i-use-the-gpl-and-not-cuck-licenses explains part of it
Andrew  dont agree to all of it, i see a lot of use of permissive licenses, but not for the project working on now
ChrisWarrick    do you have a less offensive article?
Andrew  I'm working on that
ChrisWarrick    okay    

I hope this is clear enough on what I need ... well, how do I explain
the GPL to them?

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 184 bytes --]

_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss

             reply	other threads:[~2022-05-17 15:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-17 15:52 andrew via libreplanet-discuss [this message]
2022-05-17 16:20 ` People calling the GPLs 'evil licenses' - action plan? wolftune
2022-05-17 21:27 ` Dennis Payne
2022-05-18  2:15   ` Aaron Wolf
2022-05-18 16:26     ` Jim Garrett

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://lists.gnu.org/mailman/listinfo/libreplanet-discuss

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220517155250.q65vcyqtujvhutec@gentoo-dell \
    --to=libreplanet-discuss@libreplanet.org \
    --cc=andrew@andrewyu.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.
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).