Message-ID: <418359de-e084-47f9-9090-7980e41661e0@flygoat.com>
Date: Wed, 23 Oct 2024 10:53:09 +0100
From: Jiaxun Yang <jiaxun.yang@...goat.com>
To: Mingcong Bai <jeffbai@...c.io>, WangYuli <wangyuli@...ontech.com>,
 gregkh@...uxfoundation.org
Cc: patches@...ts.linux.dev, nikita@...n.ru, ink@...assic.park.msu.ru,
 shc_work@...l.ru, richard.henderson@...aro.org, mattst88@...il.com,
 linux-alpha@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
 fancer.lancer@...il.com, linux-hwmon@...r.kernel.org,
 dmaengine@...r.kernel.org, xeb@...l.ru, netdev@...r.kernel.org,
 s.shtylyov@....ru, linux-ide@...r.kernel.org, serjk@...up.ru,
 aospan@...up.ru, linux-media@...r.kernel.org, ddrokosov@...rdevices.ru,
 linux-iio@...r.kernel.org, v.georgiev@...rotek.ru,
 linux-mips@...r.kernel.org, ntb@...ts.linux.dev,
 linux-renesas-soc@...r.kernel.org, linux-gpio@...r.kernel.org,
 linux-spi@...r.kernel.org, dushistov@...l.ru,
 manivannan.sadhasivam@...aro.org, conor.dooley@...rochip.com,
 linux-fpga@...r.kernel.org, tsbogend@...ha.franken.de,
 hoan@...amperecomputing.com, geert@...ux-m68k.org,
 wsa+renesas@...g-engineering.com
Subject: Re: [PATCH] MAINTAINERS: Remove some entries due to various
 compliance requirements.



On 2024/10/23 09:26, Mingcong Bai wrote:
> No, no, no. Nuh, uh.
>
> Greg has unfortunately decided to respond in private over a matter 
> that by no means should be glossed over. Here below is our conversation:

I can't believe a senior maintainer is breaking our agreed netiquette 
[1], but that's happening.

> 在 2024-10-23 15:55，Greg KH 写道：
[...]
>
> Request declined. Your response is now public knowledge (and hey, if 
> this is not by your will, my apologies). Again, this matter requires 
> public response.
>
>> 在 2024-10-23 14:30，WangYuli 写道： Although this commit has been 
>> merged, it's still important to know the
>> specific reason (or even an example) that triggered this change for
>> everyone here, right?
>>
>> And those maintainers who have been removed should be notified.
>> Seconded.
>
> Sorry, but that's not how this is allowed to work.  Please contact your
> company lawyers if you have any questions about this.  And this only
> affects maintainers, as you aren't listed in the MAINTAINERS file, there
> should not be any issue, but again, contact your company if you have any
> questions as they know what is going on.

I think there are no regulations on earth preventing itself from being 
referenced.
Even if the regulation prevents further communication with affected bodies,
the wider community still deserves an explanation.

As a person with M entries I found this behavior appalling. It shakes mutual
trust between maintainers, as we all assumed that patches being applied are
well scrutinized.

Besides, many of us are working on kernel as hobbyist  in a personal 
capacity.
That means we don't have access to lawyers, especially US one. While I 
understand
corporate participants may be the majority of the community, please 
don't leave
hobbyists behind!

I've had some interactions with some of people being removed here, and I 
would
say they are all brilliant individuals. It's  really sad to see them 
being turned away :-(

>
> Just *wink* if you were compelled into this.
^ It sounds unprofessional to me.

Thanks
- Jiaxun

[1]: https://people.kernel.org/tglx/notes-about-netiquette-qw89
>
>> thanks,
>>
>> greg k-h
>
> Best Regards,
> Mingcong Bai
>

Download attachment "OpenPGP_0xC111949073FC0F67.asc" of type "application/pgp-keys" (16944 bytes)

Download attachment "OpenPGP_signature.asc" of type "application/pgp-signature" (237 bytes)

Powered by blists - more mailing lists