ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Dave Airlie <airlied@gmail.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: ksummit <ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] CHANGE OF PLAN: Maintainer Summit will be in Edinburgh
Date: Sat, 8 Sep 2018 08:13:54 +1000	[thread overview]
Message-ID: <CAPM=9tz7uwj7QZVdSZ8URAY0ZkwrX1ACdat39vsuaJXeytFLfQ@mail.gmail.com> (raw)
In-Reply-To: <20180906185043.GA14607@thunk.org>

On Fri, 7 Sep 2018 at 04:50, Theodore Y. Ts'o <tytso@mit.edu> wrote:
>
> Last Friday (just before Labor Day) I learned that Linus had gotten
> confused about when and where the Maintainer's Summit was going to be
> held this year.  And most unfortunately, he has already scheduled a
> family vacation overlapping with the week of the Maintainer's Summit.
>
> Over the weekend, I've been conferring with folks from the Linux
> Foundation, Linus, and the Maintainer's / Kernel Summit program
> committee.  We explored a lot of options, but ultimately there were
> only two choices that were workable:
>
> 1)  Have the Maintainer's Summit in Vancouver, without Linus.
>
> 2)  Move the Maintainer's Summit to Edinburgh, with Linus.
>
> Curiously enough, Linus suggested option #1.  And while holding the
> Maintainer's Summit without Linus might be an interesting experiment,
> ultimately, the Program Committee had a strong consensus that moving
> it Summit to Edinburgh was the better option.
>
> This means that the Maintainer's Summit will take place in Edinburgh,
> on Monday afternoon, October 22nd.  As a reminder, the Maintainer's
> Summit is an invite-only workshop, with ~30 people attending.  The
> focus of the Maintainer's Summit is process and development issues,
> *not* technical issues.
>
> The Kernel Summit track will still be held in Vancouver alongside
> Plumber's.  Technical discussions will take place there; we simply
> won't have the time, or necessarily, the right people, to have
> technical discussions at the Maintainer's Summit.
>
> This means that people who get an invite to the Maintainer's Summit
> may have an extra trip this year (some may have been planning to
> attend OSS EU anyway).  For those for which this will be an extra
> trip, I apologize in advance.  Maintainer's Summit invitees will still
> receive a free (non-transferrable) registration to the Linux Plumber's
> Conference.
>
> This also means that the process by which we issue invites to the
> Maintainer's Summit is going to have been significantly accelerated.
> So if you have any ideas for the Maintainer's Summit Topics, please
> chime in soon!

Way to go team :-)

I was unsure on making to Vancouver, getting to Edinburgh in a shorter
timeframe is even more unlikely at this stage, surprisingly I prefer
being married to hanging out with Linus.

3) Have it next year. It's all ticking along nicely, and we probably
won't make major changes anyways.

I assume this means the Monday at LPC is empty now, unless we can
propose a use for it, or a mini-summit no Linus.

Dave.

      reply	other threads:[~2018-09-07 22:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-06 18:50 Theodore Y. Ts'o
2018-09-07 22:13 ` Dave Airlie [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='CAPM=9tz7uwj7QZVdSZ8URAY0ZkwrX1ACdat39vsuaJXeytFLfQ@mail.gmail.com' \
    --to=airlied@gmail.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=tytso@mit.edu \
    /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