From: Till Kamppeter <till.kamppeter@gmx.net>
To: "McDonald, Ira" <imcdonald@sharplabs.com>
Cc: "'lsm-printing@linuxprinting.org'"
<lsm-printing@linuxprinting.org>,
'Pierre Jarillon' <jarillon@abul.org>,
printing-architecture@freestandards.org
Subject: Re: [Printing-architecture] Schedule for Open Printing day(s) at LSM?
Date: Thu, 10 Jun 2004 04:21:53 +0200 [thread overview]
Message-ID: <40C7C5C1.3080501@gmx.net> (raw)
In-Reply-To: <CFEE79A465B35C4385389BA5866BEDF00C7714@mailsrvnt02.enet.sharplabs.com>
McDonald, Ira wrote:
> Hi Till,
>
> At the FSG Open Printing Int'l Steering Committee meeting
> two days ago we agreed to try to schedule:
>
> (1) First day of Open Printing overview/intro/etc.,
> for attendance by all LSM conference members
> (2) Second day of Open Printing technical sessions,
> for working on FSG OP standards issues
>
At first we must know, which days of the event are only for
project-group-internal sessions and on which days of the event are
public sessions. We must also know on which day(s) we can give our
presentations to the visitors of LSM and which is the total of hours in
these sessions. Pierre?
Then we must sort out, which presentations are only interesting for the
FSG OpenPrinting group, which are also interesting to the other
participating printing developers, and which should be given in the
publich session(s), where also visitors will be.
We must also take into account, that not all of the participants of the
printing workshop on the LSM are members of FSG OpenPrinting group. This
means, that they also want to have a certain part of the talking time in
the public session(s) and they also will be not necessarily interested
in all our sessions.
Under these aspects we should choose the days and the hours of our sessions.
We should also present somehow to the non-FSG-OpenPrinting people and to
the visitors of LSM, what we have done in OpenPrinting and what we will do.
We have a room for us during all the five days and we have also a
session in the conference. We cannot stuff the time in our room full
with presentations as there should also stay time for individual
discussion and sor hacking sessions.
> At the LSM Web page (http://lsm.abul.org/rubrique2.html),
> we still can't find any day-by-day schedule.
>
> Please ask the LSM organizers, if necessary, and reply to
> this note with a day-by-day LSM schedule _very_ soon.
>
So please make your suggestions for a schedule. Everyone reading this
and not being member of the FSG OpenPrinting group, please make your
suggestions on what and when you like to present.
> If we can have a second day of technical sessions (perhaps
> outside the regular LSM conference days), then Mark Hamzy
> can schedule one or more telecons for those who can't
> travel to France this July.
>
Perhaps July 5 or July 11?
Till
next prev parent reply other threads:[~2004-06-10 2:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 15:28 [Printing-architecture] Schedule for Open Printing day(s) at LSM? McDonald, Ira
2004-06-10 2:21 ` Till Kamppeter [this message]
2004-06-10 21:22 ` [lsm-printing] " Jody Goldberg
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=40C7C5C1.3080501@gmx.net \
--to=till.kamppeter@gmx.net \
--cc=imcdonald@sharplabs.com \
--cc=jarillon@abul.org \
--cc=lsm-printing@linuxprinting.org \
--cc=printing-architecture@freestandards.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.