All of lore.kernel.org
 help / color / mirror / Atom feed
* [Ksummit-discuss] Next steps and plans for the 2017 Maintainer and Kernel Summits
@ 2017-06-14 13:29 ` Theodore Ts'o
  0 siblings, 0 replies; 5+ messages in thread
From: Theodore Ts'o @ 2017-06-14 13:29 UTC (permalink / raw)
  To: ksummit-discuss, linux-kernel

After talking to Linus about what the next steps should be, here's the
plan that we've come up with.  The following people drawn from Linus's core
list will be extended invitations to the Maintainers Summit.

David Miller
Greg KH
Daniel Vetter
Ingo Molnar
Arnd Bergmann
Andrew Morton
Michael Ellerman
Takashi Iwai
Linus Torvalds
Ben Hutchings
Stephen Rothwell
Ted Ts'o
Shuah Kahn
James Bottomley

A mini-program committee composed of James Bottomley, Shuah Kahn, Greg
KH, and myself will pick enough names to bring the total number of
invited attendees to 30 for the Maintainers Summit, using the criteria
which Linus has described.

We will use the rest of names that Linus had mentioned as being part
of his secondary list to preseed the list of people to be considered.
People who suggest topics that should be discussed on the Maintainer's
summit will be added to the list.  Please prefix [MAINTAINERS SUMMIT]
to the subject line, and remember that we only have a half-day, and
they should be appropriate for the Maintainer's summit --- that is,
they should be focused on the development process.

For technical topics, we will have a "Kernel Summit" that will be work
much like the Technical Session days last year.  The technical
sessions will be run in parallel with the Open Source Summit Europe,
and will be open to anyone who registered with the OSS Europe.  The
goal will be to provide a forum to discuss specific technical issues
that would be easier to resolve in person than over e-mail.  The
program committee will also consider "information sharing" topics if
they are clearly of interest to the wider development community (i.e.,
advanced training in topics that would be useful for maintainers).

To suggest a topic for the Kernel Summit, please tag your e-mail with
[TECH TOPIC].  As before, please use a separate e-mail for each topic,
and send the topic suggestions to:

	ksummit-discuss@lists.linuxfoundation.org

We will also be reserving roughly half the slots to be scheduled on
the day of the conference, but if you know are interested in
organizing a discussion around a topic, or giving a presentation on
some topic that would be of interest to kernel developers, please send
them as soon as possible.  For each topic that is accepted and
submitted before July 8th, we will give a free admission to OSS Europe
/ Kernel Summit.  All others will have to pay the normal registration
fee.

If you were not subscribed on to the kernel-discuss mailing list from
last year (or if you had removed yourself after the kernel summit),
you can subscribe to the discuss list using mailman:

   https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Next steps and plans for the 2017 Maintainer and Kernel Summits
@ 2017-06-14 13:29 ` Theodore Ts'o
  0 siblings, 0 replies; 5+ messages in thread
From: Theodore Ts'o @ 2017-06-14 13:29 UTC (permalink / raw)
  To: ksummit-discuss, linux-kernel

After talking to Linus about what the next steps should be, here's the
plan that we've come up with.  The following people drawn from Linus's core
list will be extended invitations to the Maintainers Summit.

David Miller
Greg KH
Daniel Vetter
Ingo Molnar
Arnd Bergmann
Andrew Morton
Michael Ellerman
Takashi Iwai
Linus Torvalds
Ben Hutchings
Stephen Rothwell
Ted Ts'o
Shuah Kahn
James Bottomley

A mini-program committee composed of James Bottomley, Shuah Kahn, Greg
KH, and myself will pick enough names to bring the total number of
invited attendees to 30 for the Maintainers Summit, using the criteria
which Linus has described.

We will use the rest of names that Linus had mentioned as being part
of his secondary list to preseed the list of people to be considered.
People who suggest topics that should be discussed on the Maintainer's
summit will be added to the list.  Please prefix [MAINTAINERS SUMMIT]
to the subject line, and remember that we only have a half-day, and
they should be appropriate for the Maintainer's summit --- that is,
they should be focused on the development process.

For technical topics, we will have a "Kernel Summit" that will be work
much like the Technical Session days last year.  The technical
sessions will be run in parallel with the Open Source Summit Europe,
and will be open to anyone who registered with the OSS Europe.  The
goal will be to provide a forum to discuss specific technical issues
that would be easier to resolve in person than over e-mail.  The
program committee will also consider "information sharing" topics if
they are clearly of interest to the wider development community (i.e.,
advanced training in topics that would be useful for maintainers).

