All of lore.kernel.org
 help / color / mirror / Atom feed
From: Till Kamppeter <till.kamppeter@gmail.com>
To: "'printing-summit@lists.linux-foundation.org'"
	<printing-summit@lists.linux-foundation.org>,
	"printing-architecture@lists.linux-foundation.org"
	<printing-architecture@lists.linux-foundation.org>,
	Printing-japan <printing-japan@lists.linux-foundation.org>
Cc: "C. Craig Ross" <ccr@linuxfoundation.org>
Subject: [Printing-architecture] OpenPrinting Summit Agenda
Date: Mon, 09 Feb 2009 01:17:33 +0100	[thread overview]
Message-ID: <498F761D.40305@gmail.com> (raw)
In-Reply-To: <fb0caef70902060814h1dc66c78se0d54f9c48243c82@mail.gmail.com>

Hi,

we need to put together a preliminary agenda as soon as possible. At 
least we will need a list of the most important topics, participants, 
and presentations by the end of this week (Fri, Feb 13). This is needed 
for the announcement of speaker lineup of the LF Collab Summit. See below.

As we are doing the OpenPrinting Summit over all the three days and as 
we do more discussion than presentations, we will not need to fix the 
hours for each of our sessions, but at least get together a list of 
highlights for the OpenPrinting Summit, as for example the most 
important participants.

Therefore we need anyone who has an important position in the printing 
stack to tell us quickly whether he will attend, and also if he has 
anything special to present and what.

See also the message cited below.

    Till


C. Craig Ross wrote:
> Requirements for Session Leads:
> 1. Organizing a list of presentations and speakers for your session.
> 2. Inviting the appropriate people to the Collaboration Summit to speak
> and attend your session.
> 3. Preparing the schedule for your session.
> 4. Making sure that we (LF) have all of the necessary abstracts and
> information for the agenda.
> 
> We would like to have the majority of the topics and speakers confirmed
> by Friday, February 13th so that we can publish the schedule and
> announce the lineup for the Collaboration Summit.  Please do your best
> to get your material prepared as quickly as possible.


           reply	other threads:[~2009-02-09  0:17 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <fb0caef70902060814h1dc66c78se0d54f9c48243c82@mail.gmail.com>]

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=498F761D.40305@gmail.com \
    --to=till.kamppeter@gmail.com \
    --cc=ccr@linuxfoundation.org \
    --cc=printing-architecture@lists.linux-foundation.org \
    --cc=printing-japan@lists.linux-foundation.org \
    --cc=printing-summit@lists.linux-foundation.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 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.