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>
Subject: [Printing-architecture] OpenPrinting Summit 2009: First cut of putting the sessions into the days
Date: Thu, 12 Mar 2009 00:03:57 +0100	[thread overview]
Message-ID: <49B8435D.40800@gmail.com> (raw)

Hi,

please have a look at

https://www.linuxfoundation.org/en/OpenPrinting/OpenPrinting_Summit_San_Francisco_2009#Agenda

The length of the sessions between the breaks given by the agenda of the 
Linux Foundation Collaboration Summit 
http://events.linuxfoundation.org/events/collaboration-summit/agenda/ 
was not very friendly for fitting in the sessions we have talked about 
on this Tuesday's planning phone meeting, but I have got it together.

The topics most interesting for the printer vendors I have put onto the 
Wednesday. Once, Nagasaki-san and Tak Shizoaki will probably only attend 
the first day if they come, and second, I have put the sessions into the 
afternoon, as this is the better time for Japaneses to call in (SF's 
morning is in the middle of the night for Japan). See

http://www.timeanddate.com/worldclock/meetingtime.html?month=4&day=9&year=2009&p1=224&p2=136&p3=37&p4=248

The second day is 3 hours color management and 3 hours Desktop printing. 
The Joint meeting with the Desktop Architects should be scheduled as a 
part of the desktop printing sessions in the afternoon. We can continue 
the discussion in the breakout sessions of the third day.

On the third day we will do the breakouts, and the joint meetings with 
LSB and Driver Backports.

I had to break the driver package part into two pieces, to make the 
printer vendor part more accessible for the vendors (see reasoning for 
the first day) and to be able to run a joint session with the Driver 
Backports.

Slight changes are possible, for example if one of the LF workgroups 
does not agree with our schedule of their joint meeting, or if one of 
you has problems to attend the sessions he desires to attend.

Please tell what you think about the schedules and make suggestions if 
you want to have something changed.

If you want to give a presentation, edit the session where you want to 
give it, and upload and link your slides as soon as you have them ready. 
Slides should be uploaded before the event so that phone attendees can 
easily follow your talk and attendees in general could prepare for the 
discussion.

    Till




                 reply	other threads:[~2009-03-11 23:03 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=49B8435D.40800@gmail.com \
    --to=till.kamppeter@gmail.com \
    --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.