We've decided to run an experiment with using a new component for incoming uncatagorized bugs, instead of using Firefox::General for both that and bugs without a more specific component. This allows inexperienced users to just drop new bugs here, and not have to try and figure out where in our maze of products and components things should go. Product: Firefox Component: Untriaged Description: For newly filed bugs that need some help finding the right place to go. Default QA: untriaged@firefox.bugs Otherwise basically the same as Firefox::General. Though if it's possible to turn off various bells and whistles for just this component, that would be swell... The intention is that bugs filed here will either (1) be moved elsewhere, (2) remain here while submitters are asked for more info or (3) closed.

Also, can I get a list of users (email) who are watching general@firefox.bugs? I'm going to blog about this, but would like to make sure existing watchers know what's happening.

(In reply to Justin Dolske [:Dolske] from comment #0) > Otherwise basically the same as Firefox::General. Though if it's possible to > turn off various bells and whistles for just this component, that would be > swell... part of the plan for the tell-us-more facility is for an untraiged _product_ to be created as a store of these bugs. see https://wiki.mozilla.org/Firefox/TellUsMore and https://wiki.mozilla.org/BMO/TellUsMore a large reason for opting to use a product instead of a component is it will be easier to tailor the show_bug form on a per-product rather than per-component basis (things like removing most fields, adding triage helpers such as inline bug searching and canned responses). it's less work to to proceed with it as a component (i'm thinking about the amount of work involved in bug 713165 here), so let's get the ball rolling on that, but keep in the back of our minds that it may need to be migrated to an untriaged product once those bells and whistles are in place. > Also, can I get a list of users (email) who are watching general@firefox.bugs? note to self: we'll also need a list of people watching the firefox:general component, as well as the qa user.

(In reply to Byron Jones ‹:glob› from comment #2) > it's less work to to proceed with it as a component (i'm thinking about the > amount of work involved in bug 713165 here), so let's get the ball rolling > on that, but keep in the back of our minds that it may need to be migrated > to an untriaged product once those bells and whistles are in place. Yep, that's fine and will be a nice solution in the long-term. I suppose this even helps that by separating out the multiple roles of Firefox::General.

i've added the component, waiting to get a hold of someone who can run the sql http://glob.pastebin.mozilla.org/1417181 against prod and email me the results.

(In reply to Justin Dolske [:Dolske] from comment #0) > We've decided to run an experiment Are there some logs available of this discussion? I didn't see anything on the "dev-quality at lists.mozilla.org" mailing list but maybe this is not the place?

i've emailed dolske the list of people watching firefox::general.

(In reply to Andre Klapper from comment #5) > Are there some logs available of this discussion? I didn't see anything on > the "dev-quality at lists.mozilla.org" mailing list but maybe this is not > the place? It was after a discussion on IRC in #fx-team, trying to figure out ways to better triage bugs in the Firefox component. Sadly, I can't easily get logs from the discussion, maybe someone else can.

(In reply to Justin Dolske [:Dolske] from comment #1) > Also, can I get a list of users (email) who are watching > general@firefox.bugs? I'm going to blog about this, but would like to make > sure existing watchers know what's happening. This has now been done. Thanks!