141669 - add a component in bugzilla to track gtk2 port work?

Status: RESOLVED DUPLICATE of bug 77313

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

Description

[Jay Yan]

I am not sure whether this is a good suggestion,

please see http://bugzilla.mozilla.org/showdependencytree.cgi?id=92033,

nowadays some Sun persons begin to work with Chris on gtk2 port, including file 
bugs, when they are submiting bugs, they are confused with what componnet 
should select, and they have to fill in the responsible engineer and qa 
contact, if they leave these values as default values, the default owner and qa 
contact have as no time to care about gtk2 work, and they are feel tried to 
deal with the email from bugzilla.daemon. 

so I have a suggestion, open a new component to track gtk2 port work? as we can 
see, a new component is added recently, it is Accessibility API, it is used to 
track accessibility API implementation work for some Sun person who are working 
with Aaronl and Jgaunt.

If it is a bad idea, please add comment on it, I will mark it as invalid.

Comment 1

[Boris Zbarsky [:bzbarsky]]

Over to the right component.  :)

Comment 2

[timeless]

we're currently opposed to this.

there's no component for os/2, none for BeOS, none for Photon, none for Qt.

If you can convince asa to make those, then you can have yours.

Comment 3

[Brian Tarricone]

timeless: please, there's no reason to get political over this.  the point of
making a new component is twofold: 1) to make it easier on users, so they aren't
confused as to how to most effectively report a bug; and 2) to make it easier on
the developers dealing with bugs, so that they don't have to waste their time
looking over a bug that shouldn't belong to them (in the case of the default
assignee), or, in the case of who should be working on the bug, it creates a
delay before they see it.

as i recall, there are already gtk-related components, so why not a gtk2-related
one?

i was going to suggest as an alternate solution a change in the "OS" box to
"linux-gtk" and "linux-gtk2" - but of course linux is not the only os that uses
gtk 1.2 or 2, so that would require quire a few new os entries, which probably
isn't practical.  perhaps make the gtk2 build put something unique in the
user-agent (yeah, i know, seems kinda hack-y), and then put some logic into
bugzilla to notice that and set the asignee and QA contact, as well as
automatically prefix the summary with "[gtk2]" or the like?

honestly - the issue here is not what other groups have or don't have.  the
issue is what will make bug-fixing and development easier.  turning this into a
debate over what other toolkits deserve to be "fair" is just childish.

Comment 4

[timeless]

*** This bug has been marked as a duplicate of 77313 ***

Comment 5

[Jay Yan]

I do not want to reopen it, becasue I do not want to waste time to argue for it.

But I still want to clarify my thought:

As a end user, when I file bug, I do not know which component I should use,
because the default owner and QA contact of xpwidget(it is the usual component I
use to file gtk2 releated bug) said clearly that they have no time to care about
gtk2 related bugs now. To some extent, I am annoying them. so I am hesitating to
file bug even when I find a bug, it is one obstacle.

As a developer, I can not get connection and help from gtk2 developer easily. it
is abother obstacle.

Since there are obstacles, why not take some aaction to remove them?

Comment 6

[Asa Dotzler [:asa]]

Jay, we don't encourage end users to file bugs in Bugzilla. If they do file bugs
in Bugzilla they usually file them on the wrong component anyway (usually
Browser General). Those people that are regular testers or developers can file
the bug to the correct owner without creating a new component. 
We will make this better some day but we'll probably need changes in Bugzilla
and creating one more component will make the system that much more complex for
those that arleady do know how to use it and won't help much for end users who
can't get the correct component even if we did make the change.