Re: Triage Plan for Firefox Components

Emma, On Tue, Apr 5, 2016 at 5:27 PM, Emma Humphries wrote: > It's been a week since I asked for your comments on the plan for triage, > thank you. > > I'm going reply to some general comments on the plan, and outline next > steps. > I just want to say that I have been

Re: Triage Plan for Firefox Components

It's been a week since I asked for your comments on the plan for triage, thank you. I'm going reply to some general comments on the plan, and outline next steps. Ekt and others said that up to now, individual teams have owned how they triage and prioritized bugs. Mozilla has made commitments to

Re: Build System Project - Update from the last 2 weeks

On Tue, Apr 05, 2016 at 09:02:09PM +0100, David Burns wrote: > Below is a highlight of all work the build peers have done in the last 2 > weeks as part of their work to modernise the build infrastructure. > > Since the last report[1] a large number of improvements have landed in > Mozilla

Build System Project - Update from the last 2 weeks

Below is a highlight of all work the build peers have done in the last 2 weeks as part of their work to modernise the build infrastructure. Since the last report[1] a large number of improvements have landed in Mozilla Central. The build system now lazily installs test files. Before, the build

Re: Firefox Hello new data collection

On Tue, Apr 5, 2016 at 12:05 PM, Chris Hofmann wrote: > Thie passage in https://www.mozilla.org/en-US/privacy/firefox-hello/ also > would lead me to believe that the contents of my communication with another > user (including shared URLs) are encrypted (and would be

Re: Intent to enable e10s by default when running tests locally

This has now landed on central. The following suites are e10s by default and require the --disable-e10s flag to run non-e10s: * marionette * mochitest (excluding chrome, a11y and android) * reftest (excluding android) * talos * web-platform-tests I also added some logging to marionette,

Re: Firefox Hello new data collection

I think this should be abandoned in favour of an optional survey for Hello Users 05.04.2016, 17:06, "Chris Hofmann" : > On Mon, Apr 4, 2016 at 3:01 AM, Romain Testard wrote: > >>  Firefox Hello has its own privacy notice (details here >>  

Re: Firefox Hello new data collection

On Mon, Apr 4, 2016 at 3:01 AM, Romain Testard wrote: > > Firefox Hello has its own privacy notice (details here > ). > > Its unclear to me reading the follow through link to the TokBox Privacy Policy. ->

Re: Firefox Hello new data collection

>The privacy review bug is >https://bugzilla.mozilla.org/show_bug.cgi?id=1261467. >More details added below. >> On 04/04/2016 10:01, Romain Testard wrote: >> >>> We would use a whitelist client-side to only collect domains that are >>> part of the top 2000 domains (Alexa list of top

Platform engineering project of the month: Release Build Promotion

Hello from Release Engineering! Once a month we highlight one of our projects to help the Mozilla community discover a useful tool or an interesting contribution opportunity. This month's project is Release Build Promotion. What is Release Build Promotion? Release build promotion (or "build

Re: Triage Plan for Firefox Components

A few comments, although I think others have touched on some of this already. I think my biggest concern is that this is conflating triage and prioritization, which complicates things and introduces ambiguity. For example, what would it even mean to have a "triage: fix-now" bug that's also a P5?

Re: Upcoming SSH Host Key Rotation for hg.mozilla.org

Op 5-4-2016 om 3:09 schreef Philip Chee: > On 04/04/2016 23:52, Gregory Szorc wrote: >> We also changed the SSH server config to only support the "modern" set of >> ciphers, MACs, algorithms, etc from >> https://wiki.mozilla.org/Security/Guidelines/OpenSSH#Modern. If you are >> running an old SSH