ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>, ksummit@lists.linux.dev
Subject: Re: [MAINTAINER SUMMIT] Prep?
Date: Mon, 13 Nov 2023 15:34:27 -0500	[thread overview]
Message-ID: <ZVKIU1igkgV8rSFi@mit.edu> (raw)
In-Reply-To: <871qct4ghi.fsf@meer.lwn.net>

On Mon, Nov 13, 2023 at 12:10:01PM -0700, Jonathan Corbet wrote:
> Linus Torvalds <torvalds@linux-foundation.org> writes:
> 
> > I didn't ask Jon before, so here goes: Jonathan?  Would you be willing
> > to take some input from people, and just scrub the names off it, and
> > forward some kind of word cloud of issues (or honestly, just the
> > otherwise unedited emails) to me?
> 
> Yes, I would be happy to do that.  I've gotten one email already;
> anybody else with something to pass on is encouraged to send it my way.

Thanks, Jon!  I was going to send out an anonymous Google Form that
invited people to send up to 3 things that they were going well, and 3
things that was making them unhappy, in preparation for a "Are
Maintainers Happy?" session (which is a spin on the "Is Linus Happy"
session that we've sometimes had in the past), but since Jon has
volunteered, lets stick with that.

I'd also like to ask attendees to think about specific proposals to
address Maintainer Burnout.  Given the very long thread about
Maintainer Burnout, we've scheduled 60 minutes on the schedule for it.

The current draft agenda is attached below.

					- Ted


			Maintainer's Summit
			 Omni Richmond Hotel
			 November 16, 2023

8:00  Hot breakfast and morning refreshments
9:00  Welcome and Agenda Bashing
9:30  Trust and Maintenace of File Systems
10:00 Next steps for Rust -- are we ready to commit?
10:30 Break
11:00 Maintainer Burnout
11:30 Maintainer Burnout (continued)
12:00 Lunch
1:30  Maintainers Support Group
2:00  Are Maintainers Happy?
2:30  Group Photograph
3:00  Break
3:30  Free time
6:00  Transportation loads for dinner

      reply	other threads:[~2023-11-14  5:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-13 18:49 [MAINTAINER SUMMIT] Prep? Linus Torvalds
2023-11-13 19:10 ` Jonathan Corbet
2023-11-13 20:34   ` Theodore Ts'o [this message]

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=ZVKIU1igkgV8rSFi@mit.edu \
    --to=tytso@mit.edu \
    --cc=corbet@lwn.net \
    --cc=ksummit@lists.linux.dev \
    --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;
as well as URLs for NNTP newsgroup(s).