Re: Bug 851818 - Modernizing the Enter Bug Entry Page in Bugzilla

2013-03-18 Thread David Ascher
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

Re: Bug 851818 - Modernizing the Enter Bug Entry Page in Bugzilla

2013-03-18 Thread L. David Baron
On Monday 2013-03-18 09:27 -0700, Jason Smith wrote: *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

Re: Bug 851818 - Modernizing the Enter Bug Entry Page in Bugzilla

2013-03-18 Thread Mark Banner
On 18/03/2013 16:27, Jason Smith wrote: - 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. This should be Firefox OS as that's what the users will know it as. *Rationale for Removals* -

Re: Bug 851818 - Modernizing the Enter Bug Entry Page in Bugzilla

2013-03-18 Thread Kevin Brosnan
I have a concern that removing active community projects would increase the community/MOCO divide. Kevin On Mar 18, 2013 10:35 AM, Mark Banner mban...@mozilla.com wrote: On 18/03/2013 16:27, Jason Smith wrote: - BootToGecko - Big focus at Mozilla with a lot of people working on this project,

Changed behavior: writing to console.log file

2013-03-18 Thread Mike de Boer
Hi all, Since https://bugzilla.mozilla.org/show_bug.cgi?id=833939 recently landed on central, I'd like to inform you all of its implications: * Debug builds no longer write the logs to a file called `console.log` in the users' AppData directory (for example `~/Library/Application

Re: Bug 851818 - Modernizing the Enter Bug Entry Page in Bugzilla

2013-03-18 Thread Zack Weinberg
On 2013-03-18 12:39 PM, 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

Re: Bug 851818 - Modernizing the Enter Bug Entry Page in Bugzilla

2013-03-18 Thread Robert Kaiser
Jason Smith schrieb: *Ideas for what products we should remove* And how the XXX should users of those products file new bugs then? Robert Kaiser ___ dev-platform mailing list dev-platform@lists.mozilla.org

Re: Bug 851818 - Modernizing the Enter Bug Entry Page in Bugzilla

2013-03-18 Thread Jason Smith
Sounds good to me. Also to add in a piece of private feedback I received - SeaMonkey wants to remain on the front page as there's a strong community behind it that still works on that project. Sincerely, Jason Smith Desktop QA Engineer Mozilla Corporation https://quality.mozilla.com On

Re: Bug 851818 - Modernizing the Enter Bug Entry Page in Bugzilla

2013-03-18 Thread Philipp Kewisch
On 3/18/13 10:14 PM, Jason Smith wrote: Sounds good to me. Also to add in a piece of private feedback I received - SeaMonkey wants to remain on the front page as there's a strong community behind it that still works on that project. For similar reasons I would like Calendar to stay on the

Re: Bug 851818 - Modernizing the Enter Bug Entry Page in Bugzilla

2013-03-18 Thread ISHIKAWA,chiaki
(2013/03/19 2:31), Mark Banner wrote: On 18/03/2013 16:27, Jason Smith wrote: - 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. This should be Firefox OS as that's what the users will know it

Re: Bug 851818 - Modernizing the Enter Bug Entry Page in Bugzilla

2013-03-18 Thread Byron Jones
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

Re: Decoupling the build config via moz.build files (nuking all.js)

2013-03-18 Thread Justin Lebar
1) Preferences and all.js. We currently define most of the default preferences in /modules/libpref/src/init/all.js. There are things in there related to the browser, Necko, gfx, dom, etc. Prety much the kitchen sink. 2) Telemetry histograms. They are all defined in