1505091 - Please disable Core::Untriaged

Status: NEW

(bugzilla.mozilla.org :: Graveyard Tasks, task)

Description

[Sylvestre Ledru [:Sylvestre]]

It is empty [1] and probably doesn't make much sense.
Core being mostly used by developers, they probably don't need that.

[1] https://bugzilla.mozilla.org/buglist.cgi?list_id=14420546&resolution=---&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=INACTIVE&resolution=DUPLICATE&resolution=WORKSFORME&resolution=INCOMPLETE&resolution=SUPPORT&resolution=EXPIRED&resolution=MOVED&query_format=advanced&component=Untriaged&product=Core

Comment 1

[Emma Humphries ☕️🎸🧞‍♀️✨ (she/they) [:emceeaich] (Pacific Time) use needinfo]

I want to get Selena's take on this before disabling it.

Comment 2

[Emma Humphries ☕️🎸🧞‍♀️✨ (she/they) [:emceeaich] (Pacific Time) use needinfo]

Selena, is this okay with you to disable?

Comment 3

[Selena Deckelmann :selenamarie :selena]

Ok by me.

Comment 4

[Emma Humphries ☕️🎸🧞‍♀️✨ (she/they) [:emceeaich] (Pacific Time) use needinfo]

This appears to have been disabled already. It now needs to be moved to Core Graveyard.

Comment 5

[David Lawrence [:dkl]]

Actually after looking through the code, Core :: Untriaged is hard coded in a few places such as the guided bug form, etc. We would need to change the component to something else if Untriaged is removed otherwise people may get errors when submitting new bugs.

Comment 6

[Emma Humphries ☕️🎸🧞‍♀️✨ (she/they) [:emceeaich] (Pacific Time) use needinfo]

Opening a dependent bug to remove the hard-coded references. 

Also, I found the original bug for creating the component, so before removing the hard-coded refs, :gijs, was there any reason to keep this? Or can new bugs we are not sure of a home for go into core::general?

Comment 7

[:Gijs (he/him)]

(In reply to Emma Humphries, Bugmaster ☕️🎸🧞‍♀️✨ (she/her) [:emceeaich] (UTC-8) needinfo? me from comment #6)
> Opening a dependent bug to remove the hard-coded references. 
> 
> Also, I found the original bug for creating the component, so before
> removing the hard-coded refs, :gijs, was there any reason to keep this? Or
> can new bugs we are not sure of a home for go into core::general?

I mean, it's a bit late for me to object now, feels like... I think the problem with ::General components is that they become a dumping ground, and mixing the "we don't know where this goes" and "we don't have a better / more specific component for this" buckets makes triage harder. In Firefox, *any* bug in Fx::Untriaged really ought to live somewhere else. The same is not true for ::General - that's the "catch all" component when we don't have somewhere more specific (and it's annoying that folks file so many bugs there when they should be in ::Untriaged, and I *still* want to know why that happens, many years since I first poked at that problem, but that's a rant for another day).

So I'm sad that we're removing Core::Untriaged, and besides my points above, I think the resulting discrepancy with Firefox will cause confusion. However, ultimately it's also not my call as I don't, as a rule, work in Core myself. As long as people aggressively triage out of Core::General, as we do for Fx::General, then this solution also more or less works, and if that's what people working in Core prefer, great!

Comment 8

[Sylvestre Ledru [:Sylvestre]]

I agree with you. My goal is also to remove General components (or limit their usage) by also having tools to help triage them.