Notices by Krzysztof Kozlowski (krzk@social.kernel.org)

Embed this notice
Krzysztof Kozlowski (krzk@social.kernel.org)'s status on Thursday, 21-Nov-2024 19:56:26 JST Krzysztof Kozlowski
in reply to
- Don McCurdy
@donmccurdy Copilot training and "3-week program consisting of a 5-10 hour commitment each week" is exactly what community needs to fix cases like XZ with busy maintainer bullied by bad actors.

Microsoft, are you ill? Are you just joking here around or just want to sell your crapy Copilot? This is just an insult to Open Source maintainers.

@martin.social You do not see how inappropriate this is?

In conversation about 3 days ago from social.kernel.org permalink
Embed this notice
Krzysztof Kozlowski (krzk@social.kernel.org)'s status on Thursday, 21-Nov-2024 19:47:27 JST Krzysztof Kozlowski
in reply to

@luis_in_brief Aaah, so now I know what was missing in my maintainer's life:
"Maintainers will get hands-on learning of security principles, tools like GitHub Copilot and Copilot Autofix"
Github Copilot!

Microsoft jokes from open-source...

In conversation about 3 days ago from social.kernel.org permalink
Embed this notice
Krzysztof Kozlowski (krzk@social.kernel.org)'s status on Wednesday, 20-Nov-2024 18:40:44 JST Krzysztof Kozlowski
in reply to
- Jonathan Corbet
- Jarkko Sakkinen
@jarkko What I miss in LWN stats is the employer stats for Tested/Reviewed-by. There are such for committer Signed-offs, which shows only part of employer support for long term maintenance.

@corbet Maybe for the next LWN stats? (Tested/Reviewed aggregated over employer names)

In conversation about 4 days ago from social.kernel.org permalink
Embed this notice
Krzysztof Kozlowski (krzk@social.kernel.org)'s status on Tuesday, 19-Nov-2024 23:39:35 JST Krzysztof Kozlowski

Last year, for each of six Linux kernel releases - v6.7, v6.8 ... v6.12 - I was topping the list of most active contributors. This consistency led to a more interesting stat: I am one of the most active Linux kernel contributors for this period (and I don't count Kent here as he just dropped stuff out of tree... and then developed things to his own tree without review or mailing list collaboration) with upstream 1339 commits.

I am however more proud of another impact I made: I am one of the most active reviewers of the last one year of Linux kernel development. Reviewing takes a lot of time, a lot of iterations, a lot of patience, a lot of template answers and results with only "some" of reviewed-by credit going to Linux kernel git history. Yet here I am: ~1000 reviewed-by credits for last year v6.7 - v6.12 Linux kernel.
In conversation about 5 days ago from social.kernel.org permalink
Attachments
1. Untitled attachment
  https://media.social.kernel.org/media/4bb4f8221707add31f3811071ba1a62462ff2811d4ecce89d7991dfbda505f67.png
2. Untitled attachment
  https://media.social.kernel.org/media/c6b47c50bf24f694421cc0a159a5e04d086820c9f78f1353459f7bddad968b19.png
Embed this notice
Krzysztof Kozlowski (krzk@social.kernel.org)'s status on Monday, 04-Nov-2024 17:41:22 JST Krzysztof Kozlowski
in reply to
@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 by 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.

In conversation about 20 days ago from gnusocial.jp permalink
Embed this notice
Krzysztof Kozlowski (krzk@social.kernel.org)'s status on Monday, 04-Nov-2024 17:04:16 JST Krzysztof Kozlowski
in reply to
- TUXEDO Computers
- Thorsten Leemhuis (acct. 1/4)
@kernellogger @tuxedocomputers I wonder what is actually worse for customers: crappy driver release from vendors just for open-source compliance or this pseudo-open-source-move from Tuxedo which effectively blocks any community from upstreaming this code.

Let's recap what Tuxedo said:
> We do not plan to relicense the tuxedo-drivers project directly as we want to keep control of the upstream pacing,

This is absolutely terrible move, restricting community and customers from working upstream. Kind of what proprietary company would like to do... Bleh, just choose other laptops.

In conversation about 20 days ago from social.kernel.org permalink
Embed this notice
Krzysztof Kozlowski (krzk@social.kernel.org)'s status on Tuesday, 23-Jan-2024 23:28:25 JST Krzysztof Kozlowski

Linux v6.8-rc1 comes with new document describing coding style for DTS (Devicetree sources):
https://www.kernel.org/doc/html/latest/devicetree/bindings/dts-coding-style.html

This marks the end of many unwritten rules, varying between subsystems and maintainers. At least, like with every coding style document, in theory. :)
In conversation about 10 months ago from social.kernel.org permalink
Attachments
1. No result found on File_thumbnail lookup.
  
  Devicetree Sources (DTS) Coding Style — The Linux Kernel documentation

Public

Notices by Krzysztof Kozlowski (krzk@social.kernel.org)

User actions

Following 0

Followers 1

Groups 0

Statistics

Feeds