Robert Kaiser wrote:
*Ideas for what products we should remove*
And how the XXX should users of those products file new bugs then?
we're talking about removing products from the list of products
initially shown to users, not about removing the products from bmo
completely.
the complete list of products will always be a single click away.
Philipp Kewisch wrote:
I have similar feelings for any active project.
there are *many* active projects/products which are not initially shown;
i don't think that alone is good enough criteria for inclusion in the list.
finding the product isn't difficult, via clicking on "other products" or
searching with the search field. if someone isn't able to find the
calendar product via either of these, i would question the value of
their bug report :)
L. David Baron wrote:
I'd actually like to see Core higher on the list for the
no-canconfirm case. I think it's common for reasonably
well-informed Web developers (who would have been able to choose a
reasonably correct component within Core, given the list) to file
standards bugs and end up with them languishing in Firefox::General.
if you select 'firefox' from the guided bug form, your bug is forced
into the 'firefox::untriaged' component. if their bugs are landing in
firefox::general, it would be because either they are switching to the
advanced form and selecting that product/component, or triage are
incorrectly moving bugs from firefox::untriaged to firefox::general
instead of into the core product. in either case, moving core up in the
list won't address this issue.
on the guided bug form there's always been a link "report an issue with
firefox on a site that i've developed", which takes you to the core product.
instead of moving core, i'd rather draw more attention to this link.
--
byron - irc:glob - bugzilla.mozilla.org team -
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
