public inbox for ntb@lists.linux.dev
 help / color / mirror / Atom feed
From: Peter Cai <peter@typeblog.net>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Tor Vic <torvic9@mailbox.org>
Cc: Kexy Biscuit <kexybiscuit@aosc.io>,
	jeffbai@aosc.io, gregkh@linuxfoundation.org,
	wangyuli@uniontech.com, aospan@netup.ru,
	conor.dooley@microchip.com, ddrokosov@sberdevices.ru,
	dmaengine@vger.kernel.org, dushistov@mail.ru,
	fancer.lancer@gmail.com, geert@linux-m68k.org,
	hoan@os.amperecomputing.com, ink@jurassic.park.msu.ru,
	linux-alpha@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-fpga@vger.kernel.org,
	linux-gpio@vger.kernel.org, linux-hwmon@vger.kernel.org,
	linux-ide@vger.kernel.org, linux-iio@vger.kernel.org,
	linux-media@vger.kernel.org, linux-mips@vger.kernel.org,
	linux-renesas-soc@vger.kernel.org, linux-spi@vger.kernel.org,
	manivannan.sadhasivam@linaro.org, mattst88@gmail.com,
	netdev@vger.kernel.org, nikita@trvn.ru, ntb@lists.linux.dev,
	patches@lists.linux.dev, richard.henderson@linaro.org,
	s.shtylyov@omp.ru, serjk@netup.ru, shc_work@mail.ru,
	tsbogend@alpha.franken.de, v.georgiev@metrotek.ru,
	wsa+renesas@sang-engineering.com, xeb@mail.ru
Subject: Re: [PATCH] Revert "MAINTAINERS: Remove some entries due to various compliance requirements."
Date: Wed, 23 Oct 2024 15:15:17 -0400	[thread overview]
Message-ID: <e25fb178-39fa-4b75-bdc8-a2ec5a7a1bf6@typeblog.net> (raw)
In-Reply-To: <CAHk-=whNGNVnYHHSXUAsWds_MoZ-iEgRMQMxZZ0z-jY4uHT+Gg@mail.gmail.com>

Hi there,

Not a maintainer, but I have made several bug reports using this email 
address. At least 1 reasonably-sized patch is also currently under 
review in the networking mailing list, along with people from several 
American corporations, so hopefully you won't automatically assume this 
email came from a "Russian troll" account.

Ok. With that out of the way, if you still want to bother reading, 
here's why, in the most un-provocative tone possible, why your comments 
_completely_ miss the point why people are upset:

On 10/23/24 1:45 PM, Linus Torvalds wrote:
> Ok, lots of Russian trolls out and about. >
> It's entirely clear why the change was done, it's not getting
> reverted, and using multiple random anonymous accounts to try to
> "grass root" it by Russian troll factories isn't going to change
> anything.

Yes. Everybody who has more than 1 brain cell knows, in general, "why". 
The point was never to ask for the obvious response.

People are upset because no reference to _exactly which compliance 
requirement_ resulted in the removal of these maintainers. No 
open-source project can live outside of a political entity, but that is 
not the reason why "obviously" can be used to write off such a change.

Even just stating "we were contacted by <...> but details are under NDA" 
is a **much** better response than "due to various compliance 
requirements". No one is saying the LF or the Linux kernel should be 
outside of politics. That's impossible. But it _is_ possible to run the 
project based on _transparency_ and _honesty_ instead of "why can't you 
see the obvious".

> And FYI for the actual innocent bystanders who aren't troll farm
> accounts - the "various compliance requirements" are not just a US
> thing.

Again -- are you under any sort of NDA not to even refer to a list of 
these countries?

> If you haven't heard of Russian sanctions yet, you should try to read
> the news some day.  And by "news", I don't mean Russian
> state-sponsored spam.

Before calling out community members who raised legit concerns about 
procedural transparency, maybe it is worth doing a quick fact-check. 
There are a lot of suspicious looking `.ru` emails in this thread, but 
they are not who first raised the concern. The revert patch was sent out 
by someone at aosc.io. Look up who they actually are -- and before you 
assume "state-sponsored spam" just because of the language of the 
website, maybe you can also spend more than 1 second to check where the 
website is even actually located.

> As to sending me a revert patch - please use whatever mush you call
> brains. I'm Finnish. Did you think I'd be *supporting* Russian
> aggression? Apparently it's not just lack of real news, it's lack of
> history knowledge too.

I hope that either this comment wasn't written by the real Linus 
Torvalds, or that Linus was not under his best judgement when this email 
was sent. Because just like anyone who reads the news would know about 
Russian aggression, anyone who knows anything about politics should also 
be able to understand that individuals and their states are different 
concepts.

If these maintainers are associated with the Russian state, this should 
be cited as the reason for their removal. And you know what? Most people 
wouldn't have any problem with it. And then you can say "we are not 
supporting Russian aggression" with confidence. But this is **not** what 
was done.

I seriously hope that Linus Torvalds would have known better.

Thanks,
Peter.

  parent reply	other threads:[~2024-10-23 19:25 UTC|newest]

Thread overview: 42+ 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
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: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 [this message]
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]           ` <20241024095339.GA32487@imap.altlinux.org>
2025-10-01 10:11             ` what about CoC? (was: [PATCH] Revert "MAINTAINERS: Remove some entries due to various compliance requirements.") Michael Shigorin
2025-10-03 15:48               ` what about CoC? Alexander Lobakin
2025-10-03 16:45                 ` Michael Shigorin
     [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-25  8:46 [PATCH] Revert "MAINTAINERS: Remove some entries due to various compliance requirements." thomas superb

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=e25fb178-39fa-4b75-bdc8-a2ec5a7a1bf6@typeblog.net \
    --to=peter@typeblog.net \
    --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=jeffbai@aosc.io \
    --cc=kexybiscuit@aosc.io \
    --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=torvalds@linux-foundation.org \
    --cc=torvic9@mailbox.org \
    --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