|
Device Storage Module
|
| |
Recently, Doug Turner promoted myself and Jan Varga as owners of the Device Storage module.
I don't see such a module listed on [link] so I'll propose that we add it:
Name: Device Storage
Description: Support for the device storage API [link]... more »
|
|
New module proposal: Web Audio
|
| |
We've been working on implementing the Web Audio specification in Gecko,
and I'd like to make the existing de facto ownership and peer status
official in terms of a new module.
Name: Core::Web Audio
Description: Support for the W3C Web Audio API specification.
Module owner: Ehsan Akhgari
Peers: Robert O'Callahan, Paul Adenot... more »
|
|
Privacy policy update for Firefox Health Report
|
| |
Hi All,
We’re soliciting feedback for proposed privacy policy text describing the Firefox Health Report feature for Firefox:
/begin text
Firefox Health Report (“FHR”) is a feature in Firefox designed to provide you with insights about your browser’s stability and performance. FHR does this by collecting data and sharing it with us in a way designed to minimize our ability to identify your browser. Our systems aggregate your data with that of other Firefox users and then send it back to your browser so you can see how your Firefox performance compares to others. FHR does not send us URLs from your browsing history.... more »
|
|
Sharing information with Mozillians only
|
| |
Hello,
I'm starting this discussion because I found out that the following has happened:
An Etherpad about "needed apps for Firefox OS" was shared amongst all of Reps (URL [1]).
It was soon protected with a password. The password for that etherpad was then posted in a Bug[2] that was restricted to Mozilla Reps only.... more »
|
|
Android single locale Aurora builds are back
|
| |
I guess if we want to make a change we need to bring this discussion to
governance instead of dev-l10.
This is probably a discussion for about 5-10 percent of all Firefox on
Mobile users.
Wim
2013/4/10 F Wolff <frie...@translate.org.za>
|
|
Module Ownership and Peers - Handling the Case Where It's Automation Only Ownership for an Area, Not the Whole Area
|
| |
Hi Everyone,
One issue we're running into right now with WebRTC code management is the fact that Henrik and I can effectively do reviews on automation behind the WebRTC APIs, but can't do reviews on the underlying core code in that area. However, in the module ownership definition for WebRTC right now, our review wouldn't sufficient right now to land tests per what's defined in the WebRTC module, even though there's acceptance from the team that we could provide the "checkmark" to allow something to land on the tests side.... more »
|
|
How and where to search for help at Mozilla
|
| |
Hi,
I would like to open a discussion here about something that I've been
observing more and more at Mozilla, starting probably 2 years ago or so.
When some team or employee (it's not everyone but a big number) needs
help, first tries to hire or pay someone and then, if he can't or needs
extra help, pings the volunteers. This lead to a lot of situations where... more »
|
|
|