All of lore.kernel.org
 help / color / mirror / Atom feed
From: Till Kamppeter <till.kamppeter@gmail.com>
To: Debian-printing@lists.debian.org,
	"twaugh@redhat.com" <twaugh@redhat.com>,
	Open Printing <printing-architecture@lists.linux-foundation.org>
Subject: [Printing-architecture] Upstream future of ippusbxd
Date: Mon, 06 Jul 2015 22:15:53 -0300	[thread overview]
Message-ID: <559B2849.7060907@gmail.com> (raw)

Hi,

ippusbxd is a daemon to support IPP-over-USB printing, a standard for a 
packet-based USB protocol for printers, which especially adds full IPP 
and HTTP functionality to a USB-connected, non-networked printer: Web 
interface of the printer for configuration (especially also the 
printer's WiFi if it does not have a front panel) and for using the 
built-in scanner, IPP querying of printer properties, and even 
driverless printing via IPP Everywhere.

The daemon was developed by Daniel Dresssler as a GSoC project. Now 
Daniel has no time any more to maintain it and upstream maintainership 
is going over to me (and so to OpenPrinting).

I am thinking about joining it into the cups-filters upstream package to 
not have too many tiny packages to make up the complete printing stack 
and cups-filters contains all manufacturer-independent software for 
communication with printers which is not part of CUPS itself. It will 
usually be used with CUPS anyway as there are no other maintained 
printing environments. You will simply have as manufacturer-independent 
part of the printing stack CUPS, cups-filters, and at least one PDF 
renderer (currently Ghostscript or Poppler, in the future perhaps also 
MuPDF) plus the manufacturer-dependent drivers (foomatic-db, HPLIP, 
Gutenprint, ...).

WDYT?

    Till

             reply	other threads:[~2015-07-07  1:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-07  1:15 Till Kamppeter [this message]
2015-07-07  8:47 ` [Printing-architecture] Upstream future of ippusbxd Johannes Meixner
2015-07-07 12:10 ` James Cloos
2015-07-07 14:16   ` Johannes Meixner
2015-07-07 16:02     ` James Cloos
2015-07-08  9:12       ` Johannes Meixner
2015-07-08 12:40         ` Ira McDonald
2015-07-08 14:10           ` Tim Waugh
2015-07-08 18:59           ` Till Kamppeter
2015-07-13 10:05             ` Tim Waugh
2015-07-07 15:33 ` Tim Waugh

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=559B2849.7060907@gmail.com \
    --to=till.kamppeter@gmail.com \
    --cc=Debian-printing@lists.debian.org \
    --cc=printing-architecture@lists.linux-foundation.org \
    --cc=twaugh@redhat.com \
    /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.