4 ms·
Have you ever read through the entirety of GPLv3? It's pretty damn long: http://www.gnu.org/licenses/gpl-3.0.en.html http://www.gnu.org/licenses/gpl-3.0.en.html
by Leszek 11y ago
Have you ever read through the entirety of GPLv3? It's pretty damn long: http://www.gnu.org/licenses/gpl-3.0.en.html http://www.gnu.org/licenses/gpl-3.0.en.html
- task_queue 11y agoAn end-user of software licensed under the GPLv3 doesn't ever have to read the license until they decide to modify and share it. At that point they should be well-versed in reading licensing agreements because they're touching others' source code.
- Leszek 11y agoFair point, but in that case free/open source is irrelevant: one could equally well build a closed-source app without a ToS, or an open source app with one.
- task_queue 11y agoI agree completely. I don't know what the OP was getting at.
- mschuster91 11y agoYeah, but the GPL is a pretty standard license and as such has many summarizations and tl;drs floating on the web. With company legalese, everyone has its own...
- belorn 11y agoLength doesn't really say anything about scope. I can take MIT license, one of the smallest and most permissive license out there, and add a single word which would make it incompatible with every other license in the world including itself. The only saving grace with FLOSS licenses is that they are not contracts, and only impacts those who seeks additional permission to distribute copies of a copyrighted word. If someone feel they don't understand the conditions which the license automatically grants permissions, they can always go directly to the author and ask them.