netdev - Re: [PATCH] MAINTAINERS: Remove some entries due to various compliance requirements.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <a08dc31ab773604d8f206ba005dc4c7a@aosc.io>
Date: Wed, 23 Oct 2024 15:32:50 +0800
From: Mingcong Bai <jeffbai@...c.io>
To: WangYuli <wangyuli@...ontech.com>
Cc: gregkh@...uxfoundation.org, 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.

Greetings all,

在 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.

> It should be CC'd everyone who might need to be aware of this change, 
> including the removed maintainers, other maintainers on the subsystem, 
> and the subsystem's mailing list.
> 
> To ensure transparency.

This patch is one such instance where we find ourselves questioning the 
legitimacy and indeed, the feasibility, of an international, open, and 
open source project. Vagueness breeds distrust.

It's not difficult to deduce what the "various compliance requirements" 
are and I'm sure Greg is aware of this. The Linux Foundation, if 
interested in continuing their governance role over the Linux kernel, 
should be ready to explain themselves over this decision. Greg and 
Linus, I'm not sure if I'm ready to believe that this is supposed to be 
a political show - but if this is the case, please leave the ground for 
the Foundation - they should be the one responsible and receiving the 
scrutiny (or insult, as I'm sure many - myself included - find this 
patch insulting).

So I repeat - call the decision-makers out and ask for their 
explanation.

Best Regards,
Mingcong Bai