Linux Kernel Summit discussions
 help / color / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Matthew Wilcox <willy@infradead.org>, Greg KH <greg@kroah.com>,
	Christoph Lameter <cl@gentwo.de>, Theodore Ts'o <tytso@mit.edu>,
	Jiri Kosina <jikos@kernel.org>,
	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, 28 May 2021 18:55:20 +0300
Message-ID: <YLESaAP/Bu95ACvU@pendragon.ideasonboard.com> (raw)
In-Reply-To: <15419fa8e5c0047327395387b28c09d775b35a55.camel@HansenPartnership.com>

Hi James,

On Fri, May 28, 2021 at 08:44:23AM -0700, James Bottomley wrote:
> On Fri, 2021-05-28 at 18:31 +0300, Laurent Pinchart wrote:
> > On Fri, May 28, 2021 at 08:27:44AM -0700, James Bottomley wrote:
> [...]
> > > Well, I'm not going to get into a debate over the effectiveness of
> > > the current vaccines.  I will say that all conferences have to now
> > > recognize that a sizeable proportion of former attendees will have
> > > fears about travelling and therefore remote components are going to
> > > be a fixture of conferences going forward.
> > > 
> > > However, while we should accommodate them, we can't let these fears
> > > override people willing to take the risk and meet in person.
> > 
> > The interesting question is how we'll make sure that those people
> > will not be de facto excluded from the community, or end up as
> > second-class citizens.
> 
> Before the pandemic, there was a small contingent who refused to fly
> for various reasons.  We did sort of accommodate that by rotating the
> conference to Europe where more people could come in by train (like
> they did in Lisbon) but we didn't govern the whole conference by trying
> to make aerophobes first class citizens.
> 
> The bottom line is that as long as enough people are willing to meet in
> person and in-person delivers more value that remote (even though we'll
> try to make remote as valuable as possible) we should do it.   We
> should not handicap the desires of the one group by the fears of the
> other because that's a false equality ... it's reducing everyone to the
> level of the lowest common denominator rather than trying to elevate
> people.

This should take into account the size of each group, and I believe even
then it won't be a binary decision, there's lots of variation in local
situations, creating more than just two groups of coward/careless people
(let's not debate those two words if possible, they're not meant to
insult anyway, but to emphasize that there are more categories). While I
believe that in-person meetings will become the norm again in a
reasonably near future, 2021 seems a bit premature to me.

If we want to brainstorm alternate solutions, an option could be to
split the monolithic conference location into a small set of
geographically distributed groups (assuming local travel would be easier
and generally seen as an accepted solution compared to intercontinental
travels) and link those through video conferencing. I don't have high
hopes that this would be feasible in practice given the increase in
efforts and costs to organize multiple locations in parallel, but maybe
something interesting could come out of discussing different options.

-- 
Regards,

Laurent Pinchart

  reply index

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-19 15:28 Theodore Ts'o
2021-04-28 10:29 ` Jiri Kosina
2021-04-30 21:48   ` Theodore Ts'o
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 [this message]
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-10 20:12                   ` Konstantin Ryabitsev
2021-06-10 18:55               ` Linus Torvalds
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=YLESaAP/Bu95ACvU@pendragon.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=cl@gentwo.de \
    --cc=greg@kroah.com \
    --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 \
    --cc=tytso@mit.edu \
    --cc=willy@infradead.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

Linux Kernel Summit discussions

Archives are clonable:
	git clone --mirror https://lore.kernel.org/ksummit/0 ksummit/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ksummit ksummit/ https://lore.kernel.org/ksummit \
		ksummit@lists.linux.dev
	public-inbox-index ksummit

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/dev.linux.lists.ksummit


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git