Re: Now measuring Firefox size per-commit. What else should we be tracking?

- Build: Memory footprint Background: 8 GB is our recommended minimum for building on Windows. New contributors don't necessarily have high-end developer machines. By noticing bumps we can evaluate the cost/benefit of these and protract further bumps of the recommended minimum. - Tests:

Re: Fido U2F, two-factor authentication support

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 There is an experimental add-on being worked on that tries bring U2F support to Firefox. The source code is at , but it has not yet gone through the Add-on review process. Btw, the most important thing about

Re: Fido U2F, two-factor authentication support

+1 I would love love love to have U2F in Firefox. (Also, Dropbox supports it too, just as a data point: http://blogs.dropbox.com/dropbox/2015/08/u2f-security-keys/ ) On Thu, Nov 5, 2015 at 5:18 PM, Jeroen Hoek wrote: > In December 2014 the first public release of the Fido

Fido U2F, two-factor authentication support

In December 2014 the first public release of the Fido alliance's Universal 2nd Factor (U2F) specification was published. The idea behind this open specification is to provide a secure two-factor authentication method with affordable hardware keys and a friendly UX. If I buy a hardware key that

Re: Now measuring Firefox size per-commit. What else should we be tracking?

On Wednesday 2015-11-04 12:46 -0500, William Lachance wrote: > On 2015-11-04 10:55 AM, William Lachance wrote: > > > >1. Relatively deterministic. > >2. Something people actually care about and are willing to act on, on a > >per-commit basis. If you're only going to look at it once a quarter or >

Re: Now measuring Firefox size per-commit. What else should we be tracking?

ActiveData is just a very large data base. An automated-client would be something that periodically runs a query, formats the data and plugs it into a graph. Here's an example of a client side JS tool that runs a query to determine which tests are enabled or skipped:

Long Term Use of Adjust

Hi All, We wanted to follow up on an email sent in May by Winston regarding the Adjust SDK we implemented for the Spring campaign. As a reminder, mobile installs come from App Stores, and it's challenging to integrate directly to those systems. That’s where the Adjust SDK came in. This tool has

Re: Now measuring Firefox size per-commit. What else should we be tracking?

Al,, ActiveData[1] is warehouse of our test times, build times, and whatever other properties or measures I can get my hands on. It has a primitive query tool[2] that a human can use to send queries to the public service [3]. The `unittest` table has results from all tests that emit

Re: Merging comm-central into mozilla-central

This thread has quieted down for a while, but I don't want to let it die out without a clear consensus being reached. What I want to know is whether or not there is sufficient consensus for the merge to happen that I can start planning with release engineering and automation on getting merged