Conversation
krzk

Krzysztof Kozlowski

Oh, the amazing construction of silosed Business Units of big corporations. When interacting with Open Source communities, one team in some Business Unit of that company cannot learn from the past experience of some other team, because they are silosed. Separate. Thus this team makes the same mistakes other teams already did. However Open Source community sees it differently - one company sending contributions with the same mistakes. It is always okay to make a mistake, but making the same mistake again and again, is a bit waste of our time.
1
0
1
krzk

Krzysztof Kozlowski

Reply to @krzk
One could imagine that the team doing contribution, maybe for the first time for them, will ask for review the older, experienced team from other Business Unit. You know, not to make the same mistakes. But no! It cannot! BUs are separate. However Open Source reviewers are not "separate" and unfortunately receive that stuff to review, with the same mistakes as the company did before.
1
0
0
krzk

Krzysztof Kozlowski

Reply to @krzk
Edited 1 year ago
I am getting more and more picky on this... Why? Because it is waste of our resources. Resources of both community and company. If one team learnt the hard way how to format patches and send them to LKML, why the heck other team has to go through the same learning process? Why reviewer has to explain again and again - `git format-patch -v3 -10 && scripts/get_maintainer.pl v3-00* && git send-email v3-00*`?
1
0
1
krzk

Krzysztof Kozlowski

Reply to @krzk
Edited 1 year ago
It actually damages the company's public image, because for the Open Source community there are no separate Business Units. We all look at them as one entity.
1
0
1
About social.kernel.org

Terms of service

  1. Please do not use this service in violation of the Linux Kernel Code of Conduct. Doing so will result in your account suspension with the referral of the matter to the CoC committee.

  2. "Repeating"/"boosting" someone else's status on this platform will be treated as endorsement and will fall under rule #1.

  3. You are encouraged to use this platform to promote your work on the Linux Kernel, but there is no restriction on permitted topics (with the exception of anything covered by #1 above).

  4. There is no requirement to post in English, but it should be considered the primary language of communication on this platform.

Privacy notice

The admins of this service have access to all posted statuses. They aren't looking, but if it's something they shouldn't know about, then you should not post it on this platform.

Please see the Linux Foundation Privacy Policy, which applies to this platform as well.

Getting your own account

If you would like an account on this instance, please check that the following applies to you:

  • You are listed in MAINTAINERS or CREDITS

  • OR: You have a kernel.org account or email address

  • OR: You have a long and established history of involvement with the Linux Kernel

If the above is true and you agree with the Terms of Service and Privacy Notice listed above, please use these instructions to request an account: