All of lore.kernel.org
 help / color / mirror / Atom feed
From: Till Kamppeter <till.kamppeter@gmail.com>
To: Printing-japan <printing-japan@lists.linux-foundation.org>,
	"printing-architecture@lists.linux-foundation.org"
	<printing-architecture@lists.linux-foundation.org>,
	Tso Ted <tytso@MIT.EDU>, Martin Pitt <martin.pitt@ubuntu.com>,
	"'printing-summit@lists.linux-foundation.org'"
	<printing-summit@lists.linux-foundation.org>,
	Tim Waugh <twaugh@redhat.com>, Johannes Meixner <jsmeix@suse.de>,
	Klaus Singvogel <kssingvo@suse.de>,
	Gustavo De Nardin <gustavodn@mandriva.com>,
	Ray Hsu <ray.hsu@eitc.epson.com>,
	Bin Li <bin.li@etd.ussj.ricoh.com>,
	Jim Zemlin <jzemlin@linux-foundation.org>
Subject: [Printing-architecture] Let us finalize printer driver auto-download service on OpenPrinting
Date: Fri, 06 Feb 2009 15:38:16 +0100	[thread overview]
Message-ID: <498C4B58.8000600@gmail.com> (raw)

Hi,

I would like to have a session on the OpenPrinting Summit (April 8-10, 
2009 in San Francisco) to finalize the the topic of automatically 
downloadable LSB driver packages so that the service can get started and 
that distributions agree to participate (and add the needed keys and 
activate the binary driver package download in their printer setup 
tools/download managers).

On this session we should

- present the paper the manufacturers should sign that they take full 
responsibility over their software in the case that they want to upload 
to our server

- talk about the procedure of providing driver packages on the 
manufacturer's own server (setting external link and package repository 
references in driver XML file, requirements of keeping these references 
up-to-date, ...)

- present and on agree on the standard modules allowed to be used in 
maintainer scripts

- agree on the way packages and repositories get signed and appropriate 
verification keys added to the distributions

- having a "main" repository for automatic download of 
manufacturer-supplied drivers by default and an "optional" repository 
for bleeding-edge free software drivers, ... Agree on in which points 
the conditions for uploading into the "optional" repository can be more 
relaxed

We should prepare this session well so that we can really do a final 
agreement on the Summit so that the service can be officially started 
right after the Summit.

This means that we should have an agreement paper for the manufacturers 
to sign prepared, demonstration of an externally hosted downloadable 
package, ... list of standard modules for maintainer scripts, ...

Any agreement made before the Summit by e-mail is welcome. For example 
it would be great to post a draft already before the Summit.

Please give your feedback, so that we can use the two months up the 
Summit effectively.

    Till

                 reply	other threads:[~2009-02-06 14:38 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=498C4B58.8000600@gmail.com \
    --to=till.kamppeter@gmail.com \
    --cc=bin.li@etd.ussj.ricoh.com \
    --cc=gustavodn@mandriva.com \
    --cc=jsmeix@suse.de \
    --cc=jzemlin@linux-foundation.org \
    --cc=kssingvo@suse.de \
    --cc=martin.pitt@ubuntu.com \
    --cc=printing-architecture@lists.linux-foundation.org \
    --cc=printing-japan@lists.linux-foundation.org \
    --cc=printing-summit@lists.linux-foundation.org \
    --cc=ray.hsu@eitc.epson.com \
    --cc=twaugh@redhat.com \
    --cc=tytso@MIT.EDU \
    /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.