Seems like a good proposal, but dev-platform doesn't really feel like the
best place to get feedback from the people affected.  Not sure what would
be, though.

(on Labs: There's a bunch of smaller projects there, but I don't mind if
they're slightly harder to find)

--da


On Mon, Mar 18, 2013 at 9:27 AM, Jason Smith <jsm...@mozilla.com> wrote:

> Hi Everyone,
>
> In bug 851818 
> (https://bugzilla.mozilla.org/**show_bug.cgi?id=851818<https://bugzilla.mozilla.org/show_bug.cgi?id=851818>),
> I've filed a bug to suggest rethinking what our enter bug entry page for
> users who are filing bugs with canconfirm or no canconfirm access. I'd like
> to discuss what changes we should make to that enter bug entry page such as
> adding new products to the list that we think should be there, keeping
> certain products on the list that are important enough to remain there, and
> removing certain products that we don't think need to be there. I've
> outlined the state of enter bug entry pages under canconfirm and no
> canconfirm below and included my initial thoughts below. Thoughts?
>
> *existing canconfirm access* *enter bug entry page list*
>
> - Core
> - Firefox
> - Thunderbird
> - Calendar
> - Camino
> - SeaMonkey
> - Firefox for Android
> - Mozilla Localizations
> - Mozilla Labs
> - Mozilla Services
> - Other Products
>
> *existing no canconfirm access enter bug entry page list*
>
> - Firefox
> - Firefox for Android
> - Thunderbird
> - Mozilla Services
> - SeaMonkey
> - Mozilla Localizations
> - Mozilla Labs
> - Calendar
> - Core
>
> *Ideas for what products we should add*
>
> - BootToGecko (canconfirm and not canconfirm)
> - Firefox for Metro (canconfirm and not canconfirm)
> - Marketplace (canconfirm and not canconfirm)
>
> *Ideas for what products we should remove*
>
> - Thunderbird (canconfirm and not canconfirm)
> - Calendar (canconfirm and not canconfirm)
> - Camino (canconfirm and not canconfirm)
> - SeaMonkey (canconfirm and not canconfirm)
> - Mozilla Labs (canconfirm and not canconfirm)
>
> *Rationale for Additions*
>
> - BootToGecko - Big focus at Mozilla with a lot of people working on this
> project, so I think this could benefit greatly from being on the front page.
> - Firefox for Metro - Important for our Windows 8 story and could probably
> benefit for contributors from knowing up front where to file bugs on this
> while it's under development
> - Marketplace - Important in conjunction with BootToGecko and a common
> bugzilla product I don't think people realize exists. In doing bug triage
> for B2G, there's very high cases where bugs for Marketplace have ended up
> in the incorrect component, so I'm hoping putting this on the front page
> will increase likelihood that the bug ends up in the right spot.
>
> *Rationale for Removals*
>
> - Thunderbird - Decreased focus at Mozilla now that has moved to
> contribution only now, so I don't think this needs to be on the front page.
> - Calendar - Decreased focus at Mozilla overall in comparison to other
> products on the front page
> - Camino - Low focus at Mozilla overall in comparison to other products on
> the front page
> - SeaMonkey - Low focus at Mozilla overall in comparison to other products
> on the front page
> - Mozilla Labs - Looks like an outdated Bugzilla product that may not have
> high bug filing usage - probably does not need to be on the front page
>
> --
> Sincerely,
> Jason Smith
>
> Desktop QA Engineer
> Mozilla Corporation
> https://quality.mozilla.com
>
> ______________________________**_________________
> dev-platform mailing list
> dev-platform@lists.mozilla.org
> https://lists.mozilla.org/**listinfo/dev-platform<https://lists.mozilla.org/listinfo/dev-platform>
>
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Reply via email to