▲ | kube-system a day ago | |||||||
The license snippet you quoted means that they have given YOU the right to copy, change (or compile), and redistribute, distribute anything you've created from it. Nothing about that implies contributors are required to give you binaries. This isn't all that uncommon -- usually open source licenses only apply to the source. > comically easy to bypass and literally forces someone to automate a github mirror that builds new releases. Your essentially enforcing the existence of a fork. They even provide the github actions necessary to do so in their repo already... Yeah, cloning and building software is something that is straightforward for software developers to do. Traditionally people would clone software to their own machine, but you can use GitHub or whatever tools you want to work with the source. I'm not sure if I would call this a "bypass" -- this is the typical way FOSS software has always worked, and it's part of the reason why FOSS is popular :) | ||||||||
▲ | ApolloFortyNine a day ago | parent | next [-] | |||||||
>I'm not sure if I would call this a "bypass" -- this is the typical way FOSS software has always worked, and it's part of the reason why FOSS is popular :) Any other packages you know of that are open source but have a trap license where if you download it through the package manager you owe them money? :) Plus the license mentions the binaries have to be distributed with the same license. Attaching a "if you click this download button you owe us $10000" button doesn't seem very typical to common FOSS values :) I'd say a big reason FOSS is so popular is the free and open source nature :) | ||||||||
| ||||||||
▲ | a day ago | parent | prev [-] | |||||||
[deleted] |