mozilla.governance Google Group

Stop Watching Us

2013-06-11T15:05:13Z

I love the new [link] initiative but I am a bit sad it is so US centric.

I understand it is mainly targeted at the NSA and the warrantless spying on US citizens, but as a foreigner I would still like to add my name to the list. Specially since the same thing is happening in my country of origin (Holland) and where i live now (Canada).

On architectural security as a strategy for making good on privacy promises

2013-06-10T02:44:30Z

With the recent unfortunate revelations about the NSA PRISM program, there
have been a number of people making note of Mozilla not being one of the
named participating parties. While the overall situation is horrible,
personally I think it's fantastic to see Mozilla's greater-than-usual
commitment to privacy acknowledged.

Help Develop a User Data and Services Code

2013-06-06T23:00:46Z

We are looking for 3-5 Mozilla contributors who have a passion for safe, secure, private, and trustworthy user experiences and would like to join us for a full day meeting in San Francisco on Tuesday, June 25, 2013.

The purpose of this meeting will be to write a new code of practice for user data and services. The aim of this code is to articulate our commitments to user safety, security, and privacy and establish accountability for achieving those goals. The code will build on the Mozilla Manifesto and the existing six Mozilla privacy principles.

Module Proposal: jsat

2013-06-03T17:26:32Z

Hi governance,

We have a project that sits in:
accessible/src/jsat

It is where we house the built-in assistive technology (AT) user facing
layer (primarily screen reader and braille right now) primarily driven
by user needs on Android and FF OS. The remainder of accessible/ deals
primarily with the gecko accessibility engine which serves up

Device Storage Module

2013-05-15T16:30:55Z

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]

Request: Change mozilla policy about addons which are against web openness and users rights

2013-05-13T19:50:43Z

Hi,

Please take a look at:
[link]

The above addon helps our government to censor web and internet which is against the openness of web and also users rights. In Iran government filtered people access to many, many websites, web content and internet access. It's clearly against the mission of mozilla and even human rights.

Proposal: Use UTC timezone for meetings

2013-05-12T12:25:58Z

Hi,

After a long discussion on mozillians list
<[link]>,
I want to bring this topic here with a proposal:

"In all Mozilla meetings, always include UTC
<[link]> times, you

New module proposal: Web Audio

2013-05-09T18:29:08Z

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

Privacy policy update for Firefox Health Report

2013-05-06T23:12:00Z

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.

Sharing information with Mozillians only

2013-04-16T19:54:09Z

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.

Modules proposal: documenting existing webdev modules

2013-04-11T19:11:15Z

Ahoy!

We have quite a few major web products, properties or services that have not been properly documented as modules. See list below:
[link]

This has created confusion at times around:
1. who owns what

Re: Android single locale Aurora builds are back

2013-04-10T13:41:07Z

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

2013-04-04T18:57:45Z

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.

How and where to search for help at Mozilla

2013-04-04T17:39:56Z

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

Proposal: Push Notifications Module

2013-03-31T06:51:21Z

Hi,
I'm proposing we create a Push Notifications module. I am also
proposing that I should be the module owner and Nikhil Marathe be a
peer. This work has lived in the current DOM module. However, unlike
much of what exists in the DOM, this work has both client pieces as well
as service components. We have done something like this in the past