All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Tso" <tytso@mit.edu>
To: Dave Hansen <dave.hansen@intel.com>
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 11:48:48 -0400	[thread overview]
Message-ID: <aqQiHr3O3ZpxYbqX@mit.edu> (raw)
In-Reply-To: <c1c71d57-0418-4186-9e83-fba29c6db311@intel.com>

On Fri, Sep 11, 2026 at 07:23:29AM -0500, Dave Hansen wrote:
> On 9/11/26 05:53, James Bottomley wrote:
> > Actually that's just a technical detail about the way remote A/V works,
> > so every remote A/V tool technically records.  However, we could spin
> > up an ephemeral BBB instance and shred it after the event to ensure
> > there are no traces left if that would make people happier?
> 
> I'm not super worried about it either way. Basically as long as a
> recording doesn't end up on YouTube, I'm OK with it.

This should be Dave's call, but my personal feeling is that if there
are some critically important people who can only attend remotely
(including possibly some of Dan's family if some or all of them can't
travel) we should definitely do BBB.

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?

						- ted

  reply	other threads:[~2026-09-11 15:52 UTC|newest]

Thread overview: 12+ 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 [this message]
2026-09-11 16:02           ` Dave Hansen
2026-09-11 16:50             ` Jonathan Corbet
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=aqQiHr3O3ZpxYbqX@mit.edu \
    --to=tytso@mit.edu \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=contact@linuxplumbersconf.org \
    --cc=dave.hansen@intel.com \
    --cc=mmasciangelo@linuxfoundation.org \
    --cc=rostedt@goodmis.org \
    --cc=tech-board-discuss@lists.linuxfoundation.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.