public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Linux Plumber's Conference: Call for Working Session Submissions
Date: Sat, 24 Jul 2010 17:43:35 -0300	[thread overview]
Message-ID: <4C4B5077.3020509@redhat.com> (raw)

CFP dead line for submitting proposals to LPC/2010 is approaching.
For those that intends to submit proposals for it, please do it quickly,
as the official dead line is July, 26.


---

The Planning Committee for the Linux Plumbers Conference (LPC) is happy
to announce that submissions to the "micro-conferences" portion of the
conference is now open.  The micro-conferences are working session
focused on specific infrastructural "plumbing" in the Linux system --
kernel subsystems, core libraries, windowing system, etc. -- which are
half-day in length.

The potential topics for the working sessions can be found at the Topics
page[1] of the LPC wiki and include:

	* Power Management
	* Virtualization
	* Mono
	* Desktop
	* Tracing
	* Real-time response for full FOSS/Linux stack
	* User-visible Problems in Networking
	* Media Infrastructure
	* Audio
	* HA Clustering
	* Legal Hygiene
	* Embedded Topics
	* Boot/init

[1] http://wiki.linuxplumbersconf.org/2010:topics

The topics that will actually have working sessions scheduled at the LPC
will depend on the submissions to the microconference and on the ability
of its respective community to organize a successful working session;
see "Responsibility of a working session leader"[2] page on the LPC
wiki for more details.

[2] http://wiki.linuxplumbersconf.org/2010:responsibilities_of_a_working_session_leader

Microconference submissions do not have to reflect finished work.  In
fact, proposals or proof-of-concepts of potential solutions to important
problems are encouraged, so they can be discussed and debated during the
microconference.  Proposals for presentations at a microconference may
be submitted here [3]:

[3] http://www.linuxplumbersconf.org/2010/ocw/events/LPC2010MC/proposals

In addition to the micro conference, the Linux Plumbers Conference has
open calls for papers[4] and BOF's[5].

[4] http://www.linuxplumbersconf.org/2010/ocw/events/LPC2010/proposals
[5] http://www.linuxplumbersconf.org/2010/ocw/events/LPC2010BOFS/proposals

For further announcements about LPC, please watch our blog[6] or
subscribe to our LPC announcements mailing list[7].

[6] http://www.linuxplumbersconf.org/2010/feed/rss
[7] http://lists.linuxplumbersconf.org/mailman/listinfo/lpc-announce

_______________________________________________
Lpc-session-leads mailing list
Lpc-session-leads@lists.linuxplumbersconf.org
http://lists.linuxplumbersconf.org/mailman/listinfo/lpc-session-leads

             reply	other threads:[~2010-07-24 20:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-24 20:43 Mauro Carvalho Chehab [this message]
2010-07-25 16:10 ` Linux Plumber's Conference: Call for Working Session Submissions Jarod Wilson
2010-07-25 17:35   ` Mauro Carvalho Chehab
2010-07-25 18:20     ` Jarod Wilson
2010-07-25 18:37       ` Mauro Carvalho Chehab
2010-07-26  8:15 ` Laurent Pinchart
2010-08-19 16:27 ` Mauro Carvalho Chehab
2010-08-20  8:31   ` Pawel Osciak

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=4C4B5077.3020509@redhat.com \
    --to=mchehab@redhat.com \
    --cc=linux-media@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