From: Till Kamppeter <till.kamppeter@gmail.com>
To: Osamu MIHARA <osamu.mihara@fujixerox.co.jp>
Cc: printing-architecture@lists.linux-foundation.org
Subject: Re: [Printing-architecture] OP SC / OP Arch Telecon - Mon/Tue 12/13 May
Date: Tue, 13 May 2008 00:22:25 +0200 [thread overview]
Message-ID: <4828C321.2070600@gmail.com> (raw)
In-Reply-To: <4827A6EA.7060507@fujixerox.co.jp>
Osamu MIHARA wrote:
> Hi,
>
> on 2008/05/10 2:51 Ira McDonald said the following:
>> Agenda will be determined during the meeting.
>
> I have an item to be discussed (or just confirmed) about the release
> procedure for specifications.
>
> The release procedure is defined in the document below, which can be
> fetched from the PWG ftp site:
>
> ftp://ftp.pwg.org/pub/pwg/fsg/steering_committee/Release-Procedure/FSG-OpenPrinting-Release-Procedure--V0100-2004-0930.pdf
>
> This procedure was discussed and defined in the FSG era, but I believe
> it is inherited to OpenPrinting WG under LF and still valid.
>
> I'd like to confirm that this is the common perception among the members.
>
> In addition, I couldn't find a link to this document (and other spec
> documents) from the current OpenPrinting web site. I think it would be
> convenient for developers if they find links to OP specs and procedure
> documents.
The page to place these links is
https://www.linux-foundation.org/en/OpenPrinting/Development
This page is a Wiki page, so everyone can edit it (you only need to
register to get write access).
Till
prev parent reply other threads:[~2008-05-12 22:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-09 17:51 [Printing-architecture] OP SC / OP Arch Telecon - Mon/Tue 12/13 May Ira McDonald
2008-05-12 2:09 ` Osamu MIHARA
2008-05-12 22:22 ` Till Kamppeter [this message]
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=4828C321.2070600@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=osamu.mihara@fujixerox.co.jp \
--cc=printing-architecture@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.