From: Greg KH <gregkh@linuxfoundation.org>
To: Dave Hansen <dave.hansen@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, corbet@lwn.net, sashal@kernel.org,
ben@decadent.org.uk, tglx@linutronix.de, labbott@redhat.com,
andrew.cooper3@citrix.com, tsoni@codeaurora.org,
keescook@chromium.org, tony.luck@intel.com,
linux-doc@vger.kernel.org, dan.j.williams@intel.com
Subject: Re: [PATCH 4/4] Documentation/process: add transparency promise to list subscription
Date: Wed, 11 Sep 2019 16:51:37 +0100 [thread overview]
Message-ID: <20190911155137.GC14152@kroah.com> (raw)
In-Reply-To: <20190910172652.4FFF6CA3@viggo.jf.intel.com>
On Tue, Sep 10, 2019 at 10:26:52AM -0700, Dave Hansen wrote:
>
> From: Dave Hansen <dave.hansen@linux.intel.com>
>
> Transparency is good. It it essential for everyone working under an
> embargo to know who is involved and who else is a "knower". Being
> transparent allows everyone to always make informed decisions about
> ongoing participating in a mitigation effort.
>
> Add a step to the subscription process which will notify existing
> subscribers when a new one is added.
As I don't run the mailing list software here, I don't know how much of
a burden adding this support to it would be, so I'll defer to Thomas.
We could just have something like "All new people need to announce
themselves" rule like many other private mailing lists have at times.
That would put the burden on the new person once, instead of the list
manager for every time a new person is added.
thanks,
greg k-h
next prev parent reply other threads:[~2019-09-11 15:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 17:26 [PATCH 0/4] Documentation/process: embargoed hardware issues additions Dave Hansen
2019-09-10 17:26 ` [PATCH 1/4] Documentation/process: Volunteer as the ambassador for Intel Dave Hansen
2019-09-10 17:26 ` [PATCH 2/4] Documentation/process: describe relaxing disclosing party NDAs Dave Hansen
2019-09-11 10:11 ` Sasha Levin
2019-09-11 14:11 ` Dave Hansen
2019-09-11 15:44 ` Greg KH
2019-09-11 16:09 ` Dave Hansen
2019-09-25 8:29 ` [PATCH] Documentation/process: Clarify disclosure rules Thomas Gleixner
2019-09-25 15:53 ` Dave Hansen
2019-09-29 10:42 ` [PATCH 2/4] Documentation/process: describe relaxing disclosing party NDAs Greg KH
2019-09-10 17:26 ` [PATCH 3/4] Documentation/process: soften language around conference talk dates Dave Hansen
2019-09-11 15:49 ` Greg KH
2019-09-10 17:26 ` [PATCH 4/4] Documentation/process: add transparency promise to list subscription Dave Hansen
2019-09-11 15:51 ` Greg KH [this message]
2019-09-16 8:30 ` Thomas Gleixner
2019-09-11 11:54 ` [PATCH 0/4] Documentation/process: embargoed hardware issues additions Greg KH
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=20190911155137.GC14152@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andrew.cooper3@citrix.com \
--cc=ben@decadent.org.uk \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=keescook@chromium.org \
--cc=labbott@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=tsoni@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.