From: Mingcong Bai <jeffbai@aosc.io>
To: WangYuli <wangyuli@uniontech.com>
Cc: gregkh@linuxfoundation.org, patches@lists.linux.dev,
nikita@trvn.ru, ink@jurassic.park.msu.ru, shc_work@mail.ru,
richard.henderson@linaro.org, mattst88@gmail.com,
linux-alpha@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, fancer.lancer@gmail.com,
linux-hwmon@vger.kernel.org, dmaengine@vger.kernel.org,
xeb@mail.ru, netdev@vger.kernel.org, s.shtylyov@omp.ru,
linux-ide@vger.kernel.org, serjk@netup.ru, aospan@netup.ru,
linux-media@vger.kernel.org, ddrokosov@sberdevices.ru,
linux-iio@vger.kernel.org, v.georgiev@metrotek.ru,
linux-mips@vger.kernel.org, ntb@lists.linux.dev,
linux-renesas-soc@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-spi@vger.kernel.org, dushistov@mail.ru,
manivannan.sadhasivam@linaro.org, conor.dooley@microchip.com,
linux-fpga@vger.kernel.org, tsbogend@alpha.franken.de,
hoan@os.amperecomputing.com, geert@linux-m68k.org,
wsa+renesas@sang-engineering.com
Subject: Re: [PATCH] MAINTAINERS: Remove some entries due to various compliance requirements.
Date: Wed, 23 Oct 2024 15:32:50 +0800 [thread overview]
Message-ID: <a08dc31ab773604d8f206ba005dc4c7a@aosc.io> (raw)
In-Reply-To: <A74519B4332040FA+20241023063058.223139-1-wangyuli@uniontech.com>
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
next prev parent reply other threads:[~2024-10-23 7:33 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2024101835-tiptop-blip-09ed@gregkh>
2024-10-23 6:30 ` [PATCH] MAINTAINERS: Remove some entries due to various compliance requirements WangYuli
2024-10-23 7:32 ` Mingcong Bai [this message]
2024-10-23 8:09 ` [PATCH] Revert "MAINTAINERS: Remove some entries due to various compliance requirements." Kexy Biscuit
2024-10-23 8:26 ` Nikita Travkin
2024-10-23 8:35 ` WangYuli
2024-10-23 9:04 ` Mingcong Bai
2024-10-23 9:28 ` Tonghao Zhang
2024-10-23 10:27 ` Nikita Shubin
2024-10-23 14:47 ` Lance Yang
2024-10-23 15:03 ` Yangyu Chen
2024-10-23 15:04 ` Sergio Paracuellos
2024-10-23 16:22 ` Yao Zi
2024-10-23 16:51 ` Tor Vic
2024-10-23 17:45 ` Linus Torvalds
2024-10-23 18:56 ` Phillip Susi
2024-10-23 19:15 ` Peter Cai
2024-10-23 19:19 ` Linus Torvalds
2024-10-23 19:28 ` Peter Cai
2024-10-24 21:01 ` Mikhail Novosyolov
2024-10-25 7:11 ` Nikolay Kichukov
2024-10-23 19:50 ` Tor Vic
2024-10-23 22:14 ` NotYourFox
2024-10-24 7:11 ` Integral
[not found] ` <20241024095708.189649-1-isage.dna@gmail.com>
2024-10-24 15:41 ` Andy Shevchenko
2024-10-24 16:15 ` Guenter Roeck
2024-10-24 17:13 ` Ivan Epifanov
2024-10-24 17:18 ` Guenter Roeck
2024-10-24 17:38 ` Ivan Epifanov
2024-10-24 17:28 ` Nopempele N
2024-10-24 17:07 ` Ivan Epifanov
2024-10-24 17:45 ` Sergey Shtylyov
2024-10-25 18:39 ` Tor Vic
[not found] ` <20241024140353.384881-1-vladimir_putin_rus@kremlin.ru>
[not found] ` <20241024140353.384881-2-vladimir_putin_rus@kremlin.ru>
2024-10-30 12:48 ` lore.kernel.org getting senile ? [WAS: [PATCH 1/2] MAINTAINERS: Remove Huawei due to compilance requirements metux
[not found] ` <64ef261c-82d0-4fad-ba8a-562f247340fb@metux.net>
2024-10-24 15:33 ` [PATCH] Revert "MAINTAINERS: Remove some entries due to various compliance requirements." Andy Shevchenko
2024-10-23 8:26 ` [PATCH] MAINTAINERS: Remove some entries due to various compliance requirements Mingcong Bai
2024-10-23 9:38 ` WangYuli
2024-10-23 9:53 ` Jiaxun Yang
2024-10-23 10:10 ` Mingcong Bai
2024-10-23 10:22 ` Nikita Shubin
2024-10-24 11:32 Jensen Huang
2024-10-24 12:34 ` 陈寒彤
-- strict thread matches above, loose matches on Subject: below --
2024-10-23 10:55 jisralbasha
2024-10-23 9:50 Anna Antonenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a08dc31ab773604d8f206ba005dc4c7a@aosc.io \
--to=jeffbai@aosc.io \
--cc=aospan@netup.ru \
--cc=conor.dooley@microchip.com \
--cc=ddrokosov@sberdevices.ru \
--cc=dmaengine@vger.kernel.org \
--cc=dushistov@mail.ru \
--cc=fancer.lancer@gmail.com \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=hoan@os.amperecomputing.com \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mattst88@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nikita@trvn.ru \
--cc=ntb@lists.linux.dev \
--cc=patches@lists.linux.dev \
--cc=richard.henderson@linaro.org \
--cc=s.shtylyov@omp.ru \
--cc=serjk@netup.ru \
--cc=shc_work@mail.ru \
--cc=tsbogend@alpha.franken.de \
--cc=v.georgiev@metrotek.ru \
--cc=wangyuli@uniontech.com \
--cc=wsa+renesas@sang-engineering.com \
--cc=xeb@mail.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).