To suggest a topic for the Kernel Summit, please tag your e-mail with
[TECH TOPIC].  As before, please use a separate e-mail for each topic,
and send the topic suggestions to:

	ksummit-discuss@lists.linuxfoundation.org

We will also be reserving roughly half the slots to be scheduled on
the day of the conference, but if you know are interested in
organizing a discussion around a topic, or giving a presentation on
some topic that would be of interest to kernel developers, please send
them as soon as possible.  For each topic that is accepted and
submitted before July 8th, we will give a free admission to OSS Europe
/ Kernel Summit.  All others will have to pay the normal registration
fee.

If you were not subscribed on to the kernel-discuss mailing list from
last year (or if you had removed yourself after the kernel summit),
you can subscribe to the discuss list using mailman:

   https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [Ksummit-discuss] Next steps and plans for the 2017 Maintainer and Kernel Summits
  2017-06-14 13:29 ` Theodore Ts'o
  (?)
@ 2017-06-21  5:04 ` Theodore Ts'o
  -1 siblings, 0 replies; 5+ messages in thread
From: Theodore Ts'o @ 2017-06-21  5:04 UTC (permalink / raw)
  To: ksummit-discuss, linux-kernel

On Wed, Jun 14, 2017 at 09:29:20AM -0400, Theodore Ts'o wrote:
> We will use the rest of names that Linus had mentioned as being part
> of his secondary list to preseed the list of people to be considered.
> People who suggest topics that should be discussed on the Maintainer's
> summit will be added to the list.  Please prefix [MAINTAINERS SUMMIT]
> to the subject line, and remember that we only have a half-day, and
> they should be appropriate for the Maintainer's summit --- that is,
> they should be focused on the development process.

If you are interested in attending the Maintainer's Summit, I'd
appreciate it if you could send in any topic proposals by Monday, June
26th.  Many thanks!!

					- Ted

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [Ksummit-discuss] Next steps and plans for the 2017 Maintainer and Kernel Summits
  2017-06-14 13:29 ` Theodore Ts'o
@ 2017-06-27 13:23   ` Daniel Vetter
  -1 siblings, 0 replies; 5+ messages in thread
From: Daniel Vetter @ 2017-06-27 13:23 UTC (permalink / raw)
  To: Theodore Ts'o, ksummit-discuss, Linux Kernel Mailing List
  Cc: Alex Deucher, Sean Paul, Nikula, Jani

On Wed, Jun 14, 2017 at 3:29 PM, Theodore Ts'o <tytso@mit.edu> wrote:
> Daniel Vetter

So I've completely screwed up travel planning (well properly checking
my calendar back when we discuss this a while back) and I can't attend
ks :-/

We discussed this among drm maintainers and we'd like to volunteer
Sean Paul as drm rep. He's done drm-misc maintainer (so knows drm core
stuff, and drm-misc is run with the committer model too), and he could
also bring in the drm consumer pov being on google's cros team. Jani
would be another option, but he's busy building a house then, Alex
would be another (he's been around as maintainer forever, at least
longer than me), but Dave thinks Sean would be better fit for
representing drm overall at ks.

Cheers, Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [Ksummit-discuss] Next steps and plans for the 2017 Maintainer and Kernel Summits
@ 2017-06-27 13:23   ` Daniel Vetter
  0 siblings, 0 replies; 5+ messages in thread
From: Daniel Vetter @ 2017-06-27 13:23 UTC (permalink / raw)
  To: Theodore Ts'o, ksummit-discuss, Linux Kernel Mailing List
  Cc: airlied, Nikula, Jani, Sean Paul, Alex Deucher

On Wed, Jun 14, 2017 at 3:29 PM, Theodore Ts'o <tytso@mit.edu> wrote:
> Daniel Vetter

So I've completely screwed up travel planning (well properly checking
my calendar back when we discuss this a while back) and I can't attend
ks :-/

We discussed this among drm maintainers and we'd like to volunteer
Sean Paul as drm rep. He's done drm-misc maintainer (so knows drm core
stuff, and drm-misc is run with the committer model too), and he could
also bring in the drm consumer pov being on google's cros team. Jani
would be another option, but he's busy building a house then, Alex
would be another (he's been around as maintainer forever, at least
longer than me), but Dave thinks Sean would be better fit for
representing drm overall at ks.

Cheers, Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2017-06-27 13:23 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-06-14 13:29 [Ksummit-discuss] Next steps and plans for the 2017 Maintainer and Kernel Summits Theodore Ts'o
2017-06-14 13:29 ` Theodore Ts'o
2017-06-21  5:04 ` [Ksummit-discuss] " Theodore Ts'o
2017-06-27 13:23 ` Daniel Vetter
2017-06-27 13:23   ` Daniel Vetter

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.