From: Michael Matz <matz@suse.de>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: Petr Mladek <pmladek@suse.com>,
Joe Lawrence <joe.lawrence@redhat.com>,
Jiri Kosina <jikos@kernel.org>, Miroslav Benes <mbenes@suse.cz>,
Nicolai Stange <nstange@suse.com>,
Jason Baron <jbaron@akamai.com>, Gabriel Gomes <gagomes@suse.com>,
Alice Ferrazzi <alice.ferrazzi@gmail.com>,
Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>,
ulp-devel@opensuse.org, live-patching@vger.kernel.org
Subject: Re: Live patching MC at LPC2020?
Date: Wed, 1 Jul 2020 13:13:38 +0000 (UTC) [thread overview]
Message-ID: <alpine.LSU.2.20.2007011304210.9982@wotan.suse.de> (raw)
In-Reply-To: <20200630214550.cbli6oex4xskwdjp@treble>
Hello,
On Tue, 30 Jun 2020, Josh Poimboeuf wrote:
> On Thu, Jun 25, 2020 at 08:59:43AM +0200, Petr Mladek wrote:
> > On Tue 2020-03-31 16:52:04, Joe Lawrence wrote:
> > It seems that there is interest into sharing/discussing some topics.
> > The question is whether is has to be under the LPC even umbrella.
> >
> > Advantages of LPC:
> >
> > + well defined date
> > + more attendees (ARM people, Steven Rostedt ;-)
> > + access to some powerful video conference tool
> > + access to another LPC content
> > + support for the conference in the long term
> >
> >
> > Advantages of self-organized event:
> >
> > + less paperwork?
> > + cheaper?
> > + only interested people invited
> > + date after summer holidays
> > + more time for the discussion
> >
> > I am in the favor of self organized event. For me, LPC is much less
> > interesting without the personal contact and hallway conversations.
> > All the LPC date is not ideal for me.
>
> I'd prefer LPC proper, as it would be easier (infrastructure is already
> taken care of) and more inclusive (in the past we often got good
> feedback from outside the direct livepatch community). And it's only
> $50 US.
Yeah, I think having more attendees would be valuable.
> But to be honest I have doubts about the usefulness of any online
> conference, so either way may be equally useless ;-)
Indeed. OTOH our fellow openSUSE guys seemed to have held a fairly
successful virtual summit earlier this year with some in-development
virtual-conferencing software that does more than just video/audio
streaming ( https://requiredmagic.com/roundtable/ ). In particular the
possibility to have interactive Q&A with the presenter during and after
the allotted talk slot seemed to have made up for hallway discussions.
Maybe that's a viable way. (I personally wasn't at the virtual summit to
know for sure, but the experience report from some of them was quite
positive; I know nothing about the conferencing software of LPC)
Ciao,
Michael.
prev parent reply other threads:[~2020-07-01 13:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 13:20 Live patching MC at LPC2020? Jiri Kosina
2020-03-30 14:01 ` Michael Matz
2020-03-31 20:52 ` Joe Lawrence
2020-04-08 10:22 ` Kamalesh Babulal
2020-04-14 10:03 ` Alice ferrazzi
2020-06-25 6:59 ` Petr Mladek
2020-06-27 5:43 ` Alice
2020-06-30 21:45 ` Josh Poimboeuf
2020-07-01 13:13 ` Michael Matz [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=alpine.LSU.2.20.2007011304210.9982@wotan.suse.de \
--to=matz@suse.de \
--cc=alice.ferrazzi@gmail.com \
--cc=gagomes@suse.com \
--cc=jbaron@akamai.com \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@redhat.com \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=nstange@suse.com \
--cc=pmladek@suse.com \
--cc=ulp-devel@opensuse.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).