linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Lobakin <aleksander.lobakin@intel.com>
To: Michael Shigorin <mike@altlinux.org>,
	Michael Shigorin <mike@altlinux.ru>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Tor Vic <torvic9@mailbox.org>, 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: what about CoC?
Date: Fri, 3 Oct 2025 17:48:40 +0200	[thread overview]
Message-ID: <87371abc-e43f-4afb-83d0-b9a04fc015c0@intel.com> (raw)
In-Reply-To: <20251001101148.GA30625@imap.altlinux.org>

From: Michael Shigorin <mike@altlinux.org>
Date: Wed, 1 Oct 2025 13:11:48 +0300

> On Thu, Oct 24, 2024 at 12:53:39PM +0300, I wrote
>> It's not about the patch but rather about the attitude;
>> Documentation/process/code-of-conduct-interpretation.rst:
>>
>> "regardless of ... ethnicity, ... nationality, ... race"

Lemme necro-post as well and insert my 2 coins here, for those who still
yell "it's all about ethnicity!!1".

No it's not. It's about companies that sponsor the war or are a part of it.

I wouldn't exaggerate if I say that at least a good half of Russian IT
and HW is dual-purpose / gov-owned if not most of it.

You want to talk about poor Baikal? It was under sanctions even back in
2013 before the Crimea events for being dual-purpose and ARM refused to
give them the license, so they fell back to MIPS.

Most, if not all, Russian Linux distributions are used by the govs AND
military.

So banning the `.ru` domain etc. on LKML would be like 90% precise shot
and 10% collateral damage which is a fair ratio nevertheless.
I'd rather reject a patch than get a rocket in my face powered by this
patch. Even if it's "focused on what is best for the community".

Instead of citing the Code of Conduct and all that stuff, refer to the
kernel documentation about the international restrictions for certain
HW/countries/purposes (including dual).

>> "Focusing on what is best for the community"
>>
>> "Examples of unacceptable behavior ... insulting/derogatory
>> comments ... Public or private harassment"
>>
>> Get back to single-standard integrity for yor own's sake.
Thanks,
Olek

  reply	other threads:[~2025-10-03 15:49 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: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]           ` <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               ` Alexander Lobakin [this message]
2025-10-03 16:45                 ` what about CoC? 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

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=87371abc-e43f-4afb-83d0-b9a04fc015c0@intel.com \
    --to=aleksander.lobakin@intel.com \
    --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=mike@altlinux.org \
    --cc=mike@altlinux.ru \
    --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;
as well as URLs for NNTP newsgroup(s).