Conversation

Notices

1. Embed this notice
   Leah Rowe is not a Rowebot (libreleah@mas.to)'s status on Sunday, 25-Dec-2022 18:08:39 JST Leah Rowe is not a Rowebot

   https://unixsheikh.com/articles/the-problems-with-the-gpl.html

   https://www.unixsheikh.com/articles/why-you-should-migrate-everything-from-linux-to-bsd.html

   Some random wisdom for today. I sometimes link these articles on IRC, when people ask me why I use MIT license on new works.

   • Embed this notice
     Alexandre Oliva (lxo@gnusocial.net)'s status on Sunday, 25-Dec-2022 18:08:29 JST Alexandre Oliva

     in reply to

     • /lib/sys
     this move has been completed over 15 years ago
     remaining incompatibilities are from licenses written with the express purpose of avoiding compatibility with the GPL. surely you're not suggesting GNU should be held accountable for others' licensing hostility
     翠星石 likes this.
   • Embed this notice
     Leah Rowe is not a Rowebot (libreleah@mas.to)'s status on Sunday, 25-Dec-2022 18:08:36 JST Leah Rowe is not a Rowebot

     in reply to

     • /lib/sys

     @libsys Well, MIT license specifically allows sublicensing, making it ideal for mixing with many other works, including those under copyleft.

     These days, I tend to prefer the following:

     MIT license for code, plus documentation if pertaining to the code.

     CC0 for works that consist mainly of documents, as opposed to code. The wording of the MIT license is geared specifically for software projects and accompanying documentation.

   • Embed this notice
     /lib/sys (libsys@chilemasto.casa)'s status on Sunday, 25-Dec-2022 18:08:36 JST /lib/sys

     in reply to

     • Free Software Foundation

     @libreleah @fsf Yes! Remixing flexibility is undoubtedly the most powerful argument in favor of permissive licensing. I'd love to see GNU making the move towards better compatibility with non-GNU licenses in the future. Albeit I recognize it's a difficult legal challenge.

     翠星石 repeated this.
   • Embed this notice
     /lib/sys (libsys@chilemasto.casa)'s status on Sunday, 25-Dec-2022 18:08:37 JST /lib/sys

     in reply to

     @libreleah BTW, people adding a copyleft license over a permissively licensed project is a perfect example of my point. I don't endorse the behavior, but it illustrates exactly why permissive licensing is sometimes not apt for the current state of things.

   • Embed this notice
     /lib/sys (libsys@chilemasto.casa)'s status on Sunday, 25-Dec-2022 18:08:38 JST /lib/sys

     in reply to

     @libreleah IDK, I respect that some people chooses permissive licenses or public domain because they want to be anti-copyright rather than other-kind-of-copyright-advocate. But copyleft is valid in the real world. It's not flawless, but public domain is unprotected, and no activism has been able to change that so far. I hope one day that changes. So far copyleft is the closer we can get to permanent public domain.

     That said, I respect both views and think both are real allies for freedom.

   • Embed this notice
     Alexandre Oliva (lxo@gnusocial.net)'s status on Tuesday, 27-Dec-2022 09:04:25 JST Alexandre Oliva

     in reply to

     • /lib/sys
     I agree. that ideal scenario is pursued by GNU, but sabotaged by opponents thereof. the issue you have can only be addressed by those opponents, who wrote and adopted licenses explicitly for incompatibility and division, so it should be directed at them rather than at GNU.
   • Embed this notice
     /lib/sys (libsys@chilemasto.casa)'s status on Tuesday, 27-Dec-2022 09:04:27 JST /lib/sys

     in reply to

     • Alexandre Oliva

     @lxo GNU has done a great job in ensuring the compatibility of many licenses with the GNU GPL. I think that's worthwhile, I know it took a ton of effort, and I don't mean to discredit it at all. That said, in an ideal scenario all libre software can be combined as long as it respects the four freedoms.

     翠星石 repeated this.
   • Embed this notice
     翠星石 (suiseiseki@freesoftwareextremist.com)'s status on Tuesday, 27-Dec-2022 10:28:20 JST 翠星石

     in reply to
     @libreleah Ah yes, a nice pair of articles that get everything completely wrong.
     
     >I use MIT license on new works.
     MIT had and has many licenses, you should write: MIT expat.