Repository navigation
GPL License Issues for Past Releases #16725
Replies: 1 comment 4 replies
|
Thanks for your interest in our work.
If you spot another case, please open an issue with the file and lines and we'll take care of it. I'd also ask that we stop going back to the license question/debate. As you saw, it has been discussed many times already and it will probably come up again today on Reddit, Phoronix or Hacker News with the 0.13.0 announcement. The answer isn't going to change, so I'll lock this discussion. |
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
So I've had two issues that I've opened one for
chcon.rsand one forshred.rs. They both found historical use of GPL code in this project sourced from the GNU Coreutils reference implementation. This GPL code has made it into every single release of the project so far (but based on recent changes maybe not the n+1 release. Which means that every release from 0.0.1 -> 0.12.0 has at least one of these issues (withshred.rs's code introduced in the initial release0.0.1andchcon.rs's code introduced in0.0.8) I had the bot make a handy infographic describing the issue. But essentially for each and every one of those releases people are entitled to have it as GPL and all the corresponding source as GPL (as this project is compiled and distributed into one executable binary).In the past, discussions like 8707 (ethics), 3712 (legacy) and 7797 (up streaming) have brought up and discussed various issues with not following the license (and there's a few other times it's been brought up).
One of the main reasons brought up for why it would be infeasible to do is that contributors have contributed under the MIT license historically (from 3712):
But since every file in the project is already required to be released under the terms of the GPL because of the tainting of code and it's inclusion in literally every release that no longer seems to be an issue.
Additionally, if you choose to use the upstream license (now that you can essentially do so) you gain several strategic advantages:
TLDR: Every release of this project is required to be released under the GPL, because of the GPL-derived code in
shred.rsandchcon.rsshipped in every release from 0.0.1 through 0.12.0. Under the GPL, those releases are all derivative work. That eliminates the primary blocker from releasing the project under the GPL. Rather than treating that as a problem to work around, the project could treat it as an opportunity to adopt the GPL. There's a bunch of practical benefits to doing so and it eliminates the biggest complaint about this project that tends to overshadow its technical excellence.All reactions