From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: ksummit@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: Maintainers / Kernel Summit 2021 planning kick-off
Date: Thu, 10 Jun 2021 16:12:36 -0400 [thread overview]
Message-ID: <20210610201236.gvxxmgl6ubjsbc3h@nitro.local> (raw)
In-Reply-To: <YMJcdbRaQYAgI9ER@pendragon.ideasonboard.com>
(Trimming the huge CC list)
On Thu, Jun 10, 2021 at 09:39:49PM +0300, Laurent Pinchart wrote:
> The topic of how to best organize hybrid events to maximize
> inclusiveness for remote participants is more interesting to me. LPC did
> an amazing job last year with the fully remote setup, but a hybrid setup
> brings new challenges. One issue I've previously experienced in hybrid
> setups, especially for brainstorming-type discussions, was that on-site
> attendees can very quickly break out conversations in small groups (it's
> an issue for fully on-site events too).
As a (high-functioning) introvert, I'd say that a lot of it depends not so
much on the on-site/off-site nature of participation, but on individual
communication preferences. I've presented quite a bit at conferences, and, to
me, "brainstorming-type discussions" never really happen post-presentation,
largely because being in a spotlight makes me uncomfortable and I generally
try to slink away.
I suggest that something that would help is providing information on where to
ask questions in an informal setting. For example, add the following on the
last slide of your presentation:
Thank you!
Join the discussion:
1. Mailing list: foo@lists.example.com
2. IRC: #foochan on exampleirc.com
3. Matrix: #foochan:example.com
4. My email: foo@example.com
This gives enough options for folks to ask questions whether they are in the
real-life audience or attending online. Listing both your individual email and
a group chat option will help bridge many cultural divides -- some people will
feel intimidated asking a question directly (especially if you are a luminary
in your field) and will prefer to address a group. Others will feel
intimidated addressing a group (what if my question is stupid) and will prefer
to address you directly.
> Session leads should be aware of the need to ensure even more than usual
> that all speakers use microphones. I don't think we need to go as far as
> specific training on these topics, but emphasizing the importance of
> moderation would be useful in my opinion.
I think with most sessions being recorded, people are already well conditioned
to use microphones. I try to at least always repeat the question being asked
if I notice that the person asking it isn't using a mic.
> There will always be more informal discussions between on-site participants.
> After all, this is one of the benefits of conferences, by being all together
> we can easily organize ad-hoc discussions. This is traditionally done by
> finding a not too noisy corner in the conference center, would it be useful
> to have more break-out rooms with A/V equipment than usual ?
I'm generally of the opinion that we should split conferences from hackathons,
anyway.
- conferences are great for finding about cool new things happening in your
field, and work great online where there is no limit on how many people can
join the stream; if the presentation is not what you thought it was going to
be, switching to a different video stream is dramatically cheaper than
getting out of the dark room to find a different presentation.
- hackathons are great for getting things done and meeting up with folks you
rarely get to see in real life -- and they work well as on-site, multi-site
or hybrid events.
For example, the maintainer summit is a "hackathon", even if there is no
actual code hacking done. The thing being hackathoned is the development
process itself and general direction of things. The LinuxCon is for sure a
conference and generally has little tangible value other than a pretext to get
your employer to pay for the trip. :)
So, perhaps more frequent but smaller events around narrower topics as opposed
to huge colocated events? I do appreciate that this is more difficult for
organizers, but perhaps it would result in more tangible benefits?
-K
next prev parent reply other threads:[~2021-06-10 20:12 UTC|newest]
Thread overview: 60+ 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
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 20:12 ` Konstantin Ryabitsev [this message]
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=20210610201236.gvxxmgl6ubjsbc3h@nitro.local \
--to=konstantin@linuxfoundation.org \
--cc=ksummit@lists.linux.dev \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@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).