-
Notifications
You must be signed in to change notification settings - Fork 729
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add SPDX identifiers #143
Add SPDX identifiers #143
Conversation
Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Yegor.
Thanks for picking this up!
What's the reason to tag canfdtest.c to "GPL-2.0-or-later" and not "GPL2.0-only" as in the other files?
I would recomment not to use "GPL-2.0-or-later"
@hartkopp my logic is like this: if the license text in the file has the following sentence then it is GPL-2.0-or-later:
An this is the case for the most C files in can-utils. See how this license type is defined in the header: https://spdx.org/licenses/GPL-2.0-or-later.html Other files like |
The stuff which was originally from Volkswagen is gpl2-or-bsd-clause3 as we intended to allow the socket API in other operating systems too. Therefore the basic tools follow this license scheme. |
Let's take |
If we want to relicense the files under |
Hi @marckleinebudde , |
Doh! I meant |
So we're talking about the following files:
You already have my ACK for re-licensing. @ukleinek , @grandwolf, @rshanmu, @btashton, @jmahler, @umlaeute, @sgh, @jschall, @mansr, @ftheile, @olerem, @snewz, @bombilee what do you think about it? |
Hi
I trust you guys in doing the right thing. I have no real preference, so it's
an ACK from me as well.
onsdag den 26. juni 2019 11.26.22 CEST skrev Yegor Yefremov:
… So we're talking about the following files:
- slcand.c
- canfdtest.c
- slcanpty.c
- jcat.c
- can-calc-bit-timing.c
You already have my ACK for re-licensing.
@ukleinek , @grandwolf, @rshanmu, @btashton, @jmahler, @umlaeute, @sgh,
@jschall, @mansr, @ftheile, @olerem, @snewz, @bombilee what do you think
about it?
--
Søren Holm
|
|
Oh, just detected that And of course
Tnx! |
My contribution hardly gives me the right to an opinion here, but either way, I don't care. |
what's the reason to clamp it down to |
Acked-by: Sven Schmitt sven.schmitt@gmx.net |
Acked-by: Oleksij Rempel ore@pengutronix.de |
Please check the general discussions about GPLv2 -vs- GPLv3 on the internet, e.g. the tivoization problem which makes it harder for commercial users/products. IMHO GPLv2 serves can-utils best - and the VW code is even more relaxed with gpl2-or-bsd-clause3. |
My contribution seems to be just
not sure if that is relevant enough to be able to oppose a license change. Anyhow, I'm not opposed, so: Acked-by: Uwe Kleine-König u.kleine-koenig@pengutronix.de for a switch to |
Acked-by: Brennan Ashton bashton@brennanashton.com |
well yes; tivoization is the reason i mostly switched to GPLv3 these days :-) (but then, I mostly don't really work in the industries, so my POV might be a bit "academic") but anyhow: Acked-By: IOhannes m zmölnig zmoelnig@iem.at |
Acked-by: Frank Theile ftheile@grundfos.com |
I personally prefer GPL-2.0-or-later, but well, here is my: Acked-by: Wolfgang Grandegger wg@grandegger.com |
Acked-by: Jeremiah Mahler jmmahler@gmail.com |
Acked-by: Jonathan Challinger mr.challinger@gmail.com |
Acked-by: Cheng-Lung Lee chenglung@gmail.com |
https://www.linkedin.com/in/rameshshanmugasundaram/ probably this helps.... |
Thanks! So let's wait for some more time for feedback ... |
Acked-by: Ramesh Shanmugasundaram rashanmu@gmail.com Apologies for not updating my email preferences. Corrected now. Thanks @yegorich |
@hartkopp what is the next step? Should this PR be merged as is and the followup PR change the licenses? |
Sounds good. Reference this PR from the new one that changes the license to |
Signed-off-by: Yegor Yefremov yegorslists@googlemail.com