linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Jiri Kosina <jikos@kernel.org>
Cc: ksummit@lists.linux.dev, linux-kernel@vger.kernel.org,
	linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-mm@kvack.org, netdev@vger.kernel.org,
	linux-arch@vger.kernel.org, linux-api@vger.kernel.org
Subject: Re: Maintainers / Kernel Summit 2021 planning kick-off
Date: Fri, 30 Apr 2021 17:48:55 -0400	[thread overview]
Message-ID: <YIx7R6tmcRRCl/az@mit.edu> (raw)
In-Reply-To: <nycvar.YFH.7.76.2104281228350.18270@cbobk.fhfr.pm>

On Wed, Apr 28, 2021 at 12:29:52PM +0200, Jiri Kosina wrote:
> On Mon, 19 Apr 2021, Theodore Ts'o wrote:
> 
> > This year, the Maintainers and Kernel Summit is currently planned to
> > be held in Dublin, Ireland, September 27 -- 29th.  
> 
> Given the fact that OSS is being relocated from Dublin to Washington [1], 
> is Kernel Summit following that direction?
> 
> [1] https://www.linuxfoundation.org/en/press-release/the-linux-foundation-announces-open-source-summit-embedded-linux-conference-2021-will-move-from-dublin-ireland-to-seattle-washington/

Apologies for the delay in responding; I wasiting for the LPC to post
its announcement that the LPC will be going 100% virtual:

   https://www.linuxplumbersconf.org/blog/2021/index.php/2021/04/30/linux-plumbers-goes-fully-virtual/

As the LPC planning committee stated,

   "Unfortunately, the safety protocols imposed by event venues in the
   US require masks and social distancing which make it impossible to
   hold the interactive part of Plumbers (the Microconferences)."

The Maintainer's Summit is even more interactive and discussion
focused than most of the Microconferences.  In addition, for the last
few years, the Kernel Summit is run as a track at the LPC.  As a
result, both the Maintainer's and Kernel Summit will be held virtually
this year, using the LPC infrastructure, and will not be colocated
with OSS to Seattle.  We'll make sure the dates (plus some buffer for
travel) won't overlap to avoid creating conflicts for those who are
planning to attend OSS in Seattle.

I know we're all really hungry for some in-person meetups and
discussions, but at least for LPC, Kernel Summit, and Maintainer's
Summit, we're going to have to wait for another year,

Cheers,

					- Ted

  reply	other threads:[~2021-04-30 21:49 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-19 15:28 Maintainers / Kernel Summit 2021 planning kick-off Theodore Ts'o
2021-04-28 10:29 ` Jiri Kosina
2021-04-30 21:48   ` Theodore Ts'o [this message]
2021-05-27 13:23     ` Christoph Lameter
2021-05-27 13:29       ` Greg KH
2021-05-28 14:58         ` James Bottomley
2021-05-28 15:11           ` Matthew Wilcox
2021-05-28 15:27             ` James Bottomley
2021-05-28 15:31               ` Laurent Pinchart
2021-05-28 15:44                 ` James Bottomley
2021-05-28 15:55                   ` Laurent Pinchart
2021-05-28 16:04                     ` James Bottomley
2021-05-28 16:31                       ` Laurent Pinchart
2021-05-28 15:42             ` Toke Høiland-Jørgensen
2021-06-09 10:37           ` David Hildenbrand
2021-06-09 19:23             ` James Bottomley
2021-06-11 10:58               ` Enrico Weigelt, metux IT consult
2021-06-10 18:07             ` Enrico Weigelt, metux IT consult
2021-06-10 18:23               ` Konstantin Ryabitsev
2021-06-10 18:39                 ` Laurent Pinchart
2021-06-10 19:26                   ` Steven Rostedt
2021-06-10 19:55                     ` Shuah Khan
2021-06-10 20:02                       ` Steven Rostedt
2021-06-10 20:20                         ` Matthew Wilcox
2021-06-10 20:31                           ` Steven Rostedt
2021-06-10 22:43                       ` Toke Høiland-Jørgensen
2021-06-11  2:59                         ` Willy Tarreau
2021-06-11  9:13                           ` Mauro Carvalho Chehab
2021-06-11  9:51                             ` Willy Tarreau
2021-06-18 13:46                       ` Laurent Pinchart
2021-06-18 14:11                         ` James Bottomley
2021-06-18 14:17                           ` Steven Rostedt
2021-06-18 14:28                           ` Geert Uytterhoeven
2021-06-18 14:32                             ` Steven Rostedt
2021-06-18 14:45                               ` Laurent Pinchart
2021-06-18 14:58                               ` Geert Uytterhoeven
2021-06-18 15:14                                 ` Matthew Wilcox
2021-06-18 15:23                                   ` Steven Rostedt
2021-06-18 15:29                                   ` Geert Uytterhoeven
2021-06-18 15:34                                     ` Steven Rostedt
2021-06-18 15:36                                       ` Steven Rostedt
2021-06-18 16:33                                       ` Mauro Carvalho Chehab
2021-06-18 15:58                               ` Mark Brown
2021-06-18 16:45                                 ` Mauro Carvalho Chehab
2021-06-18 14:46                             ` James Bottomley
2021-06-22 22:33                         ` Shuah Khan
2021-06-22 22:59                           ` Laurent Pinchart
2021-06-22 23:33                             ` Shuah Khan
2021-06-22 23:57                               ` Shuah Khan
2021-06-23  0:06                                 ` Laurent Pinchart
2021-06-23  0:15                                 ` Steven Rostedt
2021-06-10 18:55               ` Linus Torvalds
2021-06-18 13:34             ` Enrico Weigelt, metux IT consult
2021-06-18 14:08               ` Steven Rostedt
2021-06-11 11:10           ` David Howells
2021-06-15 18:23             ` Enrico Weigelt, metux IT consult
2021-06-15 18:30               ` Matthew Wilcox
2021-06-15 18:34                 ` Konstantin Ryabitsev
2021-06-15 18:40                 ` Laurent Pinchart

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=YIx7R6tmcRRCl/az@mit.edu \
    --to=tytso@mit.edu \
    --cc=jikos@kernel.org \
    --cc=ksummit@lists.linux.dev \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=netdev@vger.kernel.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).