On Wed, Feb 14, 2018 at 3:57 PM, Michal Kubecek <mkubecek@suse.cz> wrote:
On Tue, Feb 13, 2018 at 04:14:50PM +0100, Stephan Kulow wrote:
My thought: are they nuts to make a fine working standard incompatible without need?
How can they on their front page link to Dec 12 news that Linux kernel now has SPDX identifiers to then release on Dec 28 a new license list that makes all these SPDX identifiers outdated?
My thought exactly. Given the "less than friendly" response of some kernel developers to Greg's effort to introduce the SPDX identifiers to kernel source tree, I'm looking forward to the general response when he is going to come with "Sorry, guys, there is a new version of SPDX and those set-to-stone identifiers have to be changed. But don't worry, these are the right ones - as long as they don't come with SPDX 4.0."
I say we ignore they did this stupid mistake. Can happen to the best - it was Christmas and possibly they had too much wine.
How I wish I could believe they will realize it was a mistake and take it back.
I've been personally super cheesed off about this new revision, especially since I was previously advocating for SPDX adoption in Fedora. This kind of crap will only make things harder going forward, and already changing the identifiers is going to be a mess for various reasons (*stares at BSD and MIT licensed software*). I don't even *like* the changes they made in 3.0, because they make it even more verbose than it already was, removed *yet another* set of expressions, and made it even more difficult to rationalize across the board. What's the point of this anymore?! -- 真実はいつも一つ！/ Always, there's only one truth! -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org