@thomas OK, but how about patents? Only copyleft licenses seem to be good at handling them, others are ambiguous or don't take care of them at all.
Conversation
Notices
-
Xerz 💗 [UNMOVED] (espectalll@mstdn.io)'s status on Sunday, 11-Mar-2018 21:28:38 UTC Xerz 💗 [UNMOVED] -
rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk (rugk@gnusocial.de)'s status on Sunday, 11-Mar-2018 21:50:41 UTC rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk @espectalll @thomas apache license us not copyleft, but deals somehow with patents. But patents are AFAIK still something different than copyright so it can be that software is free (license), bit covered by patents and this people can't use it.
As for personal small projects, just avoid patented stuff. Then you need not to care about patents. Just avoid complicated legal things.😉 -
Xerz 💗 [UNMOVED] (espectalll@mstdn.io)'s status on Sunday, 11-Mar-2018 21:52:10 UTC Xerz 💗 [UNMOVED] @rugk @thomas The idea is choosing a license for (potentially) large projects - I already choose CC0 for small ones.
I'll consider Apache then, thank you! 😺
-
rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk (rugk@gnusocial.de)'s status on Sunday, 11-Mar-2018 22:35:52 UTC rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk @espectalll @thomas also large projects often do not use patents… (I think you should nevertheless know what patents you use there, if there are some)
-