Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
en.osm.town is one of the many independent Mastodon servers you can use to participate in the fediverse.
An independent, community of OpenStreetMap people on the Fediverse/Mastodon. Funding graciously provided by the OpenStreetMap Foundation.

Administered by:

Server stats:

268
active users

en.osm.town: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.7

Public *
Thorsten Leemhuis (acct. 1/4)

TIL: @tuxedocomputers released #Linux #kernel drivers for their machines under the #GPLv3, which makes it impossible for competitors and distros to ship them pre-compiled, as that license is incompatible with the #LinuxKernel's #GPLv2 only license.

They did this purposely, allegedly to "keep control of the upstream pacing" – and want to re-license the code while upstreaming.

github.com/tuxedocomputers/tux

gitlab.com/tuxedocomputers/dev

gitlab.com/tuxedocomputers/dev

gitlab.com/tuxedocomputers/dev

Quiet public
Thibaultmol 🌈

@kernellogger @tuxedocomputers important reply to mention on this thread:

Werner Sembach explaining in one of the gitlab comments: No, Yes, Let me explain: tuxedo-drivers would not be accepted upstream as-is and would require partial rewrites, this comes with some downsides: Intricate knowlege of the whole historic and current cataloge of supported devices is needed to not introduce regressions. As upstreaming would most likley not happen at once, compatiblity with the tuxedo-drivers dkms package must be maintained at any given point in time. So we need to be included tightly in the upstreaming process anyways and well, ressources are, as always, limited. I would like to call upon the "Assume good faith" principle. tuxedo-drivers (formerly tuxedo-keyboard) was open source from day 1. We try our best to make tuxedo devices as compatible as possible and you can look at the code and use it to your desire under GPLv3 which we strongly respect. The plan hinted above was chosen to not bind unnecessary ressouces so we can spend more time on actually coding.
Quiet public
Thorsten Leemhuis (acct. 1/4)

@thibaultmol @tuxedocomputers

Yeah, it's well known that Open Source has always works so well, because it allows authors to control their code.

Ohh, wait, no! It was the other way around: Open Source works so well because people do not have control and thus are able to bring it to levels that seemed unreachable earlier! 😬

Thibaultmol 🌈

@kernellogger @tuxedocomputers devils advocate: They know their code isn't good enough to be included in the kernel itself, so they want to rewrite before that happens. this license allows them to prevent from someone else putting the code in and then going "wow, this toxedo code sucks" and then tuxedo having to go "well yeah, it wasn't ready for kernel merging yet"

Nov 04, 2024, 08:04 AM·Quiet public
0boosts·1favorite
Quiet public
Thorsten Leemhuis (acct. 1/4)

@thibaultmol @tuxedocomputers

I'd consider that a lame excuse; just put a "we know the code does not meet the standards upstream expects and are working on a cleaner driver we plan to upstream" into the README while releasing it as GPLv2 – nearly everybody would understand and those who do not fall into the "you sometimes just have to ignore some people" category.

But then others could at least easily borrow parts of the code if they upstream improved or independently developed drivers.

Quiet public
Thibaultmol 🌈

@kernellogger @tuxedocomputers I'm confused what they really 'gain' from doing this (using GPLv3) , it's weird yeah

Quiet public *
Krzysztof Kozlowski
@thibaultmol @kernellogger @tuxedocomputers " this license allows them to prevent from someone else" - this is exactly something they should not do. We all know open-source compliance releases have poor quality and we do not have problems with that. That's life. But what they did is:
1. Release poor quality code.
2. Restrict community rights of improving it and bringing upstream.
That's a big no-go, big NAK for Tuxedo. Interesting twist, how one can release something open-source but not in open-source spirit.
Quiet public
Pavel Machek
@thibaultmol @kernellogger @tuxedocomputers Unless they wrote code for something else and ported, their code is derived from GPLv2 work, and Tuxedo can't choose the licensing. What they are doing is likely not legal.
ExploreLive feeds
About