Differences between revisions 4 and 5
Revision 4 as of 2010-07-02 14:20:51
Size: 3994
Editor: DidierRaboud
Comment:
Revision 5 as of 2010-07-02 16:50:10
Size: 4437
Editor: DidierRaboud
Comment: + DebugProblems
Deletions are marked like this. Additions are marked like this.
Line 42: Line 42:
=== Bugs ===

[[DebianBug:532097|Quoting Martin Pitt]]

  Someone who
  knows the Linux printing system very well needs to sit down and write
  a comprehensive "[[/DebugProblems|how to debug printing problems]]" document: in
  particular, how to identify in which package the problem is, which
  debug information to collect, and common workarounds/tests which help
  the reporter's immediate problem and are useful for diagnosis.

Debian Printing Team

/!\ THIS IS CURRENTLY A PROPOSAL: NOTHING OFFICIAL, NOTHING DONE YET /!\

Initial proposal

RFC: Forming a Printing Task Force

As stated in the above mail, the situation is not really good in the printing scope : the diff with Ubuntu is growing, the bug reports are piling, several security issues have arosen, etc. In order to solve this in time for squeeze, the idea is to merge multiple teams and their diverted forces into a bigger single "Printing Team".

This renewed team would handle the packages from the list below.

Concerned packages

Please list here the packages that would be handled by the eventual team. Please also remove them if needed.

(Please keep alphabetical order.)

Package

Maintainers

In Team

With Ubuntu

VCS

Comments

cups

Debian CUPS Maintainers <pkg-cups-devel AT lists DOT alioth DOT debian DOT org>

{X}

(./)

Bazaar - Broken ?

RFA: 532097 , other team

cups-pdf

Debian CUPS Maintainers <pkg-cups-devel AT lists DOT alioth DOT debian DOT org>

{X}

(./)

None known

Other team

foomatic-db

ChrisLawrence, DidierRaboud, ?TillKampetter

{X}

(./)

Git in collab-maint

foomatic-db-engine

ChrisLawrence, DidierRaboud, ?TillKampetter

{X}

(./)

Git in collab-maint

foomatic-filters

ChrisLawrence

{X}

{X}

Git in collab-maint

In progress, DidierRaboud and ?TillKampetter will join.

ghostscript

MasayukiHatta, TorstenLandschoff, JonasSmedegaard

{X}

{X}

Git in collab-maint

gutenprint

Debian Printing Group <debian-printing AT lists DOT debian DOT org>

{X}

{X}

Git in collab-maint

O: 479397

hplip

Debian HPIJS and HPLIP maintainers <pkg-hpijs-devel AT lists DOT alioth DOT debian DOT org>

{X}

{X}

Svn in pkg-hpijs

Hplip-only other team

poppler

?LoicMinier, ?JosselinMouette, ?DaveBeckett, ?RossBurton

{X}

{X}

None known

Infrastructure

Infrastructure re-use proposal:

Name

Debian Printing Team

? … Task Force ?

Mailing-list

<debian-printing AT lists DOT debian DOT org>

? Hijacking debian-printing from gutenprint packagers ? There are others, but that one exists and is on l.d.o (if that matters)

Alioth group

pkg-printing

Rather pkg-print ? There is already pkg-cups and pkg-hpijs…

VCS

Git

? There should probably be no preference.

IRC

#debian-print

? #debian-printing ?

To be done

Bugs

Quoting Martin Pitt

  • Someone who knows the Linux printing system very well needs to sit down and write

    a comprehensive "?how to debug printing problems" document: in particular, how to identify in which package the problem is, which debug information to collect, and common workarounds/tests which help the reporter's immediate problem and are useful for diagnosis.

Packages

  • {*} Update packages to latest packaging techniques

  • {*}{*} Update packages to new upstream versions

  • {*}{*} Merge back the Ubuntu changes

  • {*}{*} Discuss and eventually act on putting the packages under this team's umbrella

  • {*}{*}{*} Triage and act on all bugs

Team

  • {*}Make this a team page (see TeamTemplate please.)

  • {*}{*}Form the team