The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Jiaxun Yang" <jiaxun.yang@flygoat.com>
To: linux-kernel@vger.kernel.org, conduct@kernel.org,
	security@kernel.org, cve@kernel.org, linux-doc@vger.kernel.org,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	shuah@kernel.org, lee@kernel.org, sashal@kernel.org,
	"Jonathan Corbet" <corbet@lwn.net>
Subject: Re: Concerns over transparency of informal kernel groups
Date: Fri, 25 Oct 2024 16:36:35 +0100	[thread overview]
Message-ID: <0ac6833c-8e7e-458f-a7c8-833901b3e990@app.fastmail.com> (raw)
In-Reply-To: <73b8017b-fce9-4cb1-be48-fc8085f1c276@app.fastmail.com>



在2024年10月25日十月 下午4:15，Jiaxun Yang写道：
> Dear Linux Community Members,
>
> Over recent events, I've taken a closer look at how our community's 
> governance
> operates, only to find that there's remarkably little public 
> information available
> about those informal groups. With the exception of the Linux kernel 
> hardware security
> team, it seems none of these groups maintain a public list of members 
> that I can
> easily find.

Just to correct, people notified me that a membership list for Code of
Conduct Committee is available at kernel.org [1] instead of in source tree.

[...]

Thanks

[1]: https://kernel.org/code-of-conduct.html

-- 
- Jiaxun

  reply	other threads:[~2024-10-25 15:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-25 15:15 Concerns over transparency of informal kernel groups Jiaxun Yang
2024-10-25 15:36 ` Jiaxun Yang [this message]
2024-10-26 11:05 ` Krzysztof Kozlowski
2024-10-26 13:16   ` Jiaxun Yang
2024-10-26 14:56 ` Theodore Ts'o
2024-10-26 16:33   ` Jiaxun Yang
2024-10-26 17:54     ` Willy Tarreau
2024-10-27  8:40       ` Jiaxun Yang
2024-10-27  1:14     ` Theodore Ts'o
2024-10-27 10:26       ` Jiaxun Yang
2024-10-26 17:38 ` Yongmin

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=0ac6833c-8e7e-458f-a7c8-833901b3e990@app.fastmail.com \
    --to=jiaxun.yang@flygoat.com \
    --cc=conduct@kernel.org \
    --cc=corbet@lwn.net \
    --cc=cve@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=lee@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sashal@kernel.org \
    --cc=security@kernel.org \
    --cc=shuah@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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