From: Linus Torvalds <torvalds@linux-foundation.org>
To: Thomas Gleixner <tglx@linutronix.de>,
James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: David Miller <davem@davemloft.net>,
ksummit <ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] "Maintainer summit" invitation discussion
Date: Tue, 23 May 2017 13:34:29 -0700 [thread overview]
Message-ID: <CA+55aFwJravpoxKS78kbn-yD5Rw7OeMjzKjTc3kCpaVX0sv2=w@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1705232043450.2409@nanos>
On Tue, May 23, 2017 at 11:47 AM, Thomas Gleixner <tglx@linutronix.de> wrote:
>
> I'm probably late, but I would like to add myself to that list. As RT (and
> upstream) maintainer I'm pretty involved in large scale overhauls and
> restructuring which is often enough a process issue.
So I certainly have no objection, but I think we should strive to have
something approaching a "process" for the picking.
I assume there's an actual official KS organizing committee, although
I have no idea who would be on it, except for the presumed usual
suspects (ie Ted and James).
And I would suggest that in order to make it easier on them, _and_ to
actually also have an agenda in place when we show up in October,
people who want to nominate themselves (or somebody else, for that
matter), actually write a little blurb about what they want to bring
up for the agenda.
That would help both the selection committee and the agenda.
In the "what to bring up" blurb, I'd really suggest not just bringing
up a problem, but mentioning a possible real constructive (perhaps
partial) solution too, as part of why that particular person should be
at the KS and why it's worth discussing. We don't want it to be a
"this is a problem I have" kvetching session.
We know part of the agenda already, it was discussed earlier in the
thread. We've had the eternal issue about non-responsive maintainers
and how to try to improve that (whether it's group maintainership or
"fall-through-the-cracks" people or whatever). And I think we've
discussed regression tracking pretty much every year too.
But wouldn't it be good if the KS committee could basically get both a
suggested agenda item and a person selection hint at the same time?
Would there be some convenient way to submit those? We're all email
people, so perhaps just an email with something to easily search for
in the subject line. Just to the list, or who are the actual KS point
men?
On Tue, May 23, 2017 at 12:29 PM, James Bottomley
<James.Bottomley@hansenpartnership.com> wrote:
>
> I'm happy to try to wrangle interesting and highly technical vendor
> talks. I believe the current time plan for the maintainer summit is
> half a day (is this correct?), so I propose we do vendor talks in the
> other half of the day. That way people who aren't interested can take
> the afternoon or morning (depending where people want it in the
> timetable) off to see Prague.
Sounds reasonable by me. Assuming we can get _good_ vendor talks.
Linus
next prev parent reply other threads:[~2017-05-23 20:34 UTC|newest]
Thread overview: 135+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 18:59 Linus Torvalds
2017-04-18 19:50 ` Takashi Iwai
2017-04-18 20:13 ` Linus Torvalds
2017-04-18 20:21 ` Jiri Kosina
2017-04-18 20:36 ` Takashi Iwai
2017-04-18 20:29 ` Takashi Iwai
2017-04-18 20:33 ` Laura Abbott
2017-04-18 21:15 ` Mauro Carvalho Chehab
2017-04-19 22:36 ` Jonathan Corbet
2017-04-19 22:41 ` Jiri Kosina
2017-04-19 23:36 ` Josh Triplett
2017-04-19 23:51 ` Jiri Kosina
2017-04-20 1:04 ` Josh Triplett
2017-04-20 7:38 ` Jani Nikula
2017-04-20 5:23 ` Christoph Hellwig
2017-04-20 13:33 ` James Bottomley
2017-04-20 14:40 ` Alexey Dobriyan
2017-04-20 14:52 ` Ingo Molnar
2017-04-20 14:47 ` Jonathan Corbet
2017-04-20 15:34 ` James Bottomley
2017-04-20 11:25 ` Mauro Carvalho Chehab
2017-04-19 15:37 ` Doug Ledford
2017-04-19 16:18 ` Linus Torvalds
2017-04-19 16:24 ` Doug Ledford
2017-04-19 18:11 ` Justin Forbes
2017-04-19 21:52 ` Geert Uytterhoeven
2017-04-19 18:21 ` Laura Abbott
2017-04-20 8:31 ` Jani Nikula
2017-04-20 12:35 ` Mark Brown
2017-04-20 13:01 ` Jani Nikula
2017-04-21 8:41 ` Alexandre Belloni
2017-04-21 14:46 ` David Miller
2017-04-20 8:17 ` Jani Nikula
2017-04-20 10:59 ` Greg Kroah-Hartman
2017-04-20 12:22 ` Jani Nikula
2017-04-20 13:03 ` Greg Kroah-Hartman
2017-04-20 14:49 ` Mark Brown
2017-04-19 19:25 ` Laurent Pinchart
2017-04-19 19:40 ` Linus Torvalds
2017-04-19 19:45 ` Jens Axboe
2017-04-19 19:50 ` Laurent Pinchart
2017-04-19 19:55 ` James Bottomley
2017-04-20 8:26 ` Daniel Vetter
2017-04-20 13:25 ` James Bottomley
2017-04-25 16:02 ` Bart Van Assche
2017-04-25 16:38 ` Guenter Roeck
2017-04-25 16:56 ` Mark Brown
2017-04-26 3:47 ` Bart Van Assche
2017-04-26 8:39 ` Geert Uytterhoeven
2017-04-26 14:21 ` Mark Brown
2017-04-26 14:51 ` David Miller
2017-04-26 15:15 ` Mark Brown
2017-04-26 8:42 ` Dan Carpenter
2017-04-26 13:58 ` Martin K. Petersen
2017-04-26 14:15 ` Andrew Lunn
2017-04-26 15:42 ` Martin K. Petersen
2017-04-26 14:31 ` James Bottomley
2017-04-26 14:34 ` Jiri Kosina
2017-04-26 14:43 ` James Bottomley
2017-04-27 9:06 ` Jani Nikula
2017-04-27 10:41 ` Lee Jones
2017-04-27 11:02 ` Hannes Reinecke
2017-04-27 14:17 ` James Bottomley
2017-04-28 0:24 ` Rafael J. Wysocki
2017-04-27 15:40 ` Wolfram Sang
2017-04-26 15:02 ` Bart Van Assche
2017-04-26 15:25 ` James Bottomley
2017-04-26 15:36 ` Mark Brown
2017-04-19 20:14 ` Josh Triplett
2017-04-19 21:30 ` Laurent Pinchart
2017-04-20 5:44 ` Julia Lawall
2017-04-20 8:54 ` Laurent Pinchart
2017-04-19 19:58 ` Konstantin Ryabitsev
2017-04-19 20:20 ` Jiri Kosina
2017-04-18 20:00 ` Dave Airlie
2017-04-18 20:29 ` Laurent Pinchart
2017-04-18 20:38 ` Daniel Vetter
2017-04-18 20:56 ` Linus Torvalds
2017-04-18 21:39 ` Daniel Vetter
2017-04-20 19:02 ` Mark Brown
2017-04-18 20:06 ` Serge E. Hallyn
2017-04-18 20:11 ` Greg Kroah-Hartman
2017-04-18 20:21 ` Linus Torvalds
2017-04-25 15:09 ` Chris Mason
2017-04-19 0:22 ` Stephen Rothwell
2017-04-19 13:35 ` Shuah Khan
2017-04-19 20:20 ` James Bottomley
2017-04-19 20:27 ` Jiri Kosina
2017-04-20 10:24 ` Mauro Carvalho Chehab
2017-04-21 8:51 ` Alexandre Belloni
2017-04-21 8:55 ` Julia Lawall
2017-04-21 8:59 ` Wolfram Sang
2017-04-21 14:45 ` Mauro Carvalho Chehab
2017-04-21 10:34 ` Michael Ellerman
2017-04-21 15:06 ` Mauro Carvalho Chehab
2017-04-21 23:37 ` James Bottomley
2017-04-20 16:01 ` Dan Williams
2017-04-21 11:07 ` Michael Ellerman
2017-04-21 17:06 ` Mauro Carvalho Chehab
2017-04-21 23:19 ` Bjorn Helgaas
2017-04-19 20:26 ` Arnd Bergmann
2017-04-20 8:53 ` Daniel Vetter
2017-04-20 11:30 ` Arnd Bergmann
2017-04-20 13:46 ` Daniel Vetter
2017-04-24 14:02 ` Olof Johansson
2017-04-24 16:17 ` Linus Walleij
2017-04-24 17:29 ` Olof Johansson
2017-04-24 17:58 ` Mark Brown
2017-04-25 9:10 ` Lee Jones
2017-04-29 21:00 ` Daniel Vetter
2017-04-29 21:39 ` James Bottomley
2017-04-30 12:45 ` Mark Brown
2017-04-30 19:12 ` Olof Johansson
2017-05-02 8:09 ` Lee Jones
2017-04-20 19:26 ` Mark Brown
2017-04-21 11:03 ` Alexandre Belloni
2017-04-24 13:14 ` Nicolas Ferre
2017-04-19 21:05 ` Andy Lutomirski
2017-04-19 21:32 ` Linus Torvalds
2017-05-23 17:58 ` Linus Torvalds
2017-05-23 18:17 ` Randy Dunlap
2017-05-23 18:47 ` Thomas Gleixner
2017-05-23 20:34 ` Linus Torvalds [this message]
2017-05-23 19:29 ` James Bottomley
2017-05-24 3:34 ` David Miller
2017-05-24 4:55 ` Linus Torvalds
2017-04-21 0:35 ` Rafael J. Wysocki
2017-09-20 14:45 ` Doug Ledford
2017-09-20 15:07 ` James Bottomley
2017-09-20 15:22 ` Doug Ledford
2017-09-20 15:31 ` James Bottomley
2017-09-20 15:58 ` Doug Ledford
2017-09-20 22:55 ` Theodore Ts'o
2017-09-21 9:33 ` Leon Romanovsky
2017-09-21 4:54 ` James Morris
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='CA+55aFwJravpoxKS78kbn-yD5Rw7OeMjzKjTc3kCpaVX0sv2=w@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=davem@davemloft.net \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=tglx@linutronix.de \
/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