85141 - RFE: There should be a bugzilla component for the "native PostScript" module

Status: RESOLVED WONTFIX

(bugzilla.mozilla.org :: Administration, task, P5)

Description

[Roland Mainz]

As the subject says: RFE for a seperate BugZilla "component" for the "native
PostScript" module in Mozilla. This would be quite usefull to keep it seperate
from general printing issues (cross-platform) and "Xprint" bugs...

Suggested name: "Printing: PostScript"
Suggested default owner: [e-mail]
Suggested default QA: [e-mail]

Comment 1

[Roland Mainz]

sujay/dcone:
Can anyone please comment this idea ? 
It would be nice to have a seperate BugZilla component for this to get a clear
seperation between bugs in the crossplatform print API and those in the
PostScript module (e.g. mozilla/gfx/src/ps/) ...

Comment 2

[Tony Jordan]

this is very low priority. we have much more important things to spend our time
working on. Future, if ever

Comment 3

[Roland Mainz]

Tony:
It is important to get a clear seperation between XP bugs and bugs in the PS
module itself. 
It's not much fun to read tons of bugs reports which does not match a given
criteria...

Comment 4

[dcone (gone)]

I fix most the postscript bugs.. and I just put a [ps] in the summary field if I 
need to seprate those bugs.  Lately I have not been doing alot of that because 
the summary fields usually have the word postscript in them.

Comment 5

[Asa Dotzler [:asa]]

oops, that wasn't Tony Jordan.  It was me.  Too many people logging into
Bugzilla on my machines. 

We currently have 108 Browser Components and 24 MailNews Components.  With this
rediculous number of Components it's a miracle that any bugs are filed in the
right place and I'm in no hurry to add more Components unless there is a serious
problem identifying bugs. Printing and Xprint together only have about 750 total
(open and closed) bugs and only 130 open bugs.  It can't be that hard to sort
through 130 bugs with a couple of well crafted queries. Even reading the summary
of ever single open printing report took me less than 2 minutes.  

Comment 6

[dcone (gone)]

I agree with Asa.  I dont think this should be a bug.

Comment 7

[Asa Dotzler [:asa]]

cool. wontfix. if it gets really bad at some point in the future we can look at
this again (hopefully when Bugzilla is smarter and does component trees or
something).

Comment 8

[timeless]

*** Bug 119003 has been marked as a duplicate of this bug. ***

Comment 9

[timeless]

Reopening, apparently there's some interest again, this time from dcone.

Comment 10

[dcone (gone)]

No.. I am not interested in that happening. I just search on the word postscript 
for such things.

Comment 11

[Asa Dotzler [:asa]]

again

Comment 12

[Roland Mainz]

Reopening bug per comments in bug 191684 ("[ps] Mozilla kills printer") - we
should have a seperate BugZilla component for the PostScript module to avoid
confusion/complains...

Comment 13

[Roland Mainz]

Over to timeless...

Comment 14

[kill this account]

just to clarify:

> Reopening bug per comments in bug 191684 ("[ps] Mozilla kills printer") - we
> should have a seperate BugZilla component for the PostScript module to avoid
> confusion/complains...

This has no bearing on the issue in bug 191684. The issue there is "what is the
problem" not "how do we label it".

Comment 15

[Roland Mainz]

Brian Stell wrote:
> > Reopening bug per comments in bug 191684 ("[ps] Mozilla kills printer") - we
> > should have a seperate BugZilla component for the PostScript module to avoid
> > confusion/complains...
>
> This has no bearing on the issue in bug 191684. The issue there is "what is 
> the problem" not "how do we label it".

OKOK, but looking at the number of bugs which are specific to the PostScript
module it really "deserves" a seperate bugzilla component... ;-/

Comment 16

[timeless]

i don't own this component, and i have no intention of having my head chopped off.

Comment 17

[Roland Mainz]

OK, some data per hixie's request:
1. Why?
We have two print modules on Unix/Linux, "PostScript" and "Xprint". Xprint
already has it's bugzilla compoment ("Printing: Xprint") but the bugs for the
PostScript module are placed under "Printing" right now - resulting in the
following disadvantages/problems:
- It is hard to search them the PostScript module bugs (since people may use
"Linux"/"FreeBSD"/"NetBSD"/"AIX"/"SunOS"/"Solaris" and all other incarnations of
Unix/Linux/*BSD - or simply use the OS="other"). As an (ugly) workaround we 
currently stick "[ps]" in the bugs summary (currently 56 open bugs and more
FIXED/CLOSED/whatever).
- The two print modules work completely _differently_ and have completly
different codebases (PostScript module sits in gfx/src/ps/, Xprint in
gfx/src/xprint/ (sharing most of it's code with gfx/src/xlib/)). For Xprint it's
clear, the matching bugs are collected in the "Printing: Xprint" compoment - but
for the PostScript module we do not have a proper way to say "this bug sits in
the PostSCript module code (gfx/src/ps)" or is a Linux-specific issue in the
layout/-printing code (which may then affect both PostScript and Xprint
modules).

2. data for the new component (proposal):
  default-assignee=[e-mail], [e-mail] or simply
[e-mail] until someone claims ownership for the gfx/src/ps/ code
(AFAIK we have still no maintainer - since a few years)
  qa=[e-mail] (current default printing QA), [e-mail] or
[e-mail]
  component name: "Printing: PostScript" or "Printing: Unix/Linux
PostScript"(=to avoid that WinXX??-users with PostScript printers spam that
component)
  component description="PostScript print module for Unix/Linux"
  sample bugs= Just searching for "[ps]" in the bug summary returns 56 open bugs
and we have likely the same number of open bugs in bugzilla which are related to
the PostScript print module but do not carry the "[ps]" stamp yet.

Comment 18

[Hixie (not reading bugmail)]

bstell: As the suggested default assignee, are you in favour of this?

Comment 19

[kill this account]

My days of helping gecko are pretty much winding down. I put in 2 years of 
personal time to bring TrueType support into mozilla and it basically got 
suppressed and I'm left with just a bitter taste in my mouth. I may help
help now and then when I care to.

based on bug 157675 I suggest you ask [e-mail] and [e-mail]

Comment 20

[Hixie (not reading bugmail)]

So, is anyone wanting to be default assignee?

Comment 21

[Jungshik Shin]

any volunteer, yet? 

Comment 22

[Hixie (not reading bugmail)]

no interest here as far as I can tell ->WONTFIX