All of lore.kernel.org
 help / color / mirror / Atom feed
From: Till Kamppeter <till.kamppeter@gmx.net>
To: Norm Jacobs <Norm.Jacobs@Sun.COM>
Cc: printing-spool@freestandards.org,
	printing-architecture <printing-architecture@freestandards.org>,
	printing-jobticket@freestandards.org
Subject: Re: [Printing-architecture] Agenda fodder for our next meeting
Date: Mon, 12 Jun 2006 16:48:56 +0200	[thread overview]
Message-ID: <448D7ED8.5030308@gmx.net> (raw)
In-Reply-To: <448D7CCD.9060103@Sun.COM>

I have already posted a feature request on the CUPS site:

http://www.cups.org/str.php?L1767

It appears also in the roadmap under the open features for CUPS 1.3:

http://www.cups.org/roadmap.php

   Till


Norm Jacobs wrote:
> So... in the Steering Committee meeting last week, we had a fairly 
> lengthy discussion
> about getting adoption of various interfaces that we have been working on.
> I received an action item to prod the architecture, papi, and jtapi teams
> to discuss how various open source projects might integrate support for PAPI
> and JTAPI, along with some potential benefits of using these 
> interfaces.  Once
> we have started the discussions, maybe we can engage some of these projects
> to improve adoption and work toward LSB 4.0 inclusion.
> 
>        -Norm
> 
> 
> _______________________________________________
> Printing-architecture mailing list
> Printing-architecture@lists.freestandards.org
> http://lists.freestandards.org/mailman/listinfo/printing-architecture
> 
> 


      reply	other threads:[~2006-06-12 14:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-12 14:40 [Printing-architecture] Agenda fodder for our next meeting Norm Jacobs
2006-06-12 14:48 ` 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=448D7ED8.5030308@gmx.net \
    --to=till.kamppeter@gmx.net \
    --cc=Norm.Jacobs@Sun.COM \
    --cc=printing-architecture@freestandards.org \
    --cc=printing-jobticket@freestandards.org \
    --cc=printing-spool@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.