New module owner for Loop/Firefox Hello
Hi, governance. I'm shifting my role around a bit, and won't be dedicating as much time to Loop (aka Firefox Hello)[1] as I have in the past. At the same time, Mark Banner has been increasingly taking on the responsibilities associated with module ownership for Hello, and is well suited to take on the remaining tasks. I'd like to formalize this by stepping down as owner, and handing that mantle off to Mark. Sound good? [1] https://wiki.mozilla.org/Modules/All#Loop_aka_Firefox_Hello -- Adam Roach Principal Platform Engineer a...@mozilla.com +1 650 903 0800 x863 ___ governance mailing list governance@lists.mozilla.org https://lists.mozilla.org/listinfo/governance
Re: New module owner for Loop/Firefox Hello
Mark has experience being both a peer and I believe owner of Thunderbird I'm confident he will do well as owner of Loop. On Mon, Nov 23, 2015 at 8:55 AM Adam Roach wrote: > Hi, governance. > > I'm shifting my role around a bit, and won't be dedicating as much time > to Loop (aka Firefox Hello)[1] as I have in the past. At the same time, > Mark Banner has been increasingly taking on the responsibilities > associated with module ownership for Hello, and is well suited to take > on the remaining tasks. > > I'd like to formalize this by stepping down as owner, and handing that > mantle off to Mark. Sound good? > > > [1] https://wiki.mozilla.org/Modules/All#Loop_aka_Firefox_Hello > > -- > Adam Roach > Principal Platform Engineer > a...@mozilla.com > +1 650 903 0800 x863 > ___ > governance mailing list > governance@lists.mozilla.org > https://lists.mozilla.org/listinfo/governance > ___ governance mailing list governance@lists.mozilla.org https://lists.mozilla.org/listinfo/governance
Re: New module owner for Content Security
Sounds great! On 2015-11-20 7:12 PM, Jonas Sicking wrote: Sounds good to me! / Jonas On Thu, Nov 19, 2015 at 1:44 PM, Johnny Stenback wrote: +1, also, hi Sid! :) - jst On Thu, Nov 19, 2015 at 1:43 PM, wrote: Hi Governance people, Recently I've not been as active in the content security work as I wanted to be, so I've decided to step down as the module owner for Content Security[0]. I want to install Christoph Kerschbaumer as the new module owner because, frankly, he has his fingers in all of the bits of the module and was responsible for most of the major Content Security Policy overhaul we did a couple years ago. He is the most active peer of the module and in my opinion, there is no better steward for this module. What do you think? -Sid [0] https://wiki.mozilla.org/Modules/Core#Content_Security ___ governance mailing list governance@lists.mozilla.org https://lists.mozilla.org/listinfo/governance ___ governance mailing list governance@lists.mozilla.org https://lists.mozilla.org/listinfo/governance ___ governance mailing list governance@lists.mozilla.org https://lists.mozilla.org/listinfo/governance ___ governance mailing list governance@lists.mozilla.org https://lists.mozilla.org/listinfo/governance
Update to Firefox Hello Privacy Notice
Hi everyone, We would like to update our Privacy Notice for Firefox Hello[1], to reflect our usage of Google Analytics and Optimizely for analytics and inform users how to opt-out. Our use of these analytics was already part of our Privacy Notice for all Mozilla websites[2][3], but we wanted to make it clear that this included Firefox Hello. We also wanted to make sure users were provided notice of the opt-out mechanisms for each. Below is the language that we are adding: * **Analytics**: We may also use cookies and third party services to help us understand in the aggregate how users engage with Hello. We use: * Google Analytics, which places a cookie on your device, to obtain metrics on how users engage with Hello. This helps us to improve the Hello service. * Optimizely, which places a cookie on your device, to help us test variations of Hello. This helps us offer better experiences to Hello users. --- You can control individual cookie preferences and opt-out of web analytics and optimization tools. Learn More * **Cookie History**: You can accept or decline individual cookies in the preferences in the appropriate settings within your web browser. For Firefox, this can be found in the Tools/Options/Privacy history section. Note that certain features of Hello may not function properly without the aid of cookies. * **Analytics & Optimization**: If you do not want data about your interaction with Hello to be collected by Google Analytics, you can install the Google Analytics Opt-out Browser Add-on. The add-on keeps your visits anonymous and prohibits data transmission to Google Analytics. If you do not want data about your interaction with Hello to be collected by Optimizely, you can opt-out by visiting Optimizely's opt-out website for more information. You can also see the changes to the privacy policy on Github[4], which we are targeting for November 30, and we look forward to any feedback you might have. Thanks, Elvin [1] https://www.mozilla.org/en-US/privacy/firefox-hello/ [2] https://groups.google.com/forum/#!topic/mozilla.governance/xs7Sfyxc4As [3] https://www.mozilla.org/en-US/privacy/websites/ [4] https://github.com/mozilla/legal-docs/commit/c7535610c36e59d048d5138861058174c77755df ___ governance mailing list governance@lists.mozilla.org https://lists.mozilla.org/listinfo/governance
Re: proposed module: Emeritus Module Owners
On 10/20/15 9:04 AM, Myk Melez wrote: [snip] Regarding the proposal itself, initially it seemed strange to collect emeritus owners into their own module, because it would dissociate them from the modules they formerly owned. I would have expected the status to be an attribute on each module, much as some current owners/peers are marked "inactive" today. But after sitting with it a bit, it makes more sense as a recognition of project leadership (both in the assumption of an ownership role and in its relinquishment). And it could also be a resource for new/emerging leaders who are looking for mentors or role models. So I think it's a good idea. -myk I've sort of come around to your initial thought ... that we collect emeritus folks in each module. That's mostly because the list of owners and peers is a bit more to maintain and having the module folks each do this for their own module is probably best. perhaps we can then make a list of emeritus folks, as jst has done for owners. ml ___ governance mailing list governance@lists.mozilla.org https://lists.mozilla.org/listinfo/governance
