3 ms·
Is rust in Linux a good opportunity to review the Linux licensing? For example, go Gplv2+ instead of just GPLv2? Or maybe just forcing developers to subscribe
by Luker88 4y ago
Is rust in Linux a good opportunity to review the Linux licensing?
For example, go Gplv2+ instead of just GPLv2?
Or maybe just forcing developers to subscribe their DCO (Developers Certificate Of Origin)
I remember a lot of kernel developers signing additional declarations to clear up some licensing issue, I remember it was not all of them and can't find the reference.
Basically any cleanup on the licensing side, so that you know that rust also means "the correct way"? Sure, it will take decades, but at least you would not be stuck with current "gplv2-only-dco-maybe-additional-guarantees"
Can someone @Greg or even @Linus on this?
- mustache_kimono 4y agoFWIW, Rust has a strong "MIT or Apache" culture. These contributions to the kernel are "MIT or Apache," because what if the BSDs want to use these cool language bits for their OS? Doubt GPLv2+ has much resonance here.
- phendrenad2 4y agoWhat do you mean by GPL2+ exactly? I've never heard of this.