From: Nikolay Kichukov <nikolay@oldum.net>
To: Mikhail Novosyolov <m.novosyolov@rosalinux.ru>,
torvalds@linux-foundation.org
Cc: 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, gregkh@linuxfoundation.org,
hoan@os.amperecomputing.com, ink@jurassic.park.msu.ru,
jeffbai@aosc.io, kexybiscuit@aosc.io,
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,
peter@typeblog.net, richard.henderson@linaro.org,
s.shtylyov@omp.ru, serjk@netup.ru, shc_work@mail.ru,
torvic9@mailbox.org, tsbogend@alpha.franken.de,
v.georgiev@metrotek.ru, wangyuli@uniontech.com,
wsa+renesas@sang-engineering.com, xeb@mail.ru, rms@gnu.org,
campaigns@fsf.org
Subject: Re: [PATCH] Revert "MAINTAINERS: Remove some entries due to various compliance requirements."
Date: Fri, 25 Oct 2024 10:11:27 +0300 [thread overview]
Message-ID: <3ace1329d4ef99b87780d0ef07db179d27d04d44.camel@oldum.net> (raw)
In-Reply-To: <20241024210120.4126-1-m.novosyolov@rosalinux.ru>
On Fri, 2024-10-25 at 00:01 +0300, Mikhail Novosyolov wrote:
> Linus, Greg,
>
> First of all thanks to you for taking by far not the most harmful
> actions to achieve what your lawyers very kindly asked you to do.
>
> Unfortunately, already a lot of highly qualified people have started
> thinking that you acted very badly. Of course, there are questions
> like why removed maintainers were not properly notified and did not
> receive any additional explanations, but, to my mind, it is useless to
> try to find 100% justice -- it is not possible. Overton windows has
> been opened a bit more.
>
> Usually the first contribution is much harder to make then the
> following ones. A big problem here is that now many people even will
> not try to contribute to the Linux kernel and other open source
> projects: their pride for themselves, their homeland, their colleagues
> has been severely hurt (we are ready to fight for all that).
>
> It is not clear what to do with this problem. Any ideas?
>
> I am sure that people from any country and of any nationality will
> have similar feelings if you act with them or their colleagues in a
> similar way.
>
> Thanks to people who were not afraid to say something against this
> action. Chinese, Latin American, African and other people probably
> understand that they may be the next ones to be dropped from
> maintainers. Hope that we will not have to form another Linux kernel
> upstream one day...
>
> I am sorry that you have to read a lot of text from people who you
> call trolls -- it is hard to keep calm.
>
> You know, you have really made it much harder to motivate people to
> contribute into the kernel. There is such problem among developers of
> hardware that they do not feel comfortable enough to show their code,
> for example because they think that it is not perfect. Let’s take
> Baikal Electronics. They do publish their kernel code, but in a form
> of tarballs without git. They slowly, but constantly worked on
> contributing support of their hardware into the upstream kernel,
> fixing not Baikal-related bugs by the way. One day someone told them
> that “we are not comfortable with accepting your patches”. And they
> stopped their work on upstream. Now that man has been removed from
> maintainers of previously contributed code (code for not Russian
> hardware, by the way).
>
> What do I suggest to do? Well, I don’t know, but I do not see direct
> legal reasons why doing this was required and why patches from Baikal
> could not be accepted (the fact that I do not see does not mean that
> they do not exist, but please show them). Politicians and activists
> can be shown a finger in some places, by both developers and lawyers,
> at least to prevent them from being too ambitious, when they decide to
> break something working next time... But maybe I do not know something
> about truly democratic regimes :-)
>
> Thanks for reading.
>
Hi folks,
I also do not consider what's happened here as normal. The maintainers
removal stands against the key principles and values of our GNU/Linux
communities and the FOSS ideology. Values and ideas most of us have been
protecting and advocating for since we can remember!
This hurt so badly! Really. This is betrial.
Even if this is now reverted, or the upstream kernel is forked and a new
upstream kernel repository is elected, the history of it will remain and
haunt us all.
Turned out our beloved and "free" as in freedom kernel has been
compromised by compliance to a government.
But this is the Linux kernel, how could this have happened?! It is used,
improved and copied all over the world, not just one country! Why did we
let this happen?
This is a precedent that tells everybody what can come next, due to
"compliance" reasons the kernel could receive code produced by a
government institution that serves not the Linux community, but the
governement.
Surely it is not just me thinking towards what can change so we never
again have to comply to a government of a country when fighting for
freedom!
FSF, any comments on this?
Resist!
+rms and fsf
Thanks,
Nikolay
next prev parent reply other threads:[~2024-10-25 7:11 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
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 [this message]
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=3ace1329d4ef99b87780d0ef07db179d27d04d44.camel@oldum.net \
--to=nikolay@oldum.net \
--cc=aospan@netup.ru \
--cc=campaigns@fsf.org \
--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=m.novosyolov@rosalinux.ru \
--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=peter@typeblog.net \
--cc=richard.henderson@linaro.org \
--cc=rms@gnu.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