From: Chris Mason <clm@fb.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Tech Board Discuss"
<Tech-board-discuss@lists.linux-foundation.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Linux Plumbers call for organizers
Date: Mon, 5 Sep 2016 09:15:57 -0400 [thread overview]
Message-ID: <633ecfc4-6e0f-ffc0-4427-21ea66e76289@fb.com> (raw)
Each year, the Linux Foundation's Technical Advisory Board (TAB) seeks
an organizing committee for the annual Linux Plumbers Conference; that
process has now begun for the 2017 event. This is your chance to put
your stamp on one of our community's most important gatherings.
LPC 2017 will take place September 13-15, and will be colocated with
Open Source Summit NA (formerly LinuxCon NA) at the JW Marriott in
Downtown Los Angeles CA.
Interested groups should have, at a minimum, an events coordinator, a
treasurer, a microconference chair, and a chairperson. This group must
be able to take the initiative to handle conference-specific details
(including social events, the miniconf program, and more) while working
with the Linux Foundation to ensure that logistics work smoothly.
The process for putting in an application to run the Linux Plumbers
Conference is documented here:
https://wiki.linuxfoundation.org/en/LPC
Applications should be in by October 1st; the TAB then will announce a
decision by (at the latest) November 11th.
If you're interested in submitting a proposal, but are concerned that
you don't know enough about how previous Plumbers has been run, then
fear not! The TAB will support the selected organizing committee with
additional volunteers with past Plumbers organizing experience. Above
all we are looking for a capable and enthusiastic group who we can work
with to make the 2017 Linux Plumbers Conference a great success.
If you have any questions about the submission process, please email the
TAB at tech-board@lists.linux-foundation.org
reply other threads:[~2016-09-05 13:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=633ecfc4-6e0f-ffc0-4427-21ea66e76289@fb.com \
--to=clm@fb.com \
--cc=Tech-board-discuss@lists.linux-foundation.org \
--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
all inboxes | Powered by JetHome®