From: Pavel Snajdr <snajpa@snajpa.net>
To: michaeljpwoods@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 4.19-rc4 released, an apology, and a maintainership note
Date: Tue, 18 Sep 2018 03:30:38 +0200 [thread overview]
Message-ID: <260205ec45d097fb037f71ae42e7b69e@snajpa.net> (raw)
In-Reply-To: <93424bb0-180e-71ff-f0d6-602caa2d5883@gmail.com>
On 2018-09-17 23:09, Michael Woods wrote:
>
> The Code of Conflict was perfectly fine. Whomever convinced you to add
> the Code of Conduct was convincing you to give control over to a
> social justice initiative that has no interest in the kernel's core
> function or reason for existence.
>
Hi Michael,
and how about if we viewed the new Code of Conduct as about the same
thing as BitKeeper was for the development process?
It was not perfect, but wass *something* for a start. And I believe that
Linus will probably come back with a Git of CoC, or something in that
fasion.
I've been always looking up to the guys leading major community projects
and how they go about things - and I think, that most of the bad
fall-out in them is caused by insanely high expectations - firstly from
the leader themselves, and secondly from others as well.
/snajpa
P.S.: this is my first "contribution" to LKML, I hope to start sending
up some of my very prototype work soon for discussion, regarding the
Cgroup subsystem ID allocation & limits - and subsequently, start a
discussion about getting Linux to do better OS-level containers (ie.
those, which have a "look&feel of a real VM" from the admin's
perspective).
We started our organization (vpsFree.org) on top of OpenVZ patch set and
are now working to get vanilla up to the task of replacing the venerable
2.6.32-based OpenVZ 6 Linux-like thing. The new Code of Conduct is a
guarantee for us, that we won't be laughed out of the room and that our
members won't be demotivated to contribute upstream - if we can all
agree to be nice on each other; yet we still need you guys to tell us,
when we're trying stupid things or going about things the wrong way, in
some way that we will notice & can learn from.
If I understand the context correctly, the previous "regime" could be
the culprit, at least to some extent, why still don't have the VM
look&feel-having containers with vanilla. So I'm just really trying to
say, that I'm really excited about the signal this change has sent.
next prev parent reply other threads:[~2018-09-18 1:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-16 19:22 Linus Torvalds
2018-09-16 21:42 ` [...] " Adam Borowski
2018-09-16 23:59 ` Moritz Obermeier
2018-09-17 0:18 ` Linux 4.19-rc4 released, " Rene Herman
2018-09-17 0:20 ` [...] " Andy Isaacson
2018-09-17 0:23 ` Linux 4.19-rc4 released, " Rene Herman
2018-09-17 6:57 ` opal hart
2018-09-17 7:57 ` […] " Martin Steigerwald
2018-09-17 8:53 ` Martin Steigerwald
2018-09-30 12:09 ` Re: Linux 4.19-rc4 released, " lkcl
2018-09-30 14:07 ` Martin Steigerwald
2018-09-30 16:27 ` Luke Kenneth Casson Leighton
2018-09-17 12:58 ` Guenter Roeck
2018-09-17 17:09 ` Joe Perches
2018-09-17 21:09 ` Michael Woods
2018-09-18 1:30 ` Pavel Snajdr [this message]
2018-09-21 22:13 ` Michael Woods
2018-10-04 14:57 ` Eric W. Biederman
2018-10-08 15:29 ` Enrico Weigelt, metux IT consult
2018-10-08 13:54 ` Enrico Weigelt, metux IT consult
2018-10-08 16:36 ` Enrico Weigelt, metux IT consult
2018-09-17 2:15 Luke Kenneth Casson Leighton
2018-09-18 2:10 ` Luke Kenneth Casson Leighton
2018-09-30 11:47 ` Luke Kenneth Casson Leighton
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=260205ec45d097fb037f71ae42e7b69e@snajpa.net \
--to=snajpa@snajpa.net \
--cc=linux-kernel@vger.kernel.org \
--cc=michaeljpwoods@gmail.com \
/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
Powered by JetHome