From: Dave Hansen <dave.hansen@intel.com>
To: Theodore Tso <tytso@mit.edu>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
Steven Rostedt <rostedt@goodmis.org>,
Monika Masciangelo <mmasciangelo@linuxfoundation.org>,
"tech-board-discuss@lists.linuxfoundation.org"
<tech-board-discuss@lists.linuxfoundation.org>,
"contact@linuxplumbersconf.org" <contact@linuxplumbersconf.org>
Subject: Re: [lpc-contact] Memorial for Dan Williams
Date: Fri, 11 Sep 2026 09:02:25 -0700 [thread overview]
Message-ID: <1f9f5bb8-1806-4301-b25a-5abee23ac0c3@intel.com> (raw)
In-Reply-To: <aqQiHr3O3ZpxYbqX@mit.edu>
On 9/11/26 08:48, Theodore Tso wrote:
...
> If not, there will always be some people who might be uncomfortable if
> there is active A/V; even if we don't record it, someone on the remote
> end could. That seems relatively unlikely to me, but it's more about
> what other people might feel/perceive/fear. Could it still be
> worthwhile?
>
> One compromise might be that we don't broadcast the BBB link, but we
> only make it available to people who explicitly ask ahead of time.
>
> Dave, what do you think?
Doing a BBB session, but keeping the link mostly private sounds like a
good compromise to me. We'd basically only share the link with people we
trust.
next prev parent reply other threads:[~2026-09-11 16:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 18:41 Memorial for Dan Williams Steven Rostedt
2026-09-10 19:42 ` Kees Cook
2026-09-10 19:49 ` Dave Hansen
2026-09-10 19:49 ` Steven Rostedt
[not found] ` <CANoLq29+nRWwTYZPZUmfD6mkyERAEarnVJpd3k6=RBgrJ9RS1A@mail.gmail.com>
2026-09-11 12:44 ` Steven Rostedt
2026-09-11 12:53 ` [lpc-contact] " James Bottomley
2026-09-11 14:23 ` Dave Hansen
2026-09-11 15:48 ` Theodore Tso
2026-09-11 16:02 ` Dave Hansen [this message]
2026-09-11 16:50 ` Jonathan Corbet
2026-09-14 15:46 ` Steven Rostedt
2026-09-22 14:03 ` Dave Hansen
2026-09-23 8:23 ` Steven Rostedt
2026-09-11 12:55 ` Dave Hansen
2026-09-11 13:02 ` [lpc-contact] " James Bottomley
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=1f9f5bb8-1806-4301-b25a-5abee23ac0c3@intel.com \
--to=dave.hansen@intel.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=contact@linuxplumbersconf.org \
--cc=mmasciangelo@linuxfoundation.org \
--cc=rostedt@goodmis.org \
--cc=tech-board-discuss@lists.linuxfoundation.org \
--cc=tytso@mit.edu \
/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.