MozillaWiki - User contributions [en]

User talk:Trobertson

2018-03-27T16:03:46Z

Bkerensa: Welcome!

'''Welcome to ''MozillaWiki''!'''
We hope you will contribute much and well.
You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages].
Again, welcome and have fun! [[User:Bkerensa|Bkerensa]] ([[User talk:Bkerensa|talk]]) 16:03, 27 March 2018 (UTC)

User:Trobertson

2018-03-27T16:03:46Z

Bkerensa: Creating user page for new user.

Diversity and Inclusion Strategic Partner at Mozilla. I'd like an account so I can add Vancouver restaurant recommendations to the YVR page.

MozillaWiki:Team

2018-03-27T16:01:21Z

Bkerensa: /* Meeting Notes */

__TOC__

== Purpose ==

[[File:Mozilla-wiki-logo-rev.png|frameless|right]]

The purpose of the MozillaWiki team is to facilitate maintenance and improvement of MozillaWiki.

The MozillaWiki team (formerly Wiki Working Group) was formed in early 2014 with the goal of kick-starting a revitalization of the wiki and to create a sustainable framework for empowering the entire Mozilla community to participate in and sustain this effort. We have achieved the first part of this goal (revitalization) and are now working towards incremental feature improvements and creating a framework whereby the entire Mozilla Community can participate in maintaining and improving the wiki.

== Goals ==

Our main goal is to build tools and establish processes that empower Mozillians across functional, product, and regional areas to contribute to collective stewardship of the wiki.

Our 2015 goals include:

* implement feature improvements according to our [[MozillaWiki:Roadmap|roadmap]]
* document MozillaWiki [[MozillaWiki:Policies|policies, procedures and processes]]
* recruit an active group of page patrollers

== How to Participate ==

=== Meetings ===

Bi-weekly MozillaTeam meetings are currently on-hold.

If you want to be involved in the MozillaWiki team, please contact [[User:mhoye | Mike Hoye]],[[User:SpikeUK1 | Chris Foote]] or [[User:bkerensa | Benjamin Kerensa]]. or join one of our communication channels.

=== Meeting Notes ===

{{#subpages:{{FULLPAGENAME}}/Meetings|sort=desc}}

<inputbox>
align=left
type=create
buttonlabel=Create new agenda
preload=Template:Agenda/Mozilla_Wiki/preload
default={{#time: Y-m-d | tuesday}}
prefix=MozillaWiki:Team/Meetings/
</inputbox>

{{#ask:[[Category:Meeting Notes]] [[MozillaWiki:+]]
| sort=modification date
| order=descending
| format=feed
| type=rss
| searchlabel=Mozilla Wiki meeting notes RSS
| title=Mozilla Wiki meeting notes
| page=full
| description=Feed of all notes of Mozilla Wiki team and community calls.
}}

=== Communication Channels ===

==== IRC ====

The IRC channel for MozillaWiki team is {{IRC|wiki}} ([http://chat.mibbit.com/?server=irc.mozilla.org&channel=#wiki webchat]).

==== Discussion Forum ====

* [mailto:tools-wiki@lists.mozilla.org tools-wiki@lists.mozilla.org]
* [https://lists.mozilla.org/listinfo/tools-wiki subscription page] ([mailto:tools-wiki-subscribe@lists.mozilla.org subscribe via email])
* [http://groups.google.com/group/mozilla.tools.wiki google groups page]
* [https://lists.mozilla.org/pipermail/tools-wiki/ archives]
* [news://news.mozilla.org/mozilla.tools.wiki newsgroup]

== Release Processes ==

We release changes to MozillaWiki weekly on Thursdays. We track release planning on [[MozillaWiki:Releases]] subpages. Once the release is complete, post an announcement explaining the changes to [[MozillaWiki:News]].

All feature and change requests are tracked in Bugzilla, under Websites > wiki.mozilla.org.

The process for a feature or change request to be implemented in production is as follows:

# [https://bugzilla.mozilla.org/enter_bug.cgi?product=Websites&component=wiki.mozilla.org File a bug].
# Members of MozillaTeam will triage the bug accordingly, modifying whiteboard, milestone and other fields accordingly.
# The request will be evaluated for suitability on MozillaWiki during a MozillaWiki community call ([[#How_to_Participate|held twice monthly]]). Decisions during community calls are generally made by [http://nowviskie.org/2012/lazy-consensus/ lazy consensus], with MozillaWiki module owners and/or peers making the final call if necessary.
# If MozillaWiki team determines the change should be implemented, it will be rolled out to our development instance first. While it implemented on dev, it will undergo testing and security review (if required).
# Once the change has been tested and passed security review (if required), it will be pushed out to stage and finally production.

=== Requesting features and changes ===

To request a change or feature, please [https://bugzilla.mozilla.org/enter_bug.cgi?product=Websites&component=wiki.mozilla.org file a bug.]

MozillaWiki:Team

2018-03-27T15:52:22Z

Bkerensa: /* Meetings */

__TOC__

== Purpose ==

[[File:Mozilla-wiki-logo-rev.png|frameless|right]]

The purpose of the MozillaWiki team is to facilitate maintenance and improvement of MozillaWiki.

The MozillaWiki team (formerly Wiki Working Group) was formed in early 2014 with the goal of kick-starting a revitalization of the wiki and to create a sustainable framework for empowering the entire Mozilla community to participate in and sustain this effort. We have achieved the first part of this goal (revitalization) and are now working towards incremental feature improvements and creating a framework whereby the entire Mozilla Community can participate in maintaining and improving the wiki.

== Goals ==

Our main goal is to build tools and establish processes that empower Mozillians across functional, product, and regional areas to contribute to collective stewardship of the wiki.

Our 2015 goals include:

* implement feature improvements according to our [[MozillaWiki:Roadmap|roadmap]]
* document MozillaWiki [[MozillaWiki:Policies|policies, procedures and processes]]
* recruit an active group of page patrollers

== How to Participate ==

=== Meetings ===

Bi-weekly MozillaTeam meetings are currently on-hold.

If you want to be involved in the MozillaWiki team, please contact [[User:mhoye | Mike Hoye]],[[User:SpikeUK1 | Chris Foote]] or [[User:bkerensa | Benjamin Kerensa]]. or join one of our communication channels.

=== Meeting Notes ===

{{#subpages:{{FULLPAGENAME}}/Meetings|sort=desc}}

<createbox>
align=left
type=create
buttonlabel=Create new agenda
preload=Template:Agenda/Mozilla_Wiki/preload
default={{#time: Y-m-d | tuesday}}
prefix=MozillaWiki:Team/Meetings/
</createbox>

{{#ask:[[Category:Meeting Notes]] [[MozillaWiki:+]]
| sort=modification date
| order=descending
| format=feed
| type=rss
| searchlabel=Mozilla Wiki meeting notes RSS
| title=Mozilla Wiki meeting notes
| page=full
| description=Feed of all notes of Mozilla Wiki team and community calls.
}}

=== Communication Channels ===

==== IRC ====

The IRC channel for MozillaWiki team is {{IRC|wiki}} ([http://chat.mibbit.com/?server=irc.mozilla.org&channel=#wiki webchat]).

==== Discussion Forum ====

* [mailto:tools-wiki@lists.mozilla.org tools-wiki@lists.mozilla.org]
* [https://lists.mozilla.org/listinfo/tools-wiki subscription page] ([mailto:tools-wiki-subscribe@lists.mozilla.org subscribe via email])
* [http://groups.google.com/group/mozilla.tools.wiki google groups page]
* [https://lists.mozilla.org/pipermail/tools-wiki/ archives]
* [news://news.mozilla.org/mozilla.tools.wiki newsgroup]

== Release Processes ==

We release changes to MozillaWiki weekly on Thursdays. We track release planning on [[MozillaWiki:Releases]] subpages. Once the release is complete, post an announcement explaining the changes to [[MozillaWiki:News]].

All feature and change requests are tracked in Bugzilla, under Websites > wiki.mozilla.org.

The process for a feature or change request to be implemented in production is as follows:

# [https://bugzilla.mozilla.org/enter_bug.cgi?product=Websites&component=wiki.mozilla.org File a bug].
# Members of MozillaTeam will triage the bug accordingly, modifying whiteboard, milestone and other fields accordingly.
# The request will be evaluated for suitability on MozillaWiki during a MozillaWiki community call ([[#How_to_Participate|held twice monthly]]). Decisions during community calls are generally made by [http://nowviskie.org/2012/lazy-consensus/ lazy consensus], with MozillaWiki module owners and/or peers making the final call if necessary.
# If MozillaWiki team determines the change should be implemented, it will be rolled out to our development instance first. While it implemented on dev, it will undergo testing and security review (if required).
# Once the change has been tested and passed security review (if required), it will be pushed out to stage and finally production.

=== Requesting features and changes ===

To request a change or feature, please [https://bugzilla.mozilla.org/enter_bug.cgi?product=Websites&component=wiki.mozilla.org file a bug.]

User talk:Hugo Romano

2017-03-27T20:24:49Z

Bkerensa: Welcome!

User:Hugo Romano

2017-03-27T20:24:42Z

Bkerensa: Creating user page for new user.

Joined Mozilla as part of the Pocket acquisition. Will be working closely with the Firefox team on various projects. Thank you!

User talk:Nateweiner

2017-03-27T20:24:14Z

Bkerensa: Welcome!

User:Nateweiner

2017-03-27T20:24:07Z

Bkerensa: Creating user page for new user.

Would like an account for:
To add wiki entry to Weekly Project Call for Pocket.

Who am I:
Nate Weiner, Founder/CEO at Pocket

User talk:Mkoidin

2017-03-27T20:23:48Z

Bkerensa: Welcome!

User talk:Tkirtane

2017-03-27T20:23:42Z

Bkerensa: Welcome!

User:Mkoidin

2017-03-27T20:23:41Z

Bkerensa: Creating user page for new user.

My professional experience has led me on the search for challenging problems and inadequate customer experiences across a broad spectrum of industries. My specialty is in designing and developing creative ways to leverage technology to solve these problems.

I have extensive experience in technology development and building consumer-facing media businesses. Currently, I am the CTO at Pocket, a platform for shifting content on the web to read or watch whenever and where ever a user wants - on their phone, tablet or computer.

Specialties: data architecture, systems architecture, cloud architecture, web and software development, user interaction and experience design, customer experience

User:Tkirtane

2017-03-27T20:23:36Z

Bkerensa: Creating user page for new user.

I work at Pocket and would like access to edit the wiki to provide updates to the broader Mozilla community on what we're working on!

User talk:Kait

2017-03-27T20:22:55Z

Bkerensa: Welcome!

User:Kait

2017-03-27T20:22:49Z

Bkerensa: Creating user page for new user.

Just joined the Mozilla team via Pocket :) I help build mobile products centered around content discovery at Pocket.

NorthAmerica

2016-12-05T00:42:19Z

Bkerensa: Created page with "Mozilla North America Placeholder"

Mozilla North America

Placeholder

Release Management/Team members

2016-09-22T23:34:10Z

Bkerensa: More improvements

= Current Team =
* Manager: [https://mozillians.org/en-US/u/sylvestre/ Sylvestre Ledru (:sylvestre)]
* Desktop & Mobile RM: [https://mozillians.org/en-US/u/lizhenry/ Liz Henry (:lizzard)]
* Desktop & Mobile RM: [https://mozillians.org/en-US/u/rkothari/ Ritu Kothari (:ritu)]
* Desktop & Mobile RM: [https://mozillians.org/en-US/u/gchang/ Gerry Chang (:gchang)]
* Nightly RM: [https://mozillians.org/en-US/u/marcia/ Marcia Knous (:marcia)]
* Nightly PM: [https://mozillians.org/en-US/u/pascalc/ Pascal Chevrel (:pascalc)]
* Release Engineer: [https://mozillians.org/en-US/u/cdenizet/ Calixte Denizet (:calixte)]
* Release Engineer: [https://mozillians.org/en-US/u/marco/ Marco Castelluccio (:marco)]
* Static Analyzer Specialist: [https://mozillians.org/en-US/u/bpostelnicu/ Andi Bogdan Postelnicu]

[[File:Relman-team.JPG|frame|300px|Release Management Team - Paris, Nov 2015]]

{{clear}}

= Release Management Alumni =

* Release Quality Manager: [https://mozillians.org/fr/u/KaiRo/ Robert Kaiser (:KaiRo)]
* Staff Release Manager: [https://mozillians.org/en-US/u/lsblakk/ Lukas Blakk (:lsblakk)]
* Manager: [https://mozillians.org/en-US/u/lmandel/ Lawrence Mandel (:lmandel)]
* Manager: Alex Keybl (:akeybl)
* FirefoxOS/B2G Release Manager: [https://mozillians.org/en-US/u/Bhavana/ Bhavana Bajaj (:bajaj)]
* FirefoxOS/B2G Release Manager: [https://mozillians.org/en-US/u/preeti/ Preeti Raghunath (:preeti) ]
* Early Feedback Community RM: [https://mozillians.org/en-US/u/bkerensa/ Benjamin Kerensa (:bkerensa) ]
* 2015 Intern/ESR release: [https://mozillians.org/en-US/u/kglazko/ Kate Glazko]
* 2013 Intern: [https://mozillians.org/en-US/u/wcheong/ Willie Cheong]
* 2012 Intern: [https://mozillians.org/en-US/u/lianne719/ Lianne Lee]

[[File:Relman-team2014.JPG|frame|300px|Release Management Team - Portland workweek (2014)]]
{{clear}}

=Team Blogs=

* Liz Henry [http://bookmaniac.org http://bookmaniac.org] Twitter: [https://twitter.com/lizhenry @lizhenry]
* Lukas Blakk [http://lukasblakk.com/ http://lukasblakk.com] Twitter: [https://twitter.com/lsblakk @lsblakk]
* Bhavana Bajaj [https://twitter.com/tweetbhavana twitter:@tweetbhavana]
* Benjamin Kerensa [http://benjaminkerensa.com http://benjaminkerensa.com] Twitter: [https://twitter.com/bkerensa @bkerensa]
* Sylvestre Ledru [http://sylvestre.ledru.info/blog/ http://sylvestre.ledru.info/blog/] Twitter: [https://twitter.com/SylvestreLedru @SylvestreLedru]
* Lawrence Mandel [http://lawrencemandel.com/ http://lawrencemandel.com/] Twitter: [https://twitter.com/mmmandel @mmmandel]
* Marcia Knous [http://mozillamarciaknous.wixsite.com/mozcommunity http://mozillamarciaknous.wixsite.com/mozcommunity] Twitter: [https://twitter.com/MozCommunity @MozCommunity]

[[category:Release_Management]]

Release Management/Team members

2016-09-22T23:30:14Z

Bkerensa: Filling in some gaps ;)

= Current Team =
* Manager: [https://mozillians.org/en-US/u/sylvestre/ Sylvestre Ledru (:sylvestre)]
* Desktop & Mobile RM: [https://mozillians.org/en-US/u/lizhenry/ Liz Henry (:lizzard)]
* Desktop & Mobile RM: [https://mozillians.org/en-US/u/rkothari/ Ritu Kothari (:ritu)]
* Desktop & Mobile RM: Gerry Chang (:gchang)
* Nightly RM: [https://mozillians.org/en-US/u/marcia/ Marcia Knous (:marcia)]
* Nightly project manager: Pascal Chevrel (:pascalc)
* Release Engineer: Calixte Denizet (:calixte)
* Release Engineer: Marco Castelluccio (:marco)
* Static analyzer specialist: Andi Bogdan Postelnicu

[[File:Relman-team.JPG|frame|300px|Release Management Team - Paris, Nov 2015]]

{{clear}}

= Release Management Alumni =

* Release Quality Manager: [https://mozillians.org/fr/u/KaiRo/ Robert Kaiser (:KaiRo)]
* Staff Release Manager: [https://mozillians.org/en-US/u/lsblakk/ Lukas Blakk (:lsblakk)]
* Manager: [https://mozillians.org/en-US/u/lmandel/ Lawrence Mandel (:lmandel)]
* Manager: Alex Keybl (:akeybl)
* FirefoxOS/B2G Release Manager: [https://mozillians.org/en-US/u/Bhavana/ Bhavana Bajaj (:bajaj)]
* FirefoxOS/B2G Release Manager: [https://mozillians.org/en-US/u/preeti/ Preeti Raghunath (:preeti) ]
* Early Feedback Community RM: [https://mozillians.org/en-US/u/bkerensa/ Benjamin Kerensa (:bkerensa) ]
* 2015 Intern/ESR release: [https://mozillians.org/en-US/u/kglazko/ Kate Glazko]
* 2013 Intern: [https://mozillians.org/en-US/u/wcheong/ Willie Cheong]
* 2012 Intern: [https://mozillians.org/en-US/u/lianne719/ Lianne Lee]

[[File:Relman-team2014.JPG|frame|300px|Release Management Team - Portland workweek (2014)]]
{{clear}}

=Team Blogs=

* Liz Henry [http://bookmaniac.org http://bookmaniac.org] Twitter: [https://twitter.com/lizhenry @lizhenry]
* Lukas Blakk [http://lukasblakk.com/ http://lukasblakk.com] Twitter: [https://twitter.com/lsblakk @lsblakk]
* Bhavana Bajaj [https://twitter.com/tweetbhavana twitter:@tweetbhavana]
* Benjamin Kerensa [http://benjaminkerensa.com http://benjaminkerensa.com] Twitter: [https://twitter.com/bkerensa @bkerensa]
* Sylvestre Ledru [http://sylvestre.ledru.info/blog/ http://sylvestre.ledru.info/blog/] Twitter: [https://twitter.com/SylvestreLedru @SylvestreLedru]
* Lawrence Mandel [http://lawrencemandel.com/ http://lawrencemandel.com/] Twitter: [https://twitter.com/mmmandel @mmmandel]
* Marcia Knous [http://mozillamarciaknous.wixsite.com/mozcommunity http://mozillamarciaknous.wixsite.com/mozcommunity] Twitter: [https://twitter.com/MozCommunity @MozCommunity]

[[category:Release_Management]]

Modules/Activities

2016-01-26T03:15:04Z

Bkerensa: Add Mitchell Owner and Moved Brendan to Emeritus Status

<noinclude>
'''Only module owners may edit this page.'''

They may:

* update any information about their module except the name of the owner
* add or remove sub-modules
* change the owner of a sub-module
* add emeritus owners or peers

Other changes, including changes of module owner or addition/removal of modules, must be agreed with the Module Ownership Module group, probably via a discussion in [https://www.mozilla.org/about/forums/#governance mozilla.governance].
</noinclude>
{{Module
|name=Governance
|description=Policies and process for how we distribute authority and govern ourselves; including:
* Development and Implementation of new policies as appropriate for delegation of authority and responsibility
* Management of the source tree
* Balancing different constituencies of the Mozilla project
* Maintaining the Mozilla identity as we take on new activities

[http://www.mozilla.org/about/roles.html#ultimate-decision-makers Ultimate authority] within the project rests with the owner and peer(s) of this module, and project decisions can be escalated to here.
|owner=[mailto:mitchell@mozilla.org Mitchell Baker]
|peers=
|peersemeritus=Brendan Eich
|group=governance
|url=https://wiki.mozilla.org/GovernanceIssues
|components=mozilla.org::Governance
}}

===Governance Sub Modules===

{{Module
|name=Module Ownership System
|description=Healthy operation of the module ownership system, including topics such as:
* Filling vacant roles where appropriate
* Ensuring module owners are fulfilling their responsibilities, and replacing those who are not
* Creating and staffing new modules where new parts of the project evolve.
* Figuring out what to do if a module isn't getting enough attention
* Resolving conflicts among module owners
|owner= [mailto:mitchell@mozilla.org Mitchell Baker]
|peers=[mailto:pavlov@pavlov.net Stuart Parmenter], [mailto:dmose@mozilla.org Dan Mosedale], [mailto:kairo@kairo.at Robert Kaiser], [mailto:mconnor@steelgryphon.com Mike Connor], [mailto:dbaron@dbaron.org David Baron], [mailto:dascher@mozilla.com David Ascher], [mailto:mitchell@mozilla.org Mitchell Baker]. Guillermo Movia is an 'observer'. (This is a new role we're trying out as of Jan 2012. The observers are watching and learning how the module operates, since there's no code in this module to serve as a learning /participation tool.)
|ownersemeritus=Brendan Eich
|url=
|components=
}}

{{Module
|name=Commit Access Policy
|description=
|owner=[mailto:mitchell@mozilla.org Mitchell Baker]
|peers=
|group=
|url=http://www.mozilla.org/hacking/committer/
|components=mozilla.org::Miscellaneous
}}

{{Module
|name=Commit Access Implementation
|description= Governance structure for the work of enforcing and implementing Mozilla's commit access policy.
|owner=[mailto:marcia@mozilla.com Marcia Knous]
|peers=[mailto:jmatthews@mozilla.com Josh Matthews]
|group=
|url=https://wiki.mozilla.org/Commit_Access_Implementation_module
|components=mozilla.org::Repository Account Requests
}}

{{Module
|name=Security Policy
|description=
|owner=[mailto:dveditz@mozilla.com Dan Veditz]
|peers=[mailto:security@mozilla.org Al Billings]
|group=dev-security
|url=http://www.mozilla.org/security/
|components=
}}

{{Module
|name=Mozilla CA Certificate Policy
|description=
|owner=[mailto:kwilson@mozilla.com Kathleen Wilson]
|peers=[mailto:gerv@mozilla.org Gervase Markham], [mailto:rbarnes@mozilla.com Richard Barnes], [mailto:sid@mozilla.com Sid Stamm]
|ownersemeritus=Frank Hecker
|group=dev-security-policy
|url=http://www.mozilla.org/projects/security/certs/policy/
|components=
}}

{{Module
|name=Code Review Policy
|description=
|owner=[mailto:mitchell@mozilla.org Mitchell Baker]
|peers=
|peersemeritus=Brendan Eich
|group=
|url=http://www.mozilla.org/hacking/reviewers.html
|components=
}}

{{Module
|name=Performance Regression Policy
|description=
|owner=[mailto:mitchell@mozilla.org Mitchell Baker]
|peers=
|group=
|url=
|components=
}}

{{Module
|name=Planet Mozilla
|description=Content and policy for planet.mozilla.org, including topics such as:
* which blogs are syndicated to planet.mozilla.org
* which content from syndicated blogs is included
* other planet.mozilla.org policy issues
|owner=[mailto:robert@accettura.com Robert Accettura]
|peers=[mailto:reed@reedloden.com Reed Loden], [mailto:mhoye@mozilla.com Mike Hoye] -- collectively, [mailto:planet@mozilla.org planet@mozilla.org] (preferred)
|group=
|url=
|components=Websites::planet.mozilla.org
}}

{{Module
|name=Mozilla Public License
|description=Maintenance and development of the MPL
* changes in the legal landscape which could /should be reflected
* changes in FLOSS development practices which could / should be reflected
|owner=[mailto:mitchell@mozilla.org Mitchell Baker]
|peers=[mailto:handerson@mozilla.com Harvey Anderson], [mailto:gerv@mozilla.org Gervase Markham], [mailto:MeekerH@gtlaw.com Heather Meeker], [mailto:villalu@gtlaw.com Luis Villa]
|group=governance-mpl-update
|url=
|components=mozilla.org::Licensing
}}

{{Module
|name=CA Certificates
|description=Determine which root certificates should be included in Mozilla software products, which trust bits should be set on them, and which of them should be enabled for EV treatment. Evaluate requests from Certification Authorities (CAs) for inclusion or removal of root certificates, and for updating trust bit settings or enabling EV treatment for already included root certificates.
|owner=[mailto:kwilson@mozilla.com Kathleen Wilson]
|peers=[mailto:gerv@mozilla.org Gervase Markham], [mailto:rbarnes@mozilla.com Richard Barnes], [mailto:sleevi@google.com Ryan Sleevi], [mailto:sid@mozilla.com Sid Stamm]
|group=dev-security-policy
|url=http://www.mozilla.org/projects/security/certs/policy/
|components=mozilla.org::CA Certificates
}}

{{Module
|name=Participation Metrics
|description=Develop, monitor and analyze metrics relating to participation in the Mozilla project, including such things as:
* determining which questions are most important to ask (how many people do X?)
* determining what data is relevant to answer these questions
* designing and operating a system to generate the requested data
* analyzing the resulting metrics
* notifying appropriate people when participation starts to change significantly
* assisting various groups to understand and use the metrics to strengthen participation
* produce periodic report/analysis of participation metrics
|owner=[mailto:ppapadeas@mozilla.com Pierros Papadeas]
|peers=[mailto:dboswell@mozilla.com David Boswell], [mailto:asa@mozilla.com Asa Dotzler], [mailto:deinspanjer@mozilla.com Daniel Einspanjer], [mailto:aelliott@mozilla.com Annie Elliott], [mailto:david@eaves.ca David Eaves], [mailto:michelle@mozillafoundation.org Michelle Thorne], [mailto:ryan@mozillafoundation.org Ryan Merkley]
|group=
|url=https://wiki.mozilla.org/Contribute/Dashboards
|components=
}}

{{Module
|name=Productive Communications Module (aka the "Conductors")
|description=Promotion of productive communications styles within Mozilla, where "productive" means simultaneously honest and civil. This includes topics such as:
*coaching people on who to respond to nasty settings;
*coaching people to think a little before they hit post/send/submit.
*coaching people on how to be direct and yet civil, notifying people they are at or past the boundary;
*coaching people to recognize legitimate comments/ complaints / differences of opinion despite poor communication style
*redirecting conversations into a better place,
*building a culture of respect in how we communicate with difficult and contentious issues
*when necessary, letting people know they've gone beyond the boundaries.
|owner=[mailto:stormy@mozilla.com Stormy Peters]
|peers=David Ascher , Dietrich Ayala, Mike Beltzner, Matt Claypotch, David Eaves, Gen Kanai, Michelle Luna, Kev Needham, Johnathan Nightingale, Melissa Shapiro, Gavin Sharp, Benjamin Smedberg, Mike Taylor (Bear), David Tenser, Daniel Veditz - collectively, [mailto:conductors@mozilla.org conductors@mozilla.org].
|group=mozilla.governance
|url=http://wiki.mozilla.org/Conductors
|components=
}}

{{Module
|name=Internet Public Policy
|description=Mozilla activities related to Public Policy issues that affect the health of the Internet. Our working definition of Public Policy is taken from Wikipedia: "courses of action, regulatory measures, laws, and funding priorities concerning a given topic promulgated by a governmental entity or its representatives."
This includes topics such as:
*determining if Mozilla should take an official position on a particular public policy issue
*determining what that position is
*determining how mozilla communicates our position
**global, multi-regional, regional or local action
**direct action, or support of action by other aligned groups
**public campaigns or opinion pieces or educational activities, dialog with policy makers, other techniques TBD
*strengthening local community capabilities to address public policy issues
|owner=[mailto:handerson@mozilla.com Harvey Anderson]
|peers=[mailto:mitchell@mozilla.org Mitchell Baker], [mailto:afowler@mozilla.com Alex Fowler], [mailto:mark@mozillafoundation.org Mark Surman]
|advisors=Katharina Borchert, Andrew Bridges, Hanno Kaiser, Andrew McLaughlin, Danny Weitzner, Gene Kimmelman, and Ronaldo Lemos
|url=https://wiki.mozilla.org/Netpolicy
|group=https://mail.mozilla.org/listinfo/netpolicy
|components=
}}
Area Expert Advisors are people with particular expertise who have agreed to assist Mozilla with their area-specific expertise. The Area Expert Advisors are different from peers. A peer is someone to whom the module owner has delegated some of her/his authority and a peer is expected to provide leadership for Mozilla within our specific context. Area Expert Advisors are advisors to Mozilla. They may become peers, but they need not.

{{Module
|name=Weekly Project All Hands Meeting
|description=Responsibility for the weekly meetings, including:
* determining and implementing the best organization and structure for the meeting
* Determining and implementing the most useful content
* Identifying and implementing technical means to make the meeting accessible and interactive for participants around the globe
|owner=[mailto:potch@mozilla.com Matt Claypotch]
|peers=[mailto:asa@mozilla.org Asa Dotzler], MoCo Desktop IT services
|group=mozilla.governance
|url=https://wiki.mozilla.org/WeeklyUpdates
|components=
}}

(It's a new thing to have a group such as "MoCo Desktop IT services" as a
"peer." We're trying this based on the idea that anyone in the Desktop IT group
should be able to resolve problems and make fixes to the systems.)

===Other===

{{Module
|name=Popcorn Events
|description=Events to support and grow the popcorn project. These include hack days pairing web developers and media creators, as well as Learning Labs to teach popcorn.js and Popcorn Maker.
|owner=[mailto:brett@mozillafoundation.org Brett Gaylor]
|peers=[mailto:michelle@mozillafoundation.org Michelle Thorne]
|group=mozilla.community.popcorn
|url=http://www.mozillapopcorn.org/
|components=
}}

{{Module
|name=Tree Sheriffs
|description=Tree Sheriffs aid developers to easily, quickly, and seamlessly land their code in the proper location(s) and ensure that code does not break our automated tests. In the service of this objective, the Sheriffs work closely with the larger engineering organization to create and enforce landing policies that increase productivity while maintaining an efficient and robust automated testing system. Beyond the policy role, they have also become shepherds of automation quality by monitoring intermittent failures, performing uplifts and merges, and identifying poorly performing automation machines.
|owner=[mailto:rvandermeulen@mozilla.com Ryan VanderMeulen (RyanVM)]
|peers=[mailto:wkocher@mozilla.com Wes Kocher (KWierso)], [mailto:cbook@mozilla.com Carsten Book (Tomcat)]
|group=dev-tree-management
|url=https://wiki.mozilla.org/Sheriffing
|components=Tree Management::Visibility Requests
}}

Modules/Activities

2016-01-25T22:19:59Z

Bkerensa: /* Governance Sub Modules */

<noinclude>
'''Only module owners may edit this page.'''

They may:

* update any information about their module except the name of the owner
* add or remove sub-modules
* change the owner of a sub-module
* add emeritus owners or peers

Other changes, including changes of module owner or addition/removal of modules, must be agreed with the Module Ownership Module group, probably via a discussion in [https://www.mozilla.org/about/forums/#governance mozilla.governance].
</noinclude>
{{Module
|name=Governance
|description=Policies and process for how we distribute authority and govern ourselves; including:
* Development and Implementation of new policies as appropriate for delegation of authority and responsibility
* Management of the source tree
* Balancing different constituencies of the Mozilla project
* Maintaining the Mozilla identity as we take on new activities

[http://www.mozilla.org/about/roles.html#ultimate-decision-makers Ultimate authority] within the project rests with the owner and peer(s) of this module, and project decisions can be escalated to here.
|owner=[mailto:mitchell@mozilla.org Mitchell Baker]
|peers=[mailto:brendan@mozilla.org Brendan Eich]
|group=governance
|url=https://wiki.mozilla.org/GovernanceIssues
|components=mozilla.org::Governance
}}

===Governance Sub Modules===

{{Module
|name=Module Ownership System
|description=Healthy operation of the module ownership system, including topics such as:
* Filling vacant roles where appropriate
* Ensuring module owners are fulfilling their responsibilities, and replacing those who are not
* Creating and staffing new modules where new parts of the project evolve.
* Figuring out what to do if a module isn't getting enough attention
* Resolving conflicts among module owners
|owner=
|peers=[mailto:pavlov@pavlov.net Stuart Parmenter], [mailto:dmose@mozilla.org Dan Mosedale], [mailto:kairo@kairo.at Robert Kaiser], [mailto:mconnor@steelgryphon.com Mike Connor], [mailto:dbaron@dbaron.org David Baron], [mailto:dascher@mozilla.com David Ascher], [mailto:mitchell@mozilla.org Mitchell Baker]. Guillermo Movia is an 'observer'. (This is a new role we're trying out as of Jan 2012. The observers are watching and learning how the module operates, since there's no code in this module to serve as a learning /participation tool.)
|ownersemeritus=Brendan Eich
|url=
|components=
}}

{{Module
|name=Commit Access Policy
|description=
|owner=[mailto:mitchell@mozilla.org Mitchell Baker]
|peers=
|group=
|url=http://www.mozilla.org/hacking/committer/
|components=mozilla.org::Miscellaneous
}}

{{Module
|name=Commit Access Implementation
|description= Governance structure for the work of enforcing and implementing Mozilla's commit access policy.
|owner=[mailto:marcia@mozilla.com Marcia Knous]
|peers=[mailto:jmatthews@mozilla.com Josh Matthews]
|group=
|url=https://wiki.mozilla.org/Commit_Access_Implementation_module
|components=mozilla.org::Repository Account Requests
}}

{{Module
|name=Security Policy
|description=
|owner=[mailto:dveditz@mozilla.com Dan Veditz]
|peers=[mailto:security@mozilla.org Al Billings]
|group=dev-security
|url=http://www.mozilla.org/security/
|components=
}}

{{Module
|name=Mozilla CA Certificate Policy
|description=
|owner=[mailto:kwilson@mozilla.com Kathleen Wilson]
|peers=[mailto:gerv@mozilla.org Gervase Markham], [mailto:rbarnes@mozilla.com Richard Barnes], [mailto:sid@mozilla.com Sid Stamm]
|ownersemeritus=Frank Hecker
|group=dev-security-policy
|url=http://www.mozilla.org/projects/security/certs/policy/
|components=
}}

{{Module
|name=Code Review Policy
|description=
|owner=[mailto:mitchell@mozilla.org Mitchell Baker]
|peers=
|peersemeritus=Brendan Eich
|group=
|url=http://www.mozilla.org/hacking/reviewers.html
|components=
}}

{{Module
|name=Performance Regression Policy
|description=
|owner=[mailto:mitchell@mozilla.org Mitchell Baker]
|peers=
|group=
|url=
|components=
}}

{{Module
|name=Planet Mozilla
|description=Content and policy for planet.mozilla.org, including topics such as:
* which blogs are syndicated to planet.mozilla.org
* which content from syndicated blogs is included
* other planet.mozilla.org policy issues
|owner=[mailto:robert@accettura.com Robert Accettura]
|peers=[mailto:reed@reedloden.com Reed Loden], [mailto:mhoye@mozilla.com Mike Hoye] -- collectively, [mailto:planet@mozilla.org planet@mozilla.org] (preferred)
|group=
|url=
|components=Websites::planet.mozilla.org
}}

{{Module
|name=Mozilla Public License
|description=Maintenance and development of the MPL
* changes in the legal landscape which could /should be reflected
* changes in FLOSS development practices which could / should be reflected
|owner=[mailto:mitchell@mozilla.org Mitchell Baker]
|peers=[mailto:handerson@mozilla.com Harvey Anderson], [mailto:gerv@mozilla.org Gervase Markham], [mailto:MeekerH@gtlaw.com Heather Meeker], [mailto:villalu@gtlaw.com Luis Villa]
|group=governance-mpl-update
|url=
|components=mozilla.org::Licensing
}}

{{Module
|name=CA Certificates
|description=Determine which root certificates should be included in Mozilla software products, which trust bits should be set on them, and which of them should be enabled for EV treatment. Evaluate requests from Certification Authorities (CAs) for inclusion or removal of root certificates, and for updating trust bit settings or enabling EV treatment for already included root certificates.
|owner=[mailto:kwilson@mozilla.com Kathleen Wilson]
|peers=[mailto:gerv@mozilla.org Gervase Markham], [mailto:rbarnes@mozilla.com Richard Barnes], [mailto:sleevi@google.com Ryan Sleevi], [mailto:sid@mozilla.com Sid Stamm]
|group=dev-security-policy
|url=http://www.mozilla.org/projects/security/certs/policy/
|components=mozilla.org::CA Certificates
}}

{{Module
|name=Participation Metrics
|description=Develop, monitor and analyze metrics relating to participation in the Mozilla project, including such things as:
* determining which questions are most important to ask (how many people do X?)
* determining what data is relevant to answer these questions
* designing and operating a system to generate the requested data
* analyzing the resulting metrics
* notifying appropriate people when participation starts to change significantly
* assisting various groups to understand and use the metrics to strengthen participation
* produce periodic report/analysis of participation metrics
|owner=[mailto:ppapadeas@mozilla.com Pierros Papadeas]
|peers=[mailto:dboswell@mozilla.com David Boswell], [mailto:asa@mozilla.com Asa Dotzler], [mailto:deinspanjer@mozilla.com Daniel Einspanjer], [mailto:aelliott@mozilla.com Annie Elliott], [mailto:david@eaves.ca David Eaves], [mailto:michelle@mozillafoundation.org Michelle Thorne], [mailto:ryan@mozillafoundation.org Ryan Merkley]
|group=
|url=https://wiki.mozilla.org/Contribute/Dashboards
|components=
}}

{{Module
|name=Productive Communications Module (aka the "Conductors")
|description=Promotion of productive communications styles within Mozilla, where "productive" means simultaneously honest and civil. This includes topics such as:
*coaching people on who to respond to nasty settings;
*coaching people to think a little before they hit post/send/submit.
*coaching people on how to be direct and yet civil, notifying people they are at or past the boundary;
*coaching people to recognize legitimate comments/ complaints / differences of opinion despite poor communication style
*redirecting conversations into a better place,
*building a culture of respect in how we communicate with difficult and contentious issues
*when necessary, letting people know they've gone beyond the boundaries.
|owner=[mailto:stormy@mozilla.com Stormy Peters]
|peers=David Ascher , Dietrich Ayala, Mike Beltzner, Matt Claypotch, David Eaves, Gen Kanai, Michelle Luna, Kev Needham, Johnathan Nightingale, Melissa Shapiro, Gavin Sharp, Benjamin Smedberg, Mike Taylor (Bear), David Tenser, Daniel Veditz - collectively, [mailto:conductors@mozilla.org conductors@mozilla.org].
|group=mozilla.governance
|url=http://wiki.mozilla.org/Conductors
|components=
}}

{{Module
|name=Internet Public Policy
|description=Mozilla activities related to Public Policy issues that affect the health of the Internet. Our working definition of Public Policy is taken from Wikipedia: "courses of action, regulatory measures, laws, and funding priorities concerning a given topic promulgated by a governmental entity or its representatives."
This includes topics such as:
*determining if Mozilla should take an official position on a particular public policy issue
*determining what that position is
*determining how mozilla communicates our position
**global, multi-regional, regional or local action
**direct action, or support of action by other aligned groups
**public campaigns or opinion pieces or educational activities, dialog with policy makers, other techniques TBD
*strengthening local community capabilities to address public policy issues
|owner=[mailto:handerson@mozilla.com Harvey Anderson]
|peers=[mailto:mitchell@mozilla.org Mitchell Baker], [mailto:afowler@mozilla.com Alex Fowler], [mailto:mark@mozillafoundation.org Mark Surman]
|advisors=Katharina Borchert, Andrew Bridges, Hanno Kaiser, Andrew McLaughlin, Danny Weitzner, Gene Kimmelman, and Ronaldo Lemos
|url=https://wiki.mozilla.org/Netpolicy
|group=https://mail.mozilla.org/listinfo/netpolicy
|components=
}}
Area Expert Advisors are people with particular expertise who have agreed to assist Mozilla with their area-specific expertise. The Area Expert Advisors are different from peers. A peer is someone to whom the module owner has delegated some of her/his authority and a peer is expected to provide leadership for Mozilla within our specific context. Area Expert Advisors are advisors to Mozilla. They may become peers, but they need not.

{{Module
|name=Weekly Project All Hands Meeting
|description=Responsibility for the weekly meetings, including:
* determining and implementing the best organization and structure for the meeting
* Determining and implementing the most useful content
* Identifying and implementing technical means to make the meeting accessible and interactive for participants around the globe
|owner=[mailto:potch@mozilla.com Matt Claypotch]
|peers=[mailto:asa@mozilla.org Asa Dotzler], MoCo Desktop IT services
|group=mozilla.governance
|url=https://wiki.mozilla.org/WeeklyUpdates
|components=
}}

(It's a new thing to have a group such as "MoCo Desktop IT services" as a
"peer." We're trying this based on the idea that anyone in the Desktop IT group
should be able to resolve problems and make fixes to the systems.)

===Other===

{{Module
|name=Popcorn Events
|description=Events to support and grow the popcorn project. These include hack days pairing web developers and media creators, as well as Learning Labs to teach popcorn.js and Popcorn Maker.
|owner=[mailto:brett@mozillafoundation.org Brett Gaylor]
|peers=[mailto:michelle@mozillafoundation.org Michelle Thorne]
|group=mozilla.community.popcorn
|url=http://www.mozillapopcorn.org/
|components=
}}

{{Module
|name=Tree Sheriffs
|description=Tree Sheriffs aid developers to easily, quickly, and seamlessly land their code in the proper location(s) and ensure that code does not break our automated tests. In the service of this objective, the Sheriffs work closely with the larger engineering organization to create and enforce landing policies that increase productivity while maintaining an efficient and robust automated testing system. Beyond the policy role, they have also become shepherds of automation quality by monitoring intermittent failures, performing uplifts and merges, and identifying poorly performing automation machines.
|owner=[mailto:rvandermeulen@mozilla.com Ryan VanderMeulen (RyanVM)]
|peers=[mailto:wkocher@mozilla.com Wes Kocher (KWierso)], [mailto:cbook@mozilla.com Carsten Book (Tomcat)]
|group=dev-tree-management
|url=https://wiki.mozilla.org/Sheriffing
|components=Tree Management::Visibility Requests
}}

MOSS

2015-11-20T14:58:59Z

Bkerensa: /* Selection Committee */

==Program Overview==

Mozilla Open Source Support (MOSS) is a grant program specifically focused on supporting the [http://opensource.org/osd Open Source] and [http://www.gnu.org/philosophy/free-sw.en.html Free Software] movement, with an initial allocation of USD $1 million.

Mozilla is a part of the Open Source and Free Software movement. We were born out of this movement. We prosper because of the technology and activism which comes from this movement. And we know that Open Source and Free Software remains a key part of the Internet and the online life we seek to build. We have had an ad-hoc grants program for many years. MOSS is a systematic way to provide a new level of support to this community.

The Mozilla Open Source Support program is designed to recognize and celebrate communities who are leading the way with open source projects that contribute to our work and the health of the Web. It encompasses both: a) a “give back” element for Open Source and Free Software projects that Mozilla relies on; and b) a “give forward” element for supporting other projects where financial resources from Mozilla can make our entire community more successful. We will identify crisp names for these elements as we go forward.

=="Projects Mozilla Relies On"==

Mozilla relies on [[MOSS/Projects_in_use_by_Mozilla|a number of open source and free software projects]] (please help fill out that list). In some cases the software produced by these projects is incorporated into Mozilla products. In other cases we rely on as part of our infrastructure or to get our jobs done.

===Project Criteria===

Projects which Mozilla uses or relies on and who are in need of funds are welcome to apply for an award. Awards should be jointly submitted by the leader of a project and an established Mozillian who will champion the grant. The project/people need to meet the following criteria:

* Grant requests should be for the amount of financial support that helps accomplish a clear and current project goal. Projects that don’t have a need for funds at this time can be considered when such a need arises. A $10,000 grant request is just as valid as a $50,000 or $100,000 request.

* The money must be used to benefit the project, but it does not have to be used on things which themselves would directly benefit Mozilla.

* The project’s home can be anywhere in the world where we can make payment without undue burden. We have a reasonably strong preference for funding legal organizations rather than individuals representing projects, although exceptional circumstances could lead to some flexibility.

* The Mozillian champion may be (but does not need to be) a project contributor to the project they are championing.

* The Mozillian champion must vouch for the usefulness of the software, commit to monitoring the project, and report on the effectiveness of the grant after the money is spent (perhaps using a standardized form). They will also make themselves available to the application evaluation committee to help them assess the appropriateness of the grant to the needs of the project.

We expect the vast majority of MOSS grants to be singular rather than regular - that is, support for doing a particular defined thing, rather than ongoing support for a project in general. However a previous award proposal, successful or unsuccessful, does not disqualify a project from applying again.

===Selection Criteria===

These are a work in progress; further feedback is welcome on the MOSS mailing list until November 8th. All criteria are indicative rather than determinative - that is to say, they will make us more or less likely to make an award, but none will guarantee a particular outcome.

* How reliant is Mozilla on the project's technology?
* Do others also rely on it outside of Mozilla products?
* Is the technology unique? Are they doing something different?
* What role does the project play in the open source ecosystem?
* What sort of reputation does the project have in general, if any?
** This includes reputation in technical, inclusion and other areas
** Is the project known for something besides the code we are relying on?
* Will this grant make a significant impact on the project?
* Is the level of funding appropriate for the task to be accomplished?
* Does the person (or group) who will receive the money have a track record of delivering?
* What does the champion have to say? Is the case compelling?

===Selection Committee===

We have formed a selection committee of 7 participants, as follows:

* '''Current Committed Mozillians''' - they bring a good working knowledge of Mozilla's day-to-day activities and how various open source projects are used.
** [https://mozillians.org/en-US/u/bkerensa/ Benjamin Kerensa]
** [https://mozillians.org/en-US/u/laura/ Laura Thomson]
** [https://mozillians.org/en-US/u/dougt/ Doug Turner]

* '''Senior Mozilla Alumni''' - they are no longer actively involved with Mozilla on a day-to-day basis but have a deep understanding of our project and a different/outside perspective.
** [http://stormyscorner.com/ Stormy Peters]
** [http://shaver.off.net/diary/ Mike Shaver]

* '''Other Open Source Experts''' - they bring knowledge of the role of different projects within the open source ecosystem.
** [http://www.rcbowen.com/ Rich Bowen]
** (One invitation still outstanding)

==Other Tracks==

In the future, MOSS will have other tracks. We are developing one with a particular focus on providing security audit and remediation for key projects with a significant attack surface and exposure. These may have similar or different application criteria, or they may not have a public application process at all.

==How To Apply==

The application form is [https://docs.google.com/a/mozilla.com/forms/d/1Pa5IsuhT6vMUfg0HUXxr7SzrSwq5fpiZfZIJVPxN1Mc/viewform here].

==FAQs==

;What does it mean to “champion” a project for a MOSS Award?
: Being a champion means you believe in the project and its impact. You believe that funds from a MOSS Award would make a meaningful difference in the success and effectiveness of the project. And you believe the range of funds requested in the Award proposal is appropriate. In the case of the “give back” category of awards you should also also believe that project has meaningful impact on Mozilla’s work.

: A champion does a few different things:
* sponsors the project’s award proposal (it is akin to vouching for someone);
* serves as the liaison between that project and Mozilla with regard to the award;
* reviews the effectiveness of the award funds after an agreed upon period, to help Mozilla improve the effectiveness and impact of the MOSS program.

This review process might involve answering a set of standard assessment questions at the mid-point and at the end of the grant period, and giving your written opinion of the overall success of the award. The time commitment should not be massive, but it will require thoughtfulness and honesty.

;What if the project I care most about doesn’t have a legal organizational home? I see this is disfavored and exceptional circumstances are required. What might count as "exceptional"?
: You tell us. If a project doesn't have a legal organizational home, we will be handing a large sum of money to an individual with only limited accountability. This means a higher level of complexity and risk. So you need to describe why it's reasonable and important for us to accept that additional risk. We will listen because Mozilla is a pretty flexible organization, but we can’t promise the result will be as you hope.

;How can I, as a Mozillian, get started while the terms of the application and evaluation process are being finalized?
: Here are some things you can do immediately:
* Do some due diligence with other community members. Find out if others share your sense of a project’s impact.
* Identify a contact inside the project who is a good person to talk to about such things. Not every project needs funds all the time. Explore whether there is a current need within the project that could be met with a MOSS award. If there is such a need then turn to exploring the size of the amount. Think about the impact that could occur at several different ranges of money.
* If you find a project you care about has other types of needs, note that in the project list above. We aren't yet thinking about non-financial support, but we may do that in the future.
* If you are interested in participating in the finalization of the program criteria, join the discussion.

;Can I get help with thinking about or preparing a proposal? I’m not that practiced at figuring out ranges of funding, or I’d like help in thinking about the need.
: So far we have three identified mentors: [https://blog.mozilla.org/press/bios/david-bryant/ David Bryant], [https://mozillians.org/en-US/u/pfinette/ Pascal Finette] and [https://blog.mozilla.org/press/bios/jim-cook/ Jim Cook]. David is obviously clueful about software, and he’s also signed on to assist with the topics of project needs, possible solutions and appropriate amounts. For those of you who don’t know Pascal, he launched [http://webfwd.org WebFWD] when he was a Mozilla employee and now runs Singularity University’s [http://startup.singularityu.org/accelerator/ accelerator program]. Pascal has a long history and an abiding love of working with people to build things. He has great expertise in this type of task, matching by his abiding interest in contributing to Mozilla. Our CFO Jim Cook will provide assistance for those interested in the financial side of things. And Jim knows a lot about cost and value! We’ll look into adding to this list.

;Is there an amount of an award that is expected? Or a size that is too big or too small?
: In the next week we expect to identify a range within which we prefer the Awards proposals land, and to have some guidance what to do if you believe an Award really should be smaller or larger. At the moment, we are looking at a minimum of $10,000, and a maximum of $250,000.

;What’s the evaluation process?
: That’s being worked out. Input welcome.

;What’s happening by [[Coincidental_work_weeks/2015_Orlando|Orlando]]?
: Identification of the first set of projects we want to celebrate and fund. This way we can make the program tangible while we are together.

;How does the $1 million work? Does it all get allocated at Orlando? How does the $1 million figure interact with the “up to 10 projects” goal?
: The $1 million is the initial allocation for the MOSS program. We will evaluate the program as we go. It is our hope and expectation that the program provides value to the recipients and the Open Source ecosystem, and we expect to make additional allocations to the MOSS program in the future.

: We want to focus on making up to 10 good awards, to projects we think are great, where an award can make a real difference, and where we’ve had time to interact with the project and its leadership. More than 10 is difficult to impossible to do well before Orlando. Indeed, 10 may turn out to be more than we can manage.

: It is conceivable that the 10 awards could use the entire first $1 million allocation, but this is not a goal, and seems unlikely.

;How can I stay informed and involved with this work?
: Please join the MOSS [https://lists.mozilla.org/listinfo/moss public mailing list].

;This program seems unfinished right now. Why are you launching it in this state?
: The foundational elements are clear. We are going to invest in the open source and free software projects. We are going to start with a significant amount of money. We will start with open source and free software project that Mozilla is relying on. This is a crisp, clear criteria and a good way to start our larger program. We have an aggressive timeframe for a first set of grants to demonstrate we mean action.

: Once we got the foundations clear, we could have taken a couple of different approaches. One would have been to go off and create a fully polished program where we’ve already decided exactly how things will work. Another approach is to present the program while there is real room for your ideas, and for the cluefulness that is spread through Mozilla to make a program that represents all of us.

: I (Mitchell) have chosen the latter approach. The cynical of you may say “hah, time is short, and that favors announcing this before all the terms are finalized.” You are correct that time is short. However, the latter approach also reflects our view that many Mozilla activities are better when people of different perspectives and unexpected expertise and interest are involved. We hope you prove us right!

MOSS/Foundational Technology/Projects We Use

2015-10-23T20:11:01Z

Bkerensa:

This is an incomplete list of the free software and open source projects Mozilla relies upon. As a starting point, it lists each project along with a short statement of how we depend on it. Where practical it would also be helpful to identify a Mozillian most closely associated with our use of each project, as next steps will involve contacting each one to find out more about how we can best provide support.

This is a work in progress - please contribute to this list.

{| class="wikitable"
|-
! Project !! Description !! Contact within Mozilla
|-
| [https://angularjs.org/ angular.js] || Used by A-Team for web apps || Member of Jonathan Griffin's team
|-
| [https://httpd.apache.org Apache Server] || Used by A-Team for web apps || Member of Jonathan Griffin's team
|-
| [https://github.com/ansible/ansible Ansible] || Used by IT (netops) and A-Team to manage deployments || jbarnell , GPS?
|-
| [https://babeljs.io/ BabelJS] || JavaScript compiler, Used by Gaia, TaskCluster team || Selena Deckelmann
|-
| [http://buildbot.net/ BuildBot] || The base system currently in use for release automation ''(due to be replaced by Task Cluster)'' || Chris AtLee
|-
| [http://bugzilla.org/ Bugzilla] (upstream) || The base Bugzilla on that we customize for Mozilla's use || Glob
|-
| [http://www.llvm.org Clang/LLVM] || C/C++ compiler and infrastructure || Ehsan Akhgari
|-
| [https://codemirror.net/ CodeMirror] || Used in DevTools, [https://thimble.mozilla.org Thimble], and other online code tools || David Humphrey/Simon Wex
|-
| Debian || Used on many developer boxes || Unknown (maybe Sylvestre Ledru) or glandium
|-
| [https://discourse.org Discourse] || [https://discourse.mozilla-community.org Community], [https://discourse.webmaker.org/ Webmaker], [https://discourse.mozilla-advocacy.org/ Advocacy], et al || [[IT/Community/WG/Discourse|Community Ops]] (Yousef Alam or Tanner Filip)
|-
| [https://djangoproject.com DjangoProject] || Used by many Mozilla websites || Andy McKay and Jannis Leidel are (or have been) on the Foundations board
|-
| [https://github.com/docker/docker Docker] || Used by release engineering for Linux build and test containers and by ateam for managing test and production services. Used by many Mozilla websites as well. || Member of Selena Deckelmann's team
|-
| [https://github.com/ether/etherpad-lite Etherpad] || Used for meeting notes, etc || Unknown
|-
| [http://gcc.gnu.org GCC] || C/C++ compiler and infrastructure || Unknown
|-
| [https://git-scm.com/ Git] || Version control system - https://git.mozilla.org || Unknown
|-
| [http://canonware.com/jemalloc/ jemalloc] || Memory allocation library || We can ask glandium
|-
| libjpeg-turbo || JPEG decoding library || Jeff Muizelaar
|-
| libpng || PNG decoding library || Jeff Muizelaar
|-
| libvpx (Google) || Library for support of Google’s VP* family of codecs || Tim Terriberry
|-
| Linux || OS kernel used in Firefox OS || Unknown
|-
| [https://www.mediawiki.org/wiki/MediaWiki MediaWiki] || You are reading this on a wiki || Unknown
|-
| [https://www.mercurial-scm.org/ Mercurial] || Version control system and source code management || GPS
|-
| [http://www.mingw.org/wiki/msys msys] || Used to build Firefox on Windows || Unknown
|-
| [https://www.mysql.com/ MySQL] || DB used by A-Team || Member of Jonathan Griffin's team
|-
| [https://www.nagios.org/ Nagios] || IT management system. Used for notifications of system failures || IT or Amy Rich's team
|-
| nICEr || Library for traversing firewalls || Unknown
|-
| [https://nodejs.org Node.js] || JavaScript runtime for server side applications, command line utilities || Nick Desaulniers
|-
| nrappkit || Toolkit for building standalone applications || Unknown
|-
| OpenH264 (Cisco) || H.264 video library || Unknown
|-
| [http://openresty.org OpenResty] || a fast web app server by extending nginx, used by cloudops || Benson Wong (mostlygeek)
|-
| [http://openssl.org/ OpenSSL] || Cryptograpahy and TLS Toolkit || Nick Desaulniers
|-
| [https://github.com/mozilla/pdf.js PDF.js] || Used as the PDF Viewer in Firefox and Firefox OS || Brendan Dahl, Yury Delendik
|-
| [https://www.perl.org/ Perl] || Used by Bugzilla || Member of Jonathan Griffin's team
|-
| [http://www.postgresql.org/ PostgreSQL] || Relational database engine used in many projects || Selena Deckelmann?
|-
| [https://github.com/puppetlabs/puppet Puppet] || System administration tool || Member of Amy Rich's team
|-
| Python || Scripting language || [http://python.org/psf/ Python Software Foundation], Selena Deckelmann is a former board member
|-
| [https://www.rabbitmq.com/ RabbitMQ] || Distributed Queue, used by Socorro, Pulse (all our publicly available build/test/commit information flows through this) || Selena Deckelmann
|-
| [https://readthedocs.org/ Read the Docs] || Hosted automatically-built documentation, used by Cloud Services and a wide variety of mozilla Github projects || Ben Bangert
|-
| [https://www.reviewboard.org/ Review Board] || The base of MozReview, the new review tool being developed to replace Splinter || Steven MacLeod, Mike Conley
|-
| [http://www.seleniumhq.org/ Selenium] || Browser test driver || stephend/AutomatedTester or jrgm/vladikoff
|-
| [https://slimerjs.org/ SlimerJS] || Scriptable browser, based on Gecko, used for functional tests in some few Mozilla projects ( [[PluotSorbet]], some FxOS apps ? and others ?) || Unknown
|-
| [https://www.sqlite.org/ SQLite] || File-based database || khuey
|-
| [https://subversion.apache.org/ Subversion] || https://svn.mozilla.org ''(Planning to decommission in near future)'' || Unknown
|-
| [https://travis-ci.org/ Travis] || Continuous integration system used by several teams || Jonathan Griffin's team
|-
| [https://ubuntu.com/ Ubuntu] || Ubuntu Server powers many Mozilla Servers|| Unknown
|-
| [https://github.com/mitchellh/vagrant Vagrant]|| Build and distribute dev envs || Member of Jonathan Griffin's team
|-
| [http://www.webrtc.org WebRTC.org] || Components to support real-time communication in browsers and mobile applications || Randell Jesup
|-
| [http://www.wordpress.org WordPress] || Powers our blogs, blog.mozilla.org || Unknown
|-
| [http://mozdef.com mozdef] || Security event monitoring and incident response || Jeff Bryner
|-
| [https://www.djangoproject.com/ Django] || Backend web framework used on many of our websites || Django Software Foundation (jezdez is a board member)
|}

WeeklyUpdates/2015-08-10

2015-08-10T16:34:07Z

Bkerensa: /* Friends of Mozilla Friends of Mozilla */

{{WeeklyUpdateNav}}
* Every Monday @ 11:00am Pacific Time (19:00 UTC)
* http://air.mozilla.org/ to watch and listen
* join irc.mozilla.org #airmozilla for backchannel discussion
* Presenters only: Vidyo room "Brownbags". Do '''not''' use this room if you're not planning to speak.
{{conf|8600}}

__TOC__

= All-hands Status Meeting Agenda =

Items in this section will be shared during the live all-hand status meeting.

== Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==
* Huge thanks to [http://subfictional.com/ Christie Koehler] for all her efforts trying to making Mozilla a better community and organization over her four years at Mozilla.
* Congratulation to [https://reps.mozilla.org/u/nefzaoui/ Ahmed Nefzaoui] and [https://reps.mozilla.org/u/yofiesetiawan/ Yofie Setiawan] for begin the [https://discourse.mozilla-community.org/t/rep-of-the-month-june-2015/2753 Reps of the month] for June! ( a bit delayed, but never to late) Check out their contributions on the portal and read [http://yopdesign.com/blog/mozilla/433-mozilla-reps-of-the-month-july-2015.html what this meant for them]!
* Congrats to [https://reps.mozilla.org/u/mohamed7afezz/ Mohamed Hafez] for being [https://discourse.mozilla-community.org/t/rep-of-the-month-july-2015/2978/15 Rep of the month for July!] See his latest work on the portal!

== Upcoming Events ==

=== This Week ===

=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===
* [https://quality.mozilla.org/event/bug-triage-day-71/ Weekly Bug Triage Day]

=== Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===

* [https://quality.mozilla.org/event/firefox-for-android-testday-tuesday-11th-august-2015/ Firefox For Android testday] - 1am to 1600 Pt in #QA

=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===
* [https://quality.mozilla.org/event/bug-verification-day-77/ Weekly Bug Verification Day]

* '''[http://indiewebcamp.com/events/2015-08-12-homebrew-website-club Homebrew Website Club Meetup]''' (every other Wednesday)
** Be independent with your web browser and your web site.
** '''San Francisco''' (@[[MozSF]]), '''Brighton England''' ([https://twitter.com/@68middlest @68middlest]) 
** 17:30-18:30 Writing Hour
** 18:30-19:30 IndieWeb meetup & hack night <blockquote>Create or update your personal web site! Share what you've gotten working, ask for help where you're stuck.Join a community with like-minded interests. Bring friends that want a personal site!</blockquote> Any questions? See '''[http://indiewebcamp.com/events/2015-08-12-homebrew-website-club the wiki page for details]''' or join IRC: http://indiewebcamp.com/irc/today?beta#bottom

=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===
'''Monthly Brantina* on [https://en.wikipedia.org/wiki/Growth_hacking Growth Hacking] @ 9:00am PT / 12:00pm ET / 4:00pm UTC'''
* Location: San Francisco + [https://air.mozilla.org/august-brantina-with-hiten-shah-founder-kissmetrics-crazy-egg/ Air Mozilla]
* Topic: [https://www.linkedin.com/in/hnshah Hiten Shah] will share his ideas and experience with growth hacking, a scrappy marketing technique developed by technology startups. Larger companies that embrace this approach (examples include Facebook, Twitter, LinkedIn, Airbnb and Dropbox) use creativity, analytical thinking, and social metrics to gain product exposure and grow their market share quickly.
* Speaker: [https://www.linkedin.com/in/hnshah Hiten Shah] is cofounder and president of analytics companies KISSmetrics and Crazy Egg; he also advises startups.
* Host: [https://mozillians.org/en-US/u/kaykas/ Jascha Kaykas-Wolff]
* Questions: Submit your questions for Hiten in advance [https://moderator.mozilla.org/e/august-2015-brantina-hiten-shah-on-build-measure-learn here], or during the event on IRC #AirMozilla.

''* Breakfast + Cantina''

*[https://air.mozilla.org/german-speaking-community-bi-weekly-meeting-20150604/ German-speaking community bi-weekly meeting], 9pm CEST (7pm UTC, 12pm PT) AirMozilla, IRC: #deMeeting
**More info: [[De/Meetings]].

=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===

=== Saturday, {{#time:d F|{{SUBPAGENAME}} +5 days}} ===

=== Sunday, {{#time:d F|{{SUBPAGENAME}} +6 days}} ===

=== Next Week ===

== Project Status Updates (voice updates) ==

=== Firefox and Cloud Services ===
''Speaker Location:''

=== Firefox OS ===
''Speaker Location:''

=== CTO Update ===
''Speaker Location:''

=== Content Services ===
''Speaker Location:''

=== Webmaker ===
''Speaker Location:''

=== Mozilla Communities ===
''Speaker Location:''

== Speakers ==

The limit is '''3 minutes per topic'''. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week.

{| class="fullwidth-table wikitable"
|-
! [https://mozillians.org/u/USERNAME Presenter]
! Title
! Topic
! Location
! Share?
! Media
! More Details
|-
| Who Are You?
| What Do You Do?
| What are you going to talk about?
| Where are you presenting from? (Moz Space, your house, space)
| Will you be sharing your screen? (yes/no, other info)
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
| Jill Alvarez
| University Program Manager
| Interns 2016
|
|
|
|
|
|-
| Erik Rose
| DXR Project Lead
| DXR 2.0
| my house
| yes
|
| https://dxr.readthedocs.org/
[https://air.mozilla.org/dxr-2-0-part-1-dog-pony-show/ 2.0 preview talk from Whistler]
|}

= Welcome! =

Let's say hello to some new Mozillians! If you are not able to join the meeting live, you can add a link to a short video introducing yourself.

== Introducing New Volunteers ==
{| class="fullwidth-table wikitable"
|-
! New Volunteer
! Introduced by
! Speaker location
! New Volunteer location
! Will be working on
|-
| ''Who is the new volunteer?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be contributing from?''
| ''What will the new person be working on?''
|-

|-
|}

== Introducing New Hires ==
{| class="fullwidth-table wikitable"
|-
! New Hire
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Who is the new hire?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-
| Jessica Osorio
| Chelsea Novak
| Remote
| San Francisco
| [https://friends.mozilla.org Firefox Friends]
|-
| Rochelle Kumar
| Michelle Marovich
| Mountain View
| San Francisco
| Senior Recruiting Coordinator
|-
| Kelly Fraser
| Michelle Marovich
| Mountain View
| Mountain View
| Senior Recruiting Coordinator
|-
| Brian Smith
| Liz Compton
| Mountain View
| Mountain View
| Corporate Counsel
|-

|-
|}

== Introducing New Interns ==
{| class="fullwidth-table wikitable"
|-
! New Intern
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Who is the new intern?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-

|-
|}

= <meta> =

Notes and non-voice status updates that aren't part of the live meeting go here.

== Status Updates By Team (*non-voice* updates) ==

=== Firefox ===

=== Platform ===

=== Cloud Services ===

=== Messaging ===

=== Mobile ===

=== IT ===

=== Release Engineering ===

=== QA ===

==== Test Execution ====

==== Web QA ====

==== QA Community ====

=== Automation & Tools ===

=== Security ===

=== Engagement ===

* [https://docs.google.com/a/mozilla.com/spreadsheets/d/1X5kUBkEAicEe2unDaaLGTYzAJbphWFoaJYBTasHrcHQ/edit#gid=1764494528 Engagement's Active Project Dashboard]

==== PR ====

==== Events ====

==== Social Support ====

[[Category:Weekly Updates]]
[[Category:Meeting Notes]]

WeeklyUpdates/2015-08-10

2015-08-10T16:33:39Z

Bkerensa: /* Friends of Mozilla Friends of Mozilla */

{{WeeklyUpdateNav}}
* Every Monday @ 11:00am Pacific Time (19:00 UTC)
* http://air.mozilla.org/ to watch and listen
* join irc.mozilla.org #airmozilla for backchannel discussion
* Presenters only: Vidyo room "Brownbags". Do '''not''' use this room if you're not planning to speak.
{{conf|8600}}

__TOC__

= All-hands Status Meeting Agenda =

Items in this section will be shared during the live all-hand status meeting.

== Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==
* Huge thanks to [http://subfictional.com/ Christie Koehler] for all [http://subfictional.com/2015/08/09/i-have-joined-tableflip-club/ her efforts trying to making Mozilla a better community and organization] over her four years at Mozilla.
* Congratulation to [https://reps.mozilla.org/u/nefzaoui/ Ahmed Nefzaoui] and [https://reps.mozilla.org/u/yofiesetiawan/ Yofie Setiawan] for begin the [https://discourse.mozilla-community.org/t/rep-of-the-month-june-2015/2753 Reps of the month] for June! ( a bit delayed, but never to late) Check out their contributions on the portal and read [http://yopdesign.com/blog/mozilla/433-mozilla-reps-of-the-month-july-2015.html what this meant for them]!
* Congrats to [https://reps.mozilla.org/u/mohamed7afezz/ Mohamed Hafez] for being [https://discourse.mozilla-community.org/t/rep-of-the-month-july-2015/2978/15 Rep of the month for July!] See his latest work on the portal!

== Upcoming Events ==

=== This Week ===

=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===
* [https://quality.mozilla.org/event/bug-triage-day-71/ Weekly Bug Triage Day]

=== Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===

* [https://quality.mozilla.org/event/firefox-for-android-testday-tuesday-11th-august-2015/ Firefox For Android testday] - 1am to 1600 Pt in #QA

=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===
* [https://quality.mozilla.org/event/bug-verification-day-77/ Weekly Bug Verification Day]

* '''[http://indiewebcamp.com/events/2015-08-12-homebrew-website-club Homebrew Website Club Meetup]''' (every other Wednesday)
** Be independent with your web browser and your web site.
** '''San Francisco''' (@[[MozSF]]), '''Brighton England''' ([https://twitter.com/@68middlest @68middlest]) 
** 17:30-18:30 Writing Hour
** 18:30-19:30 IndieWeb meetup & hack night <blockquote>Create or update your personal web site! Share what you've gotten working, ask for help where you're stuck.Join a community with like-minded interests. Bring friends that want a personal site!</blockquote> Any questions? See '''[http://indiewebcamp.com/events/2015-08-12-homebrew-website-club the wiki page for details]''' or join IRC: http://indiewebcamp.com/irc/today?beta#bottom

=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===
'''Monthly Brantina* on [https://en.wikipedia.org/wiki/Growth_hacking Growth Hacking] @ 9:00am PT / 12:00pm ET / 4:00pm UTC'''
* Location: San Francisco + [https://air.mozilla.org/august-brantina-with-hiten-shah-founder-kissmetrics-crazy-egg/ Air Mozilla]
* Topic: [https://www.linkedin.com/in/hnshah Hiten Shah] will share his ideas and experience with growth hacking, a scrappy marketing technique developed by technology startups. Larger companies that embrace this approach (examples include Facebook, Twitter, LinkedIn, Airbnb and Dropbox) use creativity, analytical thinking, and social metrics to gain product exposure and grow their market share quickly.
* Speaker: [https://www.linkedin.com/in/hnshah Hiten Shah] is cofounder and president of analytics companies KISSmetrics and Crazy Egg; he also advises startups.
* Host: [https://mozillians.org/en-US/u/kaykas/ Jascha Kaykas-Wolff]
* Questions: Submit your questions for Hiten in advance [https://moderator.mozilla.org/e/august-2015-brantina-hiten-shah-on-build-measure-learn here], or during the event on IRC #AirMozilla.

''* Breakfast + Cantina''

*[https://air.mozilla.org/german-speaking-community-bi-weekly-meeting-20150604/ German-speaking community bi-weekly meeting], 9pm CEST (7pm UTC, 12pm PT) AirMozilla, IRC: #deMeeting
**More info: [[De/Meetings]].

=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===

=== Saturday, {{#time:d F|{{SUBPAGENAME}} +5 days}} ===

=== Sunday, {{#time:d F|{{SUBPAGENAME}} +6 days}} ===

=== Next Week ===

== Project Status Updates (voice updates) ==

=== Firefox and Cloud Services ===
''Speaker Location:''

=== Firefox OS ===
''Speaker Location:''

=== CTO Update ===
''Speaker Location:''

=== Content Services ===
''Speaker Location:''

=== Webmaker ===
''Speaker Location:''

=== Mozilla Communities ===
''Speaker Location:''

== Speakers ==

The limit is '''3 minutes per topic'''. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week.

{| class="fullwidth-table wikitable"
|-
! [https://mozillians.org/u/USERNAME Presenter]
! Title
! Topic
! Location
! Share?
! Media
! More Details
|-
| Who Are You?
| What Do You Do?
| What are you going to talk about?
| Where are you presenting from? (Moz Space, your house, space)
| Will you be sharing your screen? (yes/no, other info)
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
| Jill Alvarez
| University Program Manager
| Interns 2016
|
|
|
|
|
|-
| Erik Rose
| DXR Project Lead
| DXR 2.0
| my house
| yes
|
| https://dxr.readthedocs.org/
[https://air.mozilla.org/dxr-2-0-part-1-dog-pony-show/ 2.0 preview talk from Whistler]
|}

= Welcome! =

Let's say hello to some new Mozillians! If you are not able to join the meeting live, you can add a link to a short video introducing yourself.

== Introducing New Volunteers ==
{| class="fullwidth-table wikitable"
|-
! New Volunteer
! Introduced by
! Speaker location
! New Volunteer location
! Will be working on
|-
| ''Who is the new volunteer?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be contributing from?''
| ''What will the new person be working on?''
|-

|-
|}

== Introducing New Hires ==
{| class="fullwidth-table wikitable"
|-
! New Hire
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Who is the new hire?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-
| Jessica Osorio
| Chelsea Novak
| Remote
| San Francisco
| [https://friends.mozilla.org Firefox Friends]
|-
| Rochelle Kumar
| Michelle Marovich
| Mountain View
| San Francisco
| Senior Recruiting Coordinator
|-
| Kelly Fraser
| Michelle Marovich
| Mountain View
| Mountain View
| Senior Recruiting Coordinator
|-
| Brian Smith
| Liz Compton
| Mountain View
| Mountain View
| Corporate Counsel
|-

|-
|}

== Introducing New Interns ==
{| class="fullwidth-table wikitable"
|-
! New Intern
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Who is the new intern?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-

|-
|}

= <meta> =

Notes and non-voice status updates that aren't part of the live meeting go here.

== Status Updates By Team (*non-voice* updates) ==

=== Firefox ===

=== Platform ===

=== Cloud Services ===

=== Messaging ===

=== Mobile ===

=== IT ===

=== Release Engineering ===

=== QA ===

==== Test Execution ====

==== Web QA ====

==== QA Community ====

=== Automation & Tools ===

=== Security ===

=== Engagement ===

* [https://docs.google.com/a/mozilla.com/spreadsheets/d/1X5kUBkEAicEe2unDaaLGTYzAJbphWFoaJYBTasHrcHQ/edit#gid=1764494528 Engagement's Active Project Dashboard]

==== PR ====

==== Events ====

==== Social Support ====

[[Category:Weekly Updates]]
[[Category:Meeting Notes]]

WeeklyUpdates/2015-08-10

2015-08-10T07:27:39Z

Bkerensa: /* Friends of Mozilla Friends of Mozilla */

{{WeeklyUpdateNav}}
* Every Monday @ 11:00am Pacific Time (19:00 UTC)
* http://air.mozilla.org/ to watch and listen
* join irc.mozilla.org #airmozilla for backchannel discussion
* Presenters only: Vidyo room "Brownbags". Do '''not''' use this room if you're not planning to speak.
{{conf|8600}}

__TOC__

= All-hands Status Meeting Agenda =

Items in this section will be shared during the live all-hand status meeting.

== Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==
Huge thanks to [http://subfictional.com/ Christie Koehler] for all her efforts trying to making Mozilla a better community
and organization over her four years at Mozilla.

== Upcoming Events ==

=== This Week ===

=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===
* [https://quality.mozilla.org/event/bug-triage-day-71/ Weekly Bug Triage Day]

=== Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===

* [https://quality.mozilla.org/event/firefox-for-android-testday-tuesday-11th-august-2015/ Firefox For Android testday] - 1am to 1600 Pt in #QA

=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===
* [https://quality.mozilla.org/event/bug-verification-day-77/ Weekly Bug Verification Day]

* '''[http://indiewebcamp.com/events/2015-08-12-homebrew-website-club Homebrew Website Club Meetup]''' (every other Wednesday)
** Be independent with your web browser and your web site.
** '''San Francisco''' (@[[MozSF]]), '''Brighton England''' ([https://twitter.com/@68middlest @68middlest]) 
** 17:30-18:30 Writing Hour
** 18:30-19:30 IndieWeb meetup & hack night <blockquote>Create or update your personal web site! Share what you've gotten working, ask for help where you're stuck.Join a community with like-minded interests. Bring friends that want a personal site!</blockquote> Any questions? See '''[http://indiewebcamp.com/events/2015-08-12-homebrew-website-club the wiki page for details]''' or join IRC: http://indiewebcamp.com/irc/today?beta#bottom

=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===
'''Monthly Brantina* @ 9:00am PT / 12:00pm ET / 4:00pm UTC'''
* Location: San Francisco + [https://air.mozilla.org/august-brantina-with-hiten-shah-founder-kissmetrics-crazy-egg/ Air Mozilla]
* Topic: [https://www.linkedin.com/in/hnshah Hiten Shah] will share his ideas and experience with growth hacking, a scrappy marketing technique developed by technology startups. Larger companies that embrace this approach (examples include Facebook, Twitter, LinkedIn, Airbnb and Dropbox) use creativity, analytical thinking, and social metrics to gain product exposure and grow their market share quickly.
* Speaker: [https://www.linkedin.com/in/hnshah Hiten Shah] is cofounder and president of analytics companies KISSmetrics and Crazy Egg; he also advises startups.
* Host: [https://mozillians.org/en-US/u/kaykas/ Jascha Kaykas-Wolff]
* Questions: Submit your questions for Hiten in advance [https://moderator.mozilla.org/e/august-2015-brantina-hiten-shah-on-build-measure-learn here], or during the event on IRC #AirMozilla.

''* Breakfast + Cantina''

=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===

=== Saturday, {{#time:d F|{{SUBPAGENAME}} +5 days}} ===

=== Sunday, {{#time:d F|{{SUBPAGENAME}} +6 days}} ===

=== Next Week ===

== Project Status Updates (voice updates) ==

=== Firefox and Cloud Services ===
''Speaker Location:''

=== Firefox OS ===
''Speaker Location:''

=== CTO Update ===
''Speaker Location:''

=== Content Services ===
''Speaker Location:''

=== Webmaker ===
''Speaker Location:''

=== Mozilla Communities ===
''Speaker Location:''

== Speakers ==

The limit is '''3 minutes per topic'''. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week.

{| class="fullwidth-table wikitable"
|-
! [https://mozillians.org/u/USERNAME Presenter]
! Title
! Topic
! Location
! Share?
! Media
! More Details
|-
| Who Are You?
| What Do You Do?
| What are you going to talk about?
| Where are you presenting from? (Moz Space, your house, space)
| Will you be sharing your screen? (yes/no, other info)
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
| Jill Alvarez
| University Program Manager
| Interns 2016
|
|
|
|
|}

= Welcome! =

Let's say hello to some new Mozillians! If you are not able to join the meeting live, you can add a link to a short video introducing yourself.

== Introducing New Volunteers ==
{| class="fullwidth-table wikitable"
|-
! New Volunteer
! Introduced by
! Speaker location
! New Volunteer location
! Will be working on
|-
| ''Who is the new volunteer?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be contributing from?''
| ''What will the new person be working on?''
|-

|-
|}

== Introducing New Hires ==
{| class="fullwidth-table wikitable"
|-
! New Hire
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Who is the new hire?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-

|-
|}

== Introducing New Interns ==
{| class="fullwidth-table wikitable"
|-
! New Intern
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Who is the new intern?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-

|-
|}

= <meta> =

Notes and non-voice status updates that aren't part of the live meeting go here.

== Status Updates By Team (*non-voice* updates) ==

=== Firefox ===

=== Platform ===

=== Cloud Services ===

=== Messaging ===

=== Mobile ===

=== IT ===

=== Release Engineering ===

=== QA ===

==== Test Execution ====

==== Web QA ====

==== QA Community ====

=== Automation & Tools ===

=== Security ===

=== Engagement ===

* [https://docs.google.com/a/mozilla.com/spreadsheets/d/1X5kUBkEAicEe2unDaaLGTYzAJbphWFoaJYBTasHrcHQ/edit#gid=1764494528 Engagement's Active Project Dashboard]

==== PR ====

==== Events ====

==== Social Support ====

[[Category:Weekly Updates]]
[[Category:Meeting Notes]]

Release Management/Team members

2015-05-19T02:40:59Z

Bkerensa: /* Release Management Alumni */

= Current Team =
* Manager: [https://mozillians.org/en-US/u/lmandel/ Lawrence Mandel (:lmandel)]
* Desktop & Mobile RM: [https://mozillians.org/en-US/u/sylvestre/ Sylvestre Ledru (:sylvestre)]
* Desktop & Mobile RM: [https://mozillians.org/en-US/u/lizhenry/ Liz Henry (:lizzard)]

= Release Management Alumni =
[[File:Relman-team.JPG|frame|300px|Release Management Team - Portland Work Week, June 2014]]

* Staff Release Manager: [https://mozillians.org/en-US/u/lsblakk/ Lukas Blakk (:lsblakk)]
* FirefoxOS/B2G Release Manager: [https://mozillians.org/en-US/u/Bhavana/ Bhavana Bajaj (:bajaj)]
* Early Feedback Community RM: [https://mozillians.org/en-US/u/bkerensa/ Benjamin Kerensa (:bkerensa) ]

[[category:Release_Management]]

Release Management/Team members

2015-05-19T02:40:31Z

Bkerensa: /* Current Team */

WeeklyUpdates/2015-04-27

2015-04-27T05:19:17Z

Bkerensa: /* Friends of Mozilla Friends of Mozilla */

{{WeeklyUpdateNav}}
{{conf|8600}}

__TOC__

= All-hands Status Meeting Agenda =

Items in this section will be shared during the live all-hand status meeting.

== Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==

[https://mozillians.org/u/AprilMorone/ April Morone] for adding her app to the marketplace store

[https://mozillians.org/u/Mte90/ Daniele Scasciafratte] for stepping up and helping on the Contributor Social Media team - hes stepped up as the newest admin for the Mozilla Contributors group

Western Oregon University students for diving in to the project and working on bugs across the project during the last term.

== Upcoming Events ==

=== This Week ===

=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===

=== Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===

=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===

[https://air.mozilla.org/sumo-mobile-april-2015/ SuMo Mobile and b2g meeting] 9am pt in #sumo or the SuMo vidyo room

=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===

=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===

=== Saturday, {{#time:d F|{{SUBPAGENAME}} +5 days}} ===

=== Sunday, {{#time:d F|{{SUBPAGENAME}} +6 days}} ===

=== Next Week ===

There will be a contributors meeting on Tuesday
== Project Status Updates (voice updates) ==

=== Firefox and Cloud Services ===
''Speaker Location:''

=== Firefox OS ===
''Speaker Location:''

=== CTO Update ===
''Speaker Location:''

=== Content Services ===
''Speaker Location:''

=== Webmaker ===
''Speaker Location:''

=== Mozilla Communities ===
''Speaker Location:''

== Speakers ==

The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week.

{| class="fullwidth-table wikitable"
|-
! [https://mozillians.org/u/USERNAME Presenter]
! Title
! Topic
! Location
! Share?
! Media
! More Details
|-
| Who Are You?
| What Do You Do?
| What are you going to talk about?
| Where are you presenting from? (Moz Space, your house, space)
| Will you be sharing your screen? (yes/no, other info)
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
|}

= Roundtable =

Do you have a question about a Mozilla Project or initiative? Let us know by Friday- we'll do our best to get you an answer.

Please note that we may not always be able to get to every item on this list, but we will try!

{| class="fullwidth-table wikitable"
|-
! Who are you?
! Area of question
! Question
|-
| ''What's your name? What do you work on?''
| ''Is your question about policy, a product, a Foundation initiative, etc.''
| ''What would you like to know?''

|-
| ''David Weir (contributor)''
| ''B2G devices.''
| ''As being a long time contributor for Mozilla is their any flame devices going I can test and let users in the UK know how great b2g is?''

|-
|}

= Welcome! =

Let's say hello to some new Mozillians! If you are not able to join the meeting live, you can add a link to a short video introducing yourself.

== Introducing New Volunteers ==
{| class="fullwidth-table wikitable"
|-
! New Volunteer
! Introduced by
! Speaker location
! New Volunteer location
! Will be working on
|-
| ''Who is the new volunteer?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be contributing from?''
| ''What will the new person be working on?''
|-

|-
|}

== Introducing New Hires ==
{| class="fullwidth-table wikitable"
|-
! New Hire
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Who is the new hire?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-

|-
|}

== Introducing New Interns ==
{| class="fullwidth-table wikitable"
|-
! New Intern
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Who is the new intern?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-

|-
|}

= <meta> =

Notes and non-voice status updates that aren't part of the live meeting go here.

== Status Updates By Team (*non-voice* updates) ==

=== Firefox ===

=== Platform ===

=== Cloud Services ===

=== Messaging ===

=== Mobile ===

=== IT ===

=== Release Engineering ===

=== QA ===

==== Test Execution ====

==== Web QA ====

==== QA Community ====

=== Automation & Tools ===

==== bugzilla.mozilla.org ====
Notable changes to [https://bugzilla.mozilla.org/ bugzilla.mozilla.org] during the last week:
* {{bug|579089}} The default Hardware and Operating-System fields now default to "Unspecified/Unspecified" instead of the reporter's platform
** This can be overwritten per-product, [https://bugzilla.mozilla.org/enter_bug.cgi?product=bugzilla.mozilla.org&component=Administration file a bug] if you own a product and want this changed
[[BMO/Recent_Changes|All changes]].

=== Security ===

=== Engagement ===

* [https://docs.google.com/a/mozilla.com/spreadsheets/d/1X5kUBkEAicEe2unDaaLGTYzAJbphWFoaJYBTasHrcHQ/edit#gid=1764494528 Engagement's Active Project Dashboard]

==== PR ====

==== Events ====

==== Social Support ====

[[Category:Weekly Updates]]
[[Category:Meeting Notes]]

Template:ESR CURRENT DOT

2015-04-01T15:59:15Z

Bkerensa:

.6.0

Release Management/Onboarding

2015-03-31T17:11:20Z

Bkerensa: /* E-Mail */

Welcome to Release Management.

Here's a list of accounts to set up, tools to check out, and any other details we can think of to help you start getting yourself set up.

=Account Permissions=
You'll want to make sure you have the necessary permissions to do the following and some will take longer than others to achieve so start early:
* Bugs
** Request for your bugzilla account to be added to mozilla-next-drivers and mozilla-stable-branch-drivers groups in order to set tracking flags -- file a bug (eg: {{bug|962151}}), {{bug|1135168}}.
** [http://www.mozilla.org/en-US/about/governance/policies/security-group/bugs/#expanding Security permission] comes later.
* Repos
** svn commit access to http://viewvc.svn.mozilla.org/vc/projects/ for modifying product-details-- file a bug (eg: {{bug|962171}}, {{bug|1137251}}, {{bug|1135512}}) You will need specific allows for /libs/product-details,
/projects/mozilla-europe.org and /projects/mozillaonline.com. And, you will need to be in the svn_mozilla LDAP group.

If this is going to be a regular set of requests it would probably be better to
create a group for them.
** hg commit access (scm_level3) -- read http://www.mozilla.org/hacking/committer/, fill out a committer agreement, file a bug (eg: {{bug|738713}} except you'll request commit access, not elevation of current permissions) You will need two [https://wiki.mozilla.org/Modules/All#Core owners or peers for a core hg module] to vouch for you as described in [https://www.mozilla.org/en-US/about/governance/policies/commit/access-policy/ Commit Access Policy].

* Communications
** admin permissions for https://relman.etherpad.mozilla.org
* Builds
** Request Mozilla VPN access (required to access ship-it)
** Ask to be added to the groups ''shipit'' and ''vpn_shipit'' to get access to the build tool & l10n, by filing a bug in [https://bugzilla.mozilla.org/enter_bug.cgi?product=Infrastructure%20%26%20Operations&component=Infrastructure%3A%20LDAP Infrastructure & Operations::Infrastructure:LDAP]. Example: {{Bug|1135198}}
** Ask to be added to the LDAP group called ''verbatim'' by filing a bug in [https://bugzilla.mozilla.org/enter_bug.cgi?product=Infrastructure%20%26%20Operations&component=Infrastructure%3A%20LDAP Infrastructure & Operations::Infrastructure:LDAP]. This will give you permission to access to https://l10n.mozilla.org/ (Note: Is this true? Axel says we should not need to be in the verbatim group.)
* Release Notes
** Request admin access to https://nucleus.mozilla.org by filing a bug in [https://bugzilla.mozilla.org/enter_bug.cgi?product=Websites&component=Nucleus Websites::Nucleus]. Example: {{Bug|1135186}}

=Communication Channels=
==Release Calendar==
* https://www.google.com/calendar/embed?src=bW96aWxsYS5jb21fZGJxODRhbnI5aTh0Y25taGFiYXRzdHY1Y29AZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ

==E-Mail==
Note that some of these mailing lists need approval from an administrator.

*release-mgmt@mozilla.com - contact IT to be added (servicedesk@mozilla.com or on ServiceNow)
*release-drivers - visit https://mail.mozilla.org/listinfo/release-drivers to add yourself to release-drivers@ once your email is working
*security-group - visit https://mail.mozilla.org/listinfo/security-group to add yourself to security-group@ once your email is working
*Send a test message to both addresses individually to verify that your address has been added/subscribed.

You'll need to manually subscribe to:
*release-automation-notifications - visit https://groups.google.com/a/mozilla.com/group/release-automation-notifications/ (Contributors need invite)
*mozilla.dev.planning - visit https://lists.mozilla.org/listinfo/dev-planning
*mozilla.dev.tree-management - visit https://lists.mozilla.org/listinfo/dev-tree-management
*Enterprise - visit https://mail.mozilla.org/listinfo/enterprise
*Stability - vist https://mail.mozilla.org/listinfo/stability

These are available as [news://news.mozilla.org newsgroups], google groups, and [https://lists.mozilla.org/listinfo Mailman lists]

==Websites==

* [https://metrics.mozilla.com/pentaho Metric] (TODO: this url is out of date)
* [http://crash-stats.mozilla.com/ Crash reports]

== IRC ==

*https://wiki.mozilla.org/IRC irc://irc.mozilla.org
*irc.mozilla.org:6697
** #airmozilla - back channel for public broadcasts
** #developers - monitor check-ins and speak with devs
** #fx-team - good place to speak with desktop team
** #mobile - good place to speak with mobile devs
** #moco [access_key is here [https://intranet.mozilla.org/StaffMeeting]]
** #planning - back channel for product coordination meeting, good place to speak with broader product team
** #pm - Sheila's org
** #release-drivers - release related discussions
** #releng - releng team channel
** #relman - our team channel
** #security (ask for channel key) - the security team's channel
** #qa - QE team channel
** #www - for speaking with the mozilla.org team in case a push breaks or otherwise doesn't work
* http://chatzilla.hacksrus.com/faq/#connect

Many folks run a BNC (an IRC bouncer) (e.g. znc) and/or <tt>irssi</tt> under screen to get continuous view of traffic. Ask around.

See [[#pastebin|below]] for a local pastebin install, so you don't paste huge amounts in channel.

==EtherPad==

EtherPad is a great tool for dynamic collaboration during meetings, brainstorming, or other times when you need to collaborate:
* https://etherpad.mozilla.org/ for general use
* https://relman.etherpad.mozilla.org for team-specific information
* https://etherpad.mozilla.org/firefox38-worry-list Worry list specific to each release (change the version in the url as needed)

==Pastebin==

There's a local pastebin instance at http://pastebin.mozilla.org/, so you don't need to paste multi-lines into a channel. Use this handy [http://hg.mozilla.org/build/braindump/file/tip/utils/pastebin helper script] to pipe to pastebin from terminal.

it creates a new page from stdin, and outputs the url to stdout
an argument will be interpretted as the syntax highlighting format to use
sample usage: hg diff | pastebin python | pbcopy (last part mac specific)
set & export PASTEBIN_NAME if you don't want to post as anonymous.

==Planet==
Add a bug similar to {{bug|605709}} to get your blog syndicated on http://planet.mozilla.org. You can choose to send every post, or create a feed for a custom tag (eg: 'mozilla'). Having your blog syndicated to planet is a great channel for announcing new features (along with tweeting and posting to newsgroups).

=Software=

==Firefox==

# Please download & install Firefox [http://www.mozilla.org/fr/firefox/channel/#aurora aurora], [http://www.mozilla.org/fr/firefox/channel/#beta beta] and [http://www.mozilla.org/fr/firefox/channel/#firefox release]
# [https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles#w_creating-a-profile Create new profiles] for each version + your own profile. Read [https://developer.mozilla.org/en-US/docs/Mozilla/Multiple_Firefox_Profiles Multiple Firefox Profiles] for more help with the profile manager.

==VPN==

* Configure your system to access to the Mozilla VPN in order to get access to internal tools.
* Then, report a bug in ''Infrastructure & Operations: Mozilla VPN: ACL requests'' to get the ACL to ship-it and bedrock.productdetail. Example: {{bug|986037}} and {{bug|1001632}}
* Request permissions on bedrock.productdetail (it is not connected to the LDAP). ping TODO
* Note that using the Mozilla DNS servers is necessary to resolve the necessary URLs

=Handy Links=
==How To and Oft-Used==
* [[Release_Management]]
* [[Firefox/Channels/Meetings]]
* [https://www.mozilla.org/en-US/firefox/organizations/faq/ ESR FAQ]
* [[Enterprise/Firefox/ExtendedSupport:Proposal]]
* [[Release_Management/ESR_Landing_Process]]

==Bugzilla ==
* Install Akeybl's [http://alex.keybl.com/?p=23 bugzilla service] and HTML page title copy [https://builder.addons.mozilla.org/addon/1018034/ addon]
* Configure the [https://bugzilla.mozilla.org/userprefs.cgi?tab=securemail securemail] section if you want to see the content of security bugs in your email client. GPG key or [http://kb.mozillazine.org/Getting_an_SMIME_certificate SMIME certificate] are accepted.

=== Reports ===
* [https://bugzilla.mozilla.org/page.cgi?id=release_tracking_report.html release tracking report]
=== Queries ===
In your bugzilla preferences, under Saved Searches, you can add some of the following to your footer for quick access:
* [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=approval-aurora%3F&sharer_id=272375 approval-aurora?]
* [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=approval-beta%3F&sharer_id=272375 approval-beta?]
* [https://bugzilla.mozilla.org/buglist.cgi?o1=equals&v1=%3F&known_name=tracking-ff32%3F&f1=cf_tracking_firefox37&query_based_on=tracking-ff32%3F&query_format=advanced&list_id=12037223 tracking_firefox37?] (adjust for current beta version as needed)
* [https://bugzilla.mozilla.org/buglist.cgi?v4=---&f1=cf_tracking_firefox37&o3=equals&v3=affected&j2=OR&o1=equals&f4=cf_status_firefox37&query_format=advanced&f3=cf_status_firefox37&o4=equals&f2=OP&v1=%2B&list_id=12013780 Firefox 37 tracked bugs] (Make sure to query for the resolved bugs as well as open ones)

=Tools=
==Repos to check out==
* [https://github.com/lsblakk/relnotes Release Notes generation] (TODO: out of date: now done in nucleus?)
* [https://github.com/mozilla/bztools Bugzilla API scripts]
* [https://github.com/bbajaj/relman_nag_tool nag tool]
* [http://viewvc.svn.mozilla.org/vc/projects/mozilla.com/ svn repo for web pages]
* [http://harthur.github.io/mozregression/ mozregression]

= Community Contributors =

Some of the above access & permissions will either not be accessible to community contributors or it might take a bit longer to achieve depending on the level & needs of the contributions being made.

Currently when Early Feedback Community Release Managers are onboarded we're basing it on these [http://lukasblakk.com/contribution-opportunity-early-feedback-community-release-manager/ blog] [http://lukasblakk.com/contribution-opportunity-early-feedback-community-release-manager-2/ posts] (one was based on the other). The short version is that we're looking for people who are interested in understanding how Release Management in a major Open Source project works and our hope is that they learn while also helping us maintain a higher level of quality and visibility into release-affecting issues than a small team of employees can manage.

How that can play out is in several ways. First, any new community member who wants to work with RelMan should have a very informal conversation with a current staff member to discuss their experience, interests, and then ultimately to come up with a good time for a regular meeting that can onboard them (if they're still interested) over a period of weeks & months.

Depending on the volunteer's time availability, usually 1 or 2 hour-long triage sessions a week are feasible. Ideally these will at least sometimes include other members of the team so that the new contributor is getting to know the rest of the members. Eventually the contributor should also start getting invited to (and attending when possible) our 30 min weekly team meeting.

== Links to get started ==
* [[Release_Management/Queries/Nightly|Nightly Triage]]
* [[Release_Management/Queries|All Queries]]
* [[RapidRelease/LandingPlan|Landing Plan]]
* [[Release_Management/aurora_Landing_Process|Aurora/DevEdition Landing Process]]

= Fun Tips & Tricks =
== Vidyo Conference Rooms ==
Sometimes when you're on the go and you need to dial into a vidyo room, you may not have time to find the info and having it already loaded in your phone can make a difference. Your RelMan teammates might be able to beam you the contact info from their phones, or you can add them yourself like this:
* Vidyo; Warp Core 6509030800,92,5312#
Rooms to mark as favourites and contacts: Spadina (Toronto), Release Coordination (Virtual room, no physical location)

== Subcribe to funstuff ==
* Request here https://bugzilla.mozilla.org/show_bug.cgi?id=391268

[[category:Release_Management|O]]

Firefox/Drivers

2015-03-26T15:09:23Z

Bkerensa: /* Release Management Team */

Mozilla Release Drivers are the group of individuals that are entrusted with the coordination of Firefox releases, formally defined by membership in the mozilla-next-drivers Bugzilla group and the release-drivers@mozilla.org mailing list. Since 2011 and the advent of the rapid release model, the Release Management Team has coordinated a majority of Firefox release work, from change approval based upon risk/reward to the tracking and resolution of critical release issues.

Below is a list (updated 2/19) of all those drivers who offer their unique expertise and retain the ability to manage pre-release Firefox branches as well as their associated issues.

===[mailto:release-mgmt@mozilla.com Release Management Team]===
* [mailto:lmandel@mozilla.com Lawrence Mandel]
* [mailto:sylvestre@mozilla.com Sylvestre Ledru]
* [mailto:ehenry@mozilla.com Liz Henry]

===Security===
* [mailto:abillings@mozilla.com Al Billings]
* [mailto:curtisk@mozilla.com Curtis Koenig]
* [mailto:dveditz@mozilla.com Daniel Veditz]

===Firefox Engineering===
* [mailto:bsmedberg@mozilla.com Benjamin Smedberg]
* [mailto:mconnor@mozilla.com Mike Connor]
* [mailto:dolske@mozilla.com Justin Dolske]
* [mailto:dtownsend@mozilla.com Dave Townsend]
* [mailto:gavin@gavinsharp.com Gavin Sharp]
* [mailto:johnath@mozilla.com Johnathan Nightingale]

===Platform Engineering===
* [mailto:bzbarsky@mozilla.com Boris Zbarsky]
* [mailto:dbaron@mozilla.com David Baron]
* [mailto:dbolter@mozilla.com David Bolter]
* [mailto:doug.turner@gmail.com Doug Turner]
* [mailto:roc@ocallahan.org Robert O'Callahan]
* [mailto:bmoss@mozilla.com Bob Moss]
* [mailto:danderson@mozilla.com David Anderson]
* [mailto:gal@mozilla.com Andreas Gal]
* [mailto:jmuizelaar@mozilla.com Jeff Muizelaar]
* [mailto:joe@mozilla.com Joe Drew]
* [mailto:sicking@mozilla.com Jonas Sicking]
* [mailto:josh@mozilla.com Josh Aas]
* [mailto:jst@mozilla.org Johnny Stenback]
* [mailto:jlebar@mozilla.com Justin Lebar]
* [mailto:jwatt@jwatt.org Jonathan Watt]
* [mailto:luke@mozilla.com Luke Wagner]
* [mailto:nihsanullah@mozilla.com Naveed Ihsanullah]
* [mailto:ted@mozilla.com Ted Mielczarek]
* [mailto:vlad@mozilla.com Vladimir Vukicevic]
* [mailto:ehsan@mozilla.com Ehsan Akhgari]

===Mobile Engineering===
* [mailto:blassey@mozilla.com Brad Lassey]
* [mailto:mfinkle@mozilla.com Mark Finkle]

===Project Management===
* [mailto:smooney@mozilla.com Sheila Mooney]
* [mailto:dietrich@mozilla.com Dietrich Ayala]
* [mailto:lmandel@mozilla.com Lawrence Mandel]

===Other Groups===
* [mailto:asa@mozilla.org Asa Dotzler]
* [mailto:chofmann@mozilla.org Chris Hofmann]
* [mailto:cwwmozilla@gmail.com Cheng Wang]

Firefox/Drivers

2015-03-26T15:09:01Z

Bkerensa: /* Release Management Team */

Mozilla Release Drivers are the group of individuals that are entrusted with the coordination of Firefox releases, formally defined by membership in the mozilla-next-drivers Bugzilla group and the release-drivers@mozilla.org mailing list. Since 2011 and the advent of the rapid release model, the Release Management Team has coordinated a majority of Firefox release work, from change approval based upon risk/reward to the tracking and resolution of critical release issues.

Below is a list (updated 2/19) of all those drivers who offer their unique expertise and retain the ability to manage pre-release Firefox branches as well as their associated issues.

===[mailto:release-mgmt@mozilla.com Release Management Team]===
* [mailto:lmandel@mozilla.com Lawrence Mandel]
* [mailto:sylvestre@mozilla.com Sylvestre Ledru]
* [mailto:lmandel@mozilla.com Liz Henry]

===Security===
* [mailto:abillings@mozilla.com Al Billings]
* [mailto:curtisk@mozilla.com Curtis Koenig]
* [mailto:dveditz@mozilla.com Daniel Veditz]

===Firefox Engineering===
* [mailto:bsmedberg@mozilla.com Benjamin Smedberg]
* [mailto:mconnor@mozilla.com Mike Connor]
* [mailto:dolske@mozilla.com Justin Dolske]
* [mailto:dtownsend@mozilla.com Dave Townsend]
* [mailto:gavin@gavinsharp.com Gavin Sharp]
* [mailto:johnath@mozilla.com Johnathan Nightingale]

===Platform Engineering===
* [mailto:bzbarsky@mozilla.com Boris Zbarsky]
* [mailto:dbaron@mozilla.com David Baron]
* [mailto:dbolter@mozilla.com David Bolter]
* [mailto:doug.turner@gmail.com Doug Turner]
* [mailto:roc@ocallahan.org Robert O'Callahan]
* [mailto:bmoss@mozilla.com Bob Moss]
* [mailto:danderson@mozilla.com David Anderson]
* [mailto:gal@mozilla.com Andreas Gal]
* [mailto:jmuizelaar@mozilla.com Jeff Muizelaar]
* [mailto:joe@mozilla.com Joe Drew]
* [mailto:sicking@mozilla.com Jonas Sicking]
* [mailto:josh@mozilla.com Josh Aas]
* [mailto:jst@mozilla.org Johnny Stenback]
* [mailto:jlebar@mozilla.com Justin Lebar]
* [mailto:jwatt@jwatt.org Jonathan Watt]
* [mailto:luke@mozilla.com Luke Wagner]
* [mailto:nihsanullah@mozilla.com Naveed Ihsanullah]
* [mailto:ted@mozilla.com Ted Mielczarek]
* [mailto:vlad@mozilla.com Vladimir Vukicevic]
* [mailto:ehsan@mozilla.com Ehsan Akhgari]

===Mobile Engineering===
* [mailto:blassey@mozilla.com Brad Lassey]
* [mailto:mfinkle@mozilla.com Mark Finkle]

===Project Management===
* [mailto:smooney@mozilla.com Sheila Mooney]
* [mailto:dietrich@mozilla.com Dietrich Ayala]
* [mailto:lmandel@mozilla.com Lawrence Mandel]

===Other Groups===
* [mailto:asa@mozilla.org Asa Dotzler]
* [mailto:chofmann@mozilla.org Chris Hofmann]
* [mailto:cwwmozilla@gmail.com Cheng Wang]

Release Management/Goals/2015Q2

2015-03-26T08:46:11Z

Bkerensa: /* Personal Development */

= Release Management Q2 2015 Goals =

== Release Management General ==
; Release Quality - Improve automation / reduce risk of manual errors

; Release Quality - Find issues earlier

; Communication

; Release Strategy

; Expand contributor involvement

== Firefox Desktop/Mobile ==
* Manage and coordinate active Firefox and Firefox for Android releases
** [Lawrence] Firefox 37
** [Sylvestre] Firefox 38
** [Liz+Lawrence] Firefox 39

== Firefox ESR ==
* [Benjamin] Kick Off ESR Survey with User Advocacy (Tyler Downer)

== Special Projects ==

== Personal Development ==
* [Benjamin] Dedicate more time to reading books in my Mozilla Safari Books Queue
* [Benjamin] More banjo practice

Release Management/Goals/2015Q2

2015-03-26T08:42:26Z

Bkerensa: /* Firefox ESR */

Reps/Meetings/Council-2015-02-11

2015-02-12T18:19:53Z

Bkerensa:

{{RemoCouncilMeeting
|date=2015/02/11 02:30:00 PM
|attendees=Nukeador, Ankitgadgil, Emmairwin,
}}
== New mentors ==
A voting process on new selection of mentors was successfully completed by
the council and agreed upon the new batch of mentors.
The council will now work on contacting the new selected mentors for their
availability to take up the new role.
(Also a Wiki for mentor selection, requirements is in process.)

== Paris leadership meetup ==
The Reps council and peers are meeting in Paris in mid March to take
discussions and discuss on various ongoing & future programs/projects for
reps.
As a rep you are encouraged to let the council know if you have any ideas
or thoughts worth sharing.

== Bangladesh Community health ==
Community health and Reps positions in Bangladesh were discussed.
The council will be working with Gen Kanai and Brian King on this.

== Emails to the council ==
* Documentation platform selections,
* Decision making system,
* Suggestion of having private council conversation agenda 7 days in
advance

The council is in discussion on these topics, some of them are ongoing
action items.

== Over budget Events ==
The council discussed about events which are over-budget in accordance to
the impact they make.
Working with various projects teams (like [[Webmaker]] and Hive) to understand
factors for events:
* What are impactful events
* How and when to sponsor travel budgets
* What is a good budget amount referring the promised impact
* Wiki info page on these topics

== Mozilla Reps Application Form ==
Changing the select box for "Sex" to "Gender" to make the question more
about identity and less about biology.
The council agrees and will work with the [http://bugzilla.mozilla.org Bugzilla] team on the same.

== Mozspace Pilots ==
The council is working on a policy for deciding the best criteria on pilots
for Mozspaces.

Reps/Meetings/Council-2015-02-11

2015-02-12T18:19:16Z

Bkerensa:

{{RemoCouncilMeeting
|date=2015/02/11 02:30:00 PM
|attendees=Nukeador, Ankitgadgil, Emmairwin,
}}

== New mentors ==
A voting process on new selection of mentors was successfully completed by
the council and agreed upon the new batch of mentors.
The council will now work on contacting the new selected mentors for their
availability to take up the new role.
(Also a Wiki for mentor selection, requirements is in process.)

== Paris leadership meetup ==
The Reps council and peers are meeting in Paris in mid March to take
discussions and discuss on various ongoing & future programs/projects for
reps.
As a rep you are encouraged to let the council know if you have any ideas
or thoughts worth sharing.

== Bangladesh Community health ==
Community health and Reps positions in Bangladesh were discussed.
The council will be working with Gen Kanai and Brian King on this.

== Emails to the council ==
* Documentation platform selections,
* Decision making system,
* Suggestion of having private council conversation agenda 7 days in
advance

The council is in discussion on these topics, some of them are ongoing
action items.

== Over budget Events ==
The council discussed about events which are over-budget in accordance to
the impact they make.
Working with various projects teams (like [[Webmaker]] and Hive) to understand
factors for events:
* What are impactful events
* How and when to sponsor travel budgets
* What is a good budget amount referring the promised impact
* Wiki info page on these topics

== Mozilla Reps Application Form ==
Changing the select box for "Sex" to "Gender" to make the question more
about identity and less about biology.
The council agrees and will work with the [http://bugzilla.mozilla.org Bugzilla] team on the same.

== Mozspace Pilots ==
The council is working on a policy for deciding the best criteria on pilots
for Mozspaces.

User:Bkerensa/ReMo-Council/Meetings

2015-02-11T00:21:41Z

Bkerensa: Created page with "== 2015 == February 10th, 2015"

== 2015 ==
[[User:Bkerensa/ReMo-Council/Meetings/02-15-2015|February 10th, 2015]]

User:Bkerensa/ReMo-Council/Meetings/02-15-2015

2015-02-11T00:21:08Z

Bkerensa: Created page with "Attendance: == Agenda Items == ==== Policy on domains and hosting ==== The council discussed a need to make a policy on requiring domain names to be transferred to Mozill..."

Attendance:

== Agenda Items ==

==== Policy on domains and hosting ====

The council discussed a need to make a policy on requiring domain names to be transferred to Mozilla before hosting can be offered.

'''Action:''' Motion to require domains be owned by Mozilla before services offered.
'''
Vote:''' Motion passes unanimously

==== ReMo Camp Date ====

The council was asked what month would be best for Remo Camp in terms of logistics.

'''Action:''' Rosana makes motion to approve June for ReMo Camp
'''
Vote:''' Motion passes unanimously

'''Meeting Adjourned by Chair

Next Meeting on'''

Release Management/ESR Landing Process

2015-02-10T20:01:55Z

Bkerensa:

'''Goal:''' We'd like to have a lightweight process that prevents "surprise" ESR landings at the 11th hour and makes sure ESR patches are created very soon after their related mainline patches

=== REPOS ===
'''The ESR{{ESR_CURRENT}} repo:''' https://hg.mozilla.org/releases/mozilla-esr{{ESR_CURRENT}}/
'''The ESR{{ESR_NEXT}} repo:''' https://hg.mozilla.org/releases/mozilla-esr{{ESR_NEXT}}/

===More info about the ESR===
* https://wiki.mozilla.org/Enterprise/Firefox/ExtendedSupport:Proposal
* https://www.mozilla.org/en-US/firefox/organizations/
* [https://www.mozilla.org/en-US/firefox/organizations/all/ Download]

===What should land on mozilla-esr{{ESR_CURRENT}}/mozilla-esr{{ESR_NEXT}}===

Security and some major stability fixes when they're landed/merged onto mozilla-beta, or fixes for regressions specific to the ESR. Exception: If patches only make changes to tests, test harnesses or anything else that does not affect the shipped builds, they may land with self approval (use a=testonly, a=npotb etc).

=== The associated flags===

approval-mozilla-esr{{ESR_CURRENT}}: ''?'', ''+'', ''-''

approval-mozilla-esr{{ESR_NEXT}}: ''?'', ''+'', ''-''

tracking-esr{{ESR_CURRENT}}: ''?'', ''-'', ''{{BETA_VERSION}}+'', ''{{AURORA_VERSION}}+'', ''{{NIGHTLY_VERSION}}+'', ...

tracking-esr{{ESR_NEXT}}: ''?'', ''-'', ''{{BETA_VERSION}}+'', ''{{AURORA_VERSION}}+'', ''{{NIGHTLY_VERSION}}+'', ...

status-esr{{ESR_CURRENT}}: ''?'', ''unaffected'', ''wontfix'', ''affected'', ''checkin-pending'', ''fixed'', ''verified''

status-esr{{ESR_NEXT}}: ''?'', ''unaffected'', ''wontfix'', ''affected'', ''checkin-pending'', ''fixed'', ''verified''

===The process===

1) When an engineer believes that a stability bug needs to be addressed for the ESR, or a security fix that's landed on a branch affects the ESR:
* Set '''tracking-esr{{ESR_CURRENT}}''' (and if we're in the middle of supporting 2 versions, then also tracking-esr{{ESR_NEXT}} to '''?'''
* Set '''tracking-esr{{ESR_CURRENT}}''' (and if we're in the middle of supporting 2 versions, then also tracking-esr{{ESR_NEXT}} to '''affected''' if an ESR patch is still being worked on
* Set '''approval-mozilla-esr{{ESR_CURRENT}}''' (and if we're in the middle of support 2 versions, then also approval-mozilla-esr{{ESR_NEXT}} to '''?''' and '''status-esr{{ESR_CURRENT}}/{{ESR_NEXT}}''' checkin-pending if a patch is ''ready to land on mozilla-esr{{ESR_CURRENT}}/{{ESR_NEXT}}''
2) Members of both Security and Release Management teams will triage tracking-esr{{ESR_CURRENT}}/{{ESR_NEXT}}=?, and if agreement is that it's needed for the ESR, the tracking flag will be set to the first version of mainline Firefox that the patch is present in and the '''approval-mozilla-esr{{ESR_CURRENT}}/{{ESR_NEXT}}''' flag will be set to '''+'''.
* In the case of an ESR-specific regression, we'll track for the next ESR release (e.g.: {{ESR_FUTURE}}).
* Why are we using mainline versions to track the ESR? According to the ESR proposal, a chemspill uses a minor version number, thus throwing off our tracking flags. Additionally, engineers shouldn't have to know what version of the ESR we're on.
3) Once the mozilla-beta version matches the tracking-esr{{ESR_CURRENT}}/{{ESR_NEXT}} version(s), Security and Release Management teams will triage those bugs and make sure affected/checkin-pending fixes are landed at least 1 week prior to release so that we can go-to-build.
* Approval is required, so add "a={whoever set the approval-mozilla-esr10 flag to +}" to the commit message.
* After landing the patch, set status-esr{{ESR_CURRENT}}/{{ESR_NEXT}} to "fixed".
* Our beta period for the ESR will be to push this build to FTP a week early for qualification by enterprises.

= ESR Triage Queries =
CURRENT TEMPLATE VALUES:

[[Template:ESR_PREVIOUS|ESR_PREVIOUS (click to edit)]]: {{ESR_PREVIOUS}}

[[Template:ESR_CURRENT|ESR_CURRENT (click to edit)]]: {{ESR_CURRENT}}

[[Template:ESR_CURRENT_DOT|ESR_CURRENT_DOT (click to edit)]]: {{ESR_CURRENT_DOT}}

[[Template:ESR_NEXT|ESR_NEXT (click to edit)]]: {{ESR_NEXT}}

[[Template:ESR_NEXT_DOT|ESR_NEXT_DOT (click to edit)]]: {{ESR_NEXT_DOT}}

[[Template:ESR_FUTURE|ESR_FUTURE]]: {{ESR_FUTURE}}

== ESR{{ESR_CURRENT}} ==
* [https://bugzilla.mozilla.org/buglist.cgi?o0=equals&f0=cf_tracking_firefox_esr{{ESR_CURRENT}}&v0=%3F ESR{{ESR_CURRENT}} Nominations] - track for an upcoming ESR release, or don't track at all
* [https://bugzilla.mozilla.org/buglist.cgi?o0=substring&f0=flagtypes.name&v0=approval-mozilla-esr{{ESR_CURRENT}}%3F ESR-{{ESR_CURRENT}} approval requests] - approve/deny, make sure {{BETA_VERSION}}+ is set

* [https://bugzilla.mozilla.org/buglist.cgi?f1=bug_group&o3=nowordssubstr&v3=unaffected%20verified%20fixed%20disabled&o1=substring&o2=nowordssubstr&chfieldto=Now&chfield=resolution&chfieldfrom=2014-04-28&f3=cf_status_firefox{{ESR_CURRENT}}&f2=cf_status_firefox_esr{{ESR_CURRENT}}&chfieldvalue=FIXED&v1=core-security&v2=unaffected%20wontfix%20verified%20fixed%20affected%20disabled&list_id=8200291 Security bugs fixed on mainline, status not marked for ESR{{ESR_CURRENT}}] - mark the ESR as affected/unaffected
** Minus b2g,tbird: [https://bugzilla.mozilla.org/buglist.cgi?o0=nowordssubstr&f1=bug_group&o3=nowordssubstr&f0=product&v3=unaffected%20verified%20fixed%20disabled&o1=substring&v0=Boot2Gecko%20Testing%20MailNews%20Thunderbird%20Calendar%20SeaMonkey%20OS&o2=nowordssubstr&chfieldto=Now&chfield=resolution&chfieldfrom=2014-04-28&f3=cf_status_firefox{{ESR_CURRENT}}&f2=cf_status_firefox_esr{{ESR_CURRENT}}&chfieldvalue=FIXED&v1=core-security&v2=unaffected%20wontfix%20verified%20fixed%20affected%20disabled Security bugs fixed on mainline, status not marked for ESR{{ESR_CURRENT}}]

* [https://bugzilla.mozilla.org/buglist.cgi?o1=notsubstring&f2=bug_group&resolution=FIXED&o0=equals&v1=%2B&f0=cf_status_firefox_esr{{ESR_CURRENT}}&bug_status=RESOLVED&bug_status=VERIFIED&f1=cf_tracking_firefox_esr{{ESR_CURRENT}}&v2=core-security&v0=affected&o2=substring Bugs marked as affected for ESR, but not tracked] - track for a release or wontfix
* [https://bugzilla.mozilla.org/buglist.cgi?o5=equals&f10=CP&f1=OP&f0=OP&f8=cf_tracking_firefox_esr{{ESR_CURRENT}}&o2=anywordssubstr&f9=CP&j7=OR&f4=OP&v5=affected&j1=OR&f3=CP&f2=cf_status_firefox{{BETA_VERSION}}&j4=OR&f5=cf_status_firefox_esr{{ESR_CURRENT}}&v8={{BETA_VERSION}}%2B&f6=CP&v2=fixed%20verified&f7=OP&o8=notequals&o11=notsubstring&f11=component&v11=Mozmill May need to land now] - {{BETA_VERSION}}+ if necessary, or wontfix

* [https://bugzilla.mozilla.org/buglist.cgi?f1=cf_tracking_firefox_esr{{ESR_CURRENT}}&o1=equals&o2=nowordssubstr&f2=cf_status_firefox_esr{{ESR_CURRENT}}&v1={{BETA_VERSION}}%2B&v2=fixed%20verified%20disabled%20wontfix%20unaffected Bugs that need to be fixed on ESR{{ESR_CURRENT}} this cycle] - follow up with the engineers
* [https://bugzilla.mozilla.org/buglist.cgi?f1=cf_tracking_firefox_esr{{ESR_CURRENT}}&o1=equals&o2=nowordssubstr&f2=cf_status_firefox_esr{{ESR_CURRENT}}&v1=%2B&v2=%20fixed%20verified Tracked, but not for a specific version] - follow up and decide on what version of the ESR these fixes should go into

== ESR{{ESR_NEXT}} ==
'''Note: not useful until Firefox {{ESR_NEXT}} is on Aurora or later'''
* [https://bugzilla.mozilla.org/buglist.cgi?o0=equals&f0=cf_tracking_firefox_esr{{ESR_NEXT}}&v0=%3F ESR{{ESR_NEXT}} Nominations] - track for an upcoming ESR release, or don't track at all
* [https://bugzilla.mozilla.org/buglist.cgi?o0=substring&f0=flagtypes.name&v0=approval-mozilla-esr{{ESR_NEXT}}%3F ESR-{{ESR_NEXT}} approval requests] - approve/deny, make sure {{BETA_VERSION}}+ is set

* [https://bugzilla.mozilla.org/buglist.cgi?keywords=low%2Cmoderate&keywords_type=nowords&f1=bug_group&o3=nowordssubstr&v3=unaffected%20verified%20fixed%20disabled&o1=substring&o2=nowordssubstr&chfieldto=Now&chfield=resolution&chfieldfrom=2015-02-23&f3=cf_status_firefox{{ESR_NEXT}}&f2=cf_status_firefox_esr{{ESR_NEXT}}&chfieldvalue=FIXED&v1=core-security&v2=unaffected%20wontfix%20verified%20fixed%20affected%20disabled1&v0=Boot2Gecko%20Testing%20MailNews%20Thunderbird%20Calendar%20SeaMonkey%20OS&f0=product&o0=nowordssubstr Security bugs (not low/moderate, minus OS/TB/SM) fixed on mainline, status not marked for ESR{{ESR_NEXT}}] - mark the ESR as affected/unaffected
** wider net: [https://bugzilla.mozilla.org/buglist.cgi?v4=core-security&o5=substring&keywords=sec-want&keywords_type=nowords&f1=product&o7=nowordssubstr&o1=nowordssubstr&classification=Client%20Software&classification=Components&o2=nowordssubstr&v7=unaffected%20fixed%20verified%20disabled&f4=bug_group&chfieldto=Now&v5=sec-&chfield=resolution&chfieldfrom=2015-02-23&f3=OP&f2=cf_status_firefox_esr{{ESR_NEXT}}&o4=substring&chfieldvalue=FIXED&f5=keywords&j3=OR&v1=Calendar%20OS%20Testing%20SeaMonkey%20Mozilla&f6=CP&v2=unaffected%20wontfix%20verified%20fixed%20affected%20disabled&f7=cf_status_firefox{{ESR_NEXT}} security bugs fixed on mainline, including sec-low/moderate and Thunderbird]

* [https://bugzilla.mozilla.org/buglist.cgi?o1=notsubstring&f2=bug_group&resolution=FIXED&o0=equals&v1=%2B&f0=cf_status_firefox_esr{{ESR_NEXT}}&bug_status=RESOLVED&bug_status=VERIFIED&f1=cf_tracking_firefox_esr{{ESR_NEXT}}&v2=core-security&v0=affected&o2=substring Bugs marked as affected for ESR, but not tracked] - track for a release or wontfix
* [https://bugzilla.mozilla.org/buglist.cgi?o5=equals&f10=CP&f1=OP&f0=OP&f8=cf_tracking_firefox_esr{{ESR_NEXT}}&o2=anywordssubstr&f9=CP&j7=OR&f4=OP&v5=affected&j1=OR&f3=CP&f2=cf_status_firefox{{BETA_VERSION}}&j4=OR&f5=cf_status_firefox_esr{{ESR_NEXT}}&v8={{BETA_VERSION}}%2B&f6=CP&v2=fixed%20verified&f7=OP&o8=notequals&o11=notsubstring&f11=component&v11=Mozmill May need to land now] - {{BETA_VERSION}}+ if necessary, or wontfix

* [https://bugzilla.mozilla.org/buglist.cgi?f1=cf_tracking_firefox_esr{{ESR_NEXT}}&o1=equals&o2=nowordssubstr&f2=cf_status_firefox_esr{{ESR_NEXT}}&v1={{BETA_VERSION}}%2B&v2=fixed%20verified%20disabled%20wontfix%20unaffected Bugs that need to be fixed on ESR{{ESR_NEXT}} this cycle] - follow up with the engineers
* [https://bugzilla.mozilla.org/buglist.cgi?f1=cf_tracking_firefox_esr{{ESR_NEXT}}&o1=equals&o2=nowordssubstr&query_format=advanced&f2=cf_status_firefox_esr{{ESR_NEXT}}&v1=%2B&v2=%20fixed%20verified Tracked, but not for a specific version] - follow up and decide on what version of the ESR these fixes should go into

== B2G18 ==
NOTE: Post-merge, we'll likely need to create new static links for 20+ b2g bugs (still landing to v1.1, along with 21+ bugs)

* [https://bugzilla.mozilla.org/buglist.cgi?type1-0-0=equals;list_id=5417323;field0-0-0=flagtypes.name;query_format=advanced;value1-0-0=core-security;type0-0-0=substring;value0-0-0=approval-mozilla-b2g18%3F;field1-0-0=bug_group B2G-18 security approval requests] - approve/deny, make sure {{BETA_VERSION}}+ is set

* [https://bugzilla.mozilla.org/buglist.cgi?type0-1-0=nowordssubstr;list_id=5417475;field0-1-0=cf_status_b2g18;field0-0-0=bug_group;chfieldto=Now;query_format=advanced;chfield=resolution;value0-2-0=unaffected%20verified%20fixed%20disabled;chfieldfrom=2012-10-08;value0-1-0=unaffected%20wontfix%20verified%20fixed%20affected%20disabled;chfieldvalue=FIXED;field0-2-0=cf_status_firefox18;type0-0-0=equals;value0-0-0=core-security;type0-2-0=nowordssubstr Security bugs fixed on mainline, status not marked for B2G18] - mark B2G as affected/unaffected
** [https://bugzilla.mozilla.org/buglist.cgi?o5=substring&list_id=8461921&o1=nowordssubstr&o2=nowordssubstr&v5=core-security&chfield=resolution&chfieldfrom=2012-10-08&chfieldvalue=FIXED&j4=OR&v1=Thunderbird%20mail%20seamonkey%20services%20calendar%20testing&v2=unaffected%20wontfix%20verified%20fixed%20affected%20disabled&f1=product&o3=nowordssubstr&v6=sec-critical%20sec-high&v3=unaffected%20wontfix%20verified%20fixed%20affected%20disabled&classification=Client%20Software&classification=Components&o6=anywordssubstr&f4=OP&chfieldto=Now&query_format=advanced&f3=cf_status_firefox18&f2=cf_status_b2g18&f5=bug_group&f6=keywords security bugs fixed on mainline, status not marked for B2G18] (alternate query, includes high priority unhidden bugs, skips Thunderbird et al)
* [https://bugzilla.mozilla.org/buglist.cgi?type0-1-0=notsubstring&list_id=5417254&field0-1-0=cf_tracking_b2g18&field0-0-0=cf_status_b2g18&resolution=FIXED&query_format=advanced&value0-2-0=core-security&value0-1-0=%2B&bug_status=RESOLVED&bug_status=VERIFIED&field0-2-0=bug_group&type0-0-0=equals&value0-0-0=affected&type0-2-0=equals Security bugs marked as affected for B2G, but not tracked] - track for a release or wontfix
* [https://bugzilla.mozilla.org/buglist.cgi?field0-3-0=bug_group;type0-1-0=equals;list_id=5417343;field0-1-0=cf_status_b2g18;field0-0-0=cf_status_firefox{{BETA_VERSION}};value0-3-0=core-security;query_format=advanced;value0-2-0={{BETA_VERSION}}%2B;value0-1-0=affected;type0-3-0=equals;field0-2-0=cf_status_b2g18;type0-0-0=anywordssubstr;value0-0-0=fixed%20verified;type0-2-0=notequals Security bugs that may need to land now] - {{BETA_VERSION}}+ if necessary, or wontfix
* [https://bugzilla.mozilla.org/buglist.cgi?type0-1-0=equals;list_id=5417399;field0-1-0=cf_status_b2g18;field0-0-0=target_milestone;query_format=advanced;value0-2-0=core-security;value0-1-0=affected;bug_status=RESOLVED;bug_status=VERIFIED;field0-2-0=bug_group;type0-0-0=substring;value0-0-0={{BETA_VERSION}};type0-2-0=equals Security bugs that also may need to land now]

* [https://bugzilla.mozilla.org/buglist.cgi?type0-1-0=nowordssubstr;list_id=5417386;field0-1-0=cf_status_b2g18;field0-0-0=cf_tracking_b2g18;value0-1-0=fixed%20verified%20disabled%20wontfix%20unaffected;type0-0-0=equals;value0-0-0={{BETA_VERSION}}%2B;type0-2-0=equals;query_format=advanced;value0-2-0=core-security;field0-2-0=bug_group Bugs that need to be fixed on B2G18 this cycle] - follow up with the engineers

== B2G26(v1.2) ==
* [https://bugzilla.mozilla.org/buglist.cgi?o5=substring&f1=product&v6=sec-critical%20sec-high&o3=nowordssubstr&list_id=8780228&o1=nowordssubstr&classification=Client%20Software&classification=Components&o6=anywordssubstr&o2=nowordssubstr&f4=OP&v5=core-security&chfieldto=Now&query_format=advanced&chfield=resolution&chfieldfrom=2013-10-28&f2=cf_status_b2g_1_2&chfieldvalue=FIXED&j4=OR&f5=bug_group&v1=Thunderbird%20mail%20seamonkey%20services%20calendar%20testing&f6=keywords&v2=unaffected%20wontfix%20verified%20fixed%20affected%20disabled Security bugs fixed on mainline, status not marked for 1.2 ] - mark status-b2g-v1.2: as affected/unaffected/wontfix

= ESR Timeline and Activities =
=== Weekly ===
Review ESR queries
* for potential ESR uplifts
* to review uplift requests
* to follow up on approved uplifts that have not landed.
=== Week 4 ===
Tue: Send [[Release_Management/ESR_Landing_Process#Smoke_Test_Request|smoke test e-mail]] to enterprise list

=== Week 5 ===
Mon:
# Kick off build in ship-it
# Send [[Release_Management/ESR_Landing_Process#Go_To_Build_for_ESR_Candidate|go to build e-mail]] for ESR candidate to release-drivers.
# Create release notes in Nucleus

=== Release date ===
All happens after mainline release goes live
# Post request for QA sign-off to r-d
# Wait for QA sign-off e-mail to r-d from Matt Wobensmith
# Send [[Release_Management/ESR_Landing_Process#Request_to_push_release_to_esr_channel|push release to esr channel e-mail]] request for releng to r-d
# Mark release notes as public in Nucleus
# Update [http://viewvc.svn.mozilla.org/vc/libs/product-details/history product details in SVN] ([[Release_Management/Release_Notes_and_Product_Details|instructions]], remember to push the [[Release_Management/Release_Notes_and_Product_Details#Completion_Checklist|big red button]])
# Add release to [[Releases|historical releases page]]
# Post [[Release_Management/ESR_Landing_Process#Release_Announcement|release announcement]] to enterprise mailing list

== Sample E-mails ==
=== Smoke Test Request ===
<pre style="white-space:pre-wrap;">
Subject: Request: Smoke Test Firefox {{ESR_NEXT}}esr

As we approach the ESR {{ESR_NEXT}} release date of June 10th, we'd like your help in smoke testing the latest pre-release builds. Our request is not for full qualification of the builds but rather exploratory testing of internal websites and applications for which our QA team does not have access.

Please file bugs for any critical regressions that you find in Bugzilla and make sure to set the need-info? flag on release-mgmt at mozilla.com <mailto:release-mgmt at mozilla.com> in order to alert the release management team to the issues. Alternatively, you can directly email release-mgmt at mozilla.com <mailto:release-mgmt at mozilla.com> or this list.

Thank you for your continued support in ensuring high quality ESR releases.

<name>
Firefox Release Manager

*NOTE*: Do not deploy any of the pre-release builds listed below. These pre-release builds will not update correctly and will not be supported by Mozilla.

ESR {{ESR_NEXT}} Windows:
https://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-esr24/firefox-24.6.0esrpre.en-US.win32.installer.exe

ESR {{ESR_NEXT}} Mac OS X:
https://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-esr24/firefox-24.6.0esrpre.en-US.mac.dmg

ESR {{ESR_NEXT}} Linux 32 bits:
https://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-esr24/firefox-24.6.0esrpre.en-US.linux-i686.tar.bz2

ESR {{ESR_NEXT}} Linux 64 bits:
https://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-esr24/firefox-24.6.0esrpre.en-US.linux-x86_64.tar.bz2
</pre>

=== Go To Build for ESR Candidate ===
<pre style="white-space:pre-wrap;">
Subject: Please build ESR 24.5.0 build#1

Submitted to ship-it.

changeset <changeset id>

Thanks,
<name>
</pre>
=== Request to push release to esr channel ===
<pre style="white-space:pre-wrap;">
Subject: Please push Firefox 24.5.0esr build #1 to the ESR channel

Hello,

QA has signed off on the desktop release. Please push ESR to the esr release channel.

Thanks,
<name>
</pre>

=== Release Announcement ===
<pre>
Subject: Firefox 24.6.0esr released

I'm pleased to announce the release of Firefox ESR 24.6.0. This release includes security fixes in line with Firefox 30.

You can find installers for Windows / Mac OS X / GNU/Linux here:
https://www.mozilla.org/en-US/firefox/organizations/all/

And the release notes are available here:
https://www.mozilla.org/en-US/firefox/24.6.0/releasenotes/

<name>
Firefox Release Manager
</pre>
[[category:Release_Management|E]]

= Branching Logistics =
When we have the overlapping ESR (and the first build of a major version number for the ESR.next - 10, 17, 24, 31, etc) we do build a separate build with its own branding from the newly minted branch. See https://wiki.mozilla.org/Releases/Firefox_24.0.esr/BuildNotes for how to kick off the builds and http://hg.mozilla.org/releases/mozilla-esr31/rev/e91c79c4c04b for an example of the custom configs needed for that first build's partials that has to land before kicking off the build in ship-it.

User:Bkerensa/tb-esr-queries

2015-01-30T20:41:24Z

Bkerensa: Created page with "= <center>TB Nightly ({{CENTRAL_VERSION}})</center> = == Queries == * [https://bugzilla.mozilla.org/buglist.cgi?o5=notequals&list_id=6873273&v11=unaffected&j10=OR&o14=notequa..."

= <center>TB Nightly ({{CENTRAL_VERSION}})</center> =

== Queries ==
* [https://bugzilla.mozilla.org/buglist.cgi?o5=notequals&list_id=6873273&v11=unaffected&j10=OR&o14=notequals&f13=OP&o2=equals&j16=OR&v5=wontfix&f12=CP&j4=OR&f14=cf_status_thunderbird_esr{{CENTRAL_VERSION}}&o17=notequals&o20=notequals&v2=%2B&f21=CP&known_name=Tracking{{CENTRAL_VERSION}}%2B&f10=OP&f19=OP&f{{CENTRAL_VERSION}}=CP&f1=OP&f20=cf_status_thunderbird_esr{{CENTRAL_VERSION}}&j13=OR&f8=cf_status_thunderbird_esr{{CENTRAL_VERSION}}&f0=OP&j19=OR&o11=notequals&f18=CP&columnlist=bug_severity%2Cpriority%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate%2Ccf_tracking_thunderbird_esr17%2Ccf_tracking_thunderbird_esr18%2Ccf_status_thunderbird_esr17%2Ccf_status_thunderbird_esr18&f15=CP&query_based_on=Tracking{{CENTRAL_VERSION}}%2B&f9=CP&j7=OR&v20=verified%20disabled&f4=OP&query_format=advanced&j1=OR&v17=disabled&f3=CP&f2=cf_tracking_thunderbird_esr{{CENTRAL_VERSION}}&f11=cf_status_thunderbird_esr{{CENTRAL_VERSION}}&f5=cf_status_thunderbird_esr{{CENTRAL_VERSION}}&f17=cf_status_thunderbird_esr{{CENTRAL_VERSION}}&v8=fixed&v14=verified&f6=CP&f7=OP&o8=notequals&f16=OP Full unresolved tracking list]
** [https://bugzilla.mozilla.org/buglist.cgi?o5=notequals&list_id=6873481&v11=unaffected&j10=OR&o14=notequals&f13=OP&o2=equals&j16=OR&v5=wontfix&f12=CP&j4=OR&f14=cf_status_thunderbird_esr{{CENTRAL_VERSION}}&o17=notequals&o20=notequals&v2=%2B&f21=CP&known_name=Tracking{{CENTRAL_VERSION}}%2B&f10=OP&f19=OP&f22=CP&f1=OP&f20=cf_status_thunderbird_esr{{CENTRAL_VERSION}}&j13=OR&f8=cf_status_thunderbird_esr{{CENTRAL_VERSION}}&f0=OP&j19=OR&o11=notequals&f18=CP&f15=CP&query_based_on=Tracking{{CENTRAL_VERSION}}%2B&f9=CP&j7=OR&v20=verified%20disabled&f4=OP&query_format=advanced&j1=OR&v17=disabled&f3=CP&f2=cf_tracking_thunderbird_esr{{CENTRAL_VERSION}}&f11=cf_status_thunderbird_esr{{CENTRAL_VERSION}}&bug_status=RESOLVED&bug_status=VERIFIED&f5=cf_status_thunderbird_esr{{CENTRAL_VERSION}}&f17=cf_status_thunderbird_esr{{CENTRAL_VERSION}}&v8=fixed&v14=verified&f6=CP&f7=OP&o8=notequals&f16=OP Resolved/Fixed]
** [https://bugzilla.mozilla.org/buglist.cgi?o5=notequals&v11=unaffected&j10=OR&o14=notequals&f13=OP&o2=equals&j16=OR&f23=cf_status_thunderbird_esr{{AURORA_VERSION}}&v5=wontfix&f12=CP&v24=affected&j4=OR&f14=cf_status_thunderbird_esr{{CENTRAL_VERSION}}&o17=notequals&o20=notequals&f24=cf_status_thunderbird_esr{{AURORA_VERSION}}&v2=%2B&f21=CP&known_name=Tracking{{CENTRAL_VERSION}}%2B&f10=OP&f19=OP&f22=CP&f1=OP&f20=cf_status_thunderbird_esr{{CENTRAL_VERSION}}&j13=OR&f8=cf_status_thunderbird_esr{{CENTRAL_VERSION}}&f0=OP&j19=OR&o11=notequals&o24=notequals&f18=CP&columnlist=bug_severity%2Cpriority%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate%2Ccf_status_thunderbird_esr{{AURORA_VERSION}}%2Ccf_status_thunderbird_esr{{CENTRAL_VERSION}}&f15=CP&query_based_on=Tracking{{CENTRAL_VERSION}}%2B&f9=CP&j7=OR&v20=verified%20disabled&f4=OP&o23=notequals&query_format=advanced&v23=wontfix&j1=OR&v17=disabled&f3=CP&f2=cf_tracking_thunderbird_esr{{CENTRAL_VERSION}}&f11=cf_status_thunderbird_esr{{CENTRAL_VERSION}}&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&f5=cf_status_thunderbird_esr{{CENTRAL_VERSION}}&f17=cf_status_thunderbird_esr{{CENTRAL_VERSION}}&v8=fixed&v14=verified&f6=CP&f7=OP&o8=notequals&f16=OP&list_id=6873202 Nightly regressions, all security, no resolved]
** [https://bugzilla.mozilla.org/buglist.cgi?o5=notequals&v11=unaffected&j10=OR&v25=unaffected&o14=notequals&f13=OP&o2=equals&j16=OR&f23=cf_status_thunderbird_esr21&v5=wontfix&f12=CP&f25=cf_status_thunderbird_esr21&v24=core-security&j4=OR&f14=cf_status_thunderbird_esr{{CENTRAL_VERSION}}&o17=notequals&o20=notequals&f24=bug_group&v2=%2B&f21=CP&known_name=Tracking{{CENTRAL_VERSION}}%2B&f10=OP&f19=OP&f22=CP&f1=OP&f20=cf_status_thunderbird_esr{{CENTRAL_VERSION}}&j13=OR&f8=cf_status_thunderbird_esr{{CENTRAL_VERSION}}&f0=OP&o25=notequals&j19=OR&o11=notequals&o24=equals&f18=CP&columnlist=bug_severity%2Cpriority%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate%2Ccf_status_thunderbird_esr21%2Ccf_status_thunderbird_esr{{CENTRAL_VERSION}}&f15=CP&query_based_on=Tracking{{CENTRAL_VERSION}}%2B&f9=CP&j7=OR&v20=verified%20disabled&f4=OP&o23=anywordssubstr&query_format=advanced&v23=wontfix%20affected&n24=1&j1=OR&v17=disabled&f3=CP&f2=cf_tracking_thunderbird_esr{{CENTRAL_VERSION}}&f11=cf_status_thunderbird_esr{{CENTRAL_VERSION}}&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&f5=cf_status_thunderbird_esr{{CENTRAL_VERSION}}&f17=cf_status_thunderbird_esr{{CENTRAL_VERSION}}&v8=fixed&v14=verified&f6=CP&f7=OP&o8=notequals&f16=OP&list_id=6873222 Earlier regressions, non-security, no resolved]
== Tracked Bugs ==

<bugzilla>
{
"f1" : "cf_tracking_thunderbird_esr{{CENTRAL_VERSION}}",
"o1" : "equals",
"v1" : "?",
"include_fields": "id, summary, whiteboard, status, resolution"
}
</bugzilla>

== [https://bugzilla.mozilla.org/buglist.cgi?o2=equals&f2=cf_tracking_thunderbird_esr{{CENTRAL_VERSION}}&v2=%3F Tracking Nominations] ==
<bugzilla>
{
"f1" : "cf_tracking_thunderbird_esr{{CENTRAL_VERSION}}",
"o1" : "equals",
"v1" : "?",
"include_fields": "id, summary, whiteboard, status, resolution"
}
</bugzilla>

[https://bugzilla.mozilla.org/buglist.cgi?f1=cf_tracking_thunderbird_esr{{CENTRAL_VERSION}}&o1=equals&o2=equals&query_format=advanced&f2=bug_group&v1=%3F&v2=core-security Security tracking noms]

User:Bkerensa/tb-nightly-queries

2015-01-30T20:40:27Z

Bkerensa:

User:Bkerensa/tb-nightly-queries

2015-01-30T20:39:28Z

Bkerensa:

= <center>TB Nightly ({{CENTRAL_VERSION}})</center> =

== Queries ==
* [https://bugzilla.mozilla.org/buglist.cgi?o5=notequals&list_id=6873273&v11=unaffected&j10=OR&o14=notequals&f13=OP&o2=equals&j16=OR&v5=wontfix&f12=CP&j4=OR&f14=cf_status_thunderbird{{CENTRAL_VERSION}}&o17=notequals&o20=notequals&v2=%2B&f21=CP&known_name=Tracking{{CENTRAL_VERSION}}%2B&f10=OP&f19=OP&f{{CENTRAL_VERSION}}=CP&f1=OP&f20=cf_status_thunderbird{{CENTRAL_VERSION}}&j13=OR&f8=cf_status_thunderbird{{CENTRAL_VERSION}}&f0=OP&j19=OR&o11=notequals&f18=CP&columnlist=bug_severity%2Cpriority%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate%2Ccf_tracking_thunderbird_esr17%2Ccf_tracking_thunderbird_esr18%2Ccf_status_thunderbird17%2Ccf_status_thunderbird18&f15=CP&query_based_on=Tracking{{CENTRAL_VERSION}}%2B&f9=CP&j7=OR&v20=verified%20disabled&f4=OP&query_format=advanced&j1=OR&v17=disabled&f3=CP&f2=cf_tracking_thunderbird_esr{{CENTRAL_VERSION}}&f11=cf_status_thunderbird{{CENTRAL_VERSION}}&f5=cf_status_thunderbird{{CENTRAL_VERSION}}&f17=cf_status_thunderbird{{CENTRAL_VERSION}}&v8=fixed&v14=verified&f6=CP&f7=OP&o8=notequals&f16=OP Full unresolved tracking list]
** [https://bugzilla.mozilla.org/buglist.cgi?o5=notequals&list_id=6873481&v11=unaffected&j10=OR&o14=notequals&f13=OP&o2=equals&j16=OR&v5=wontfix&f12=CP&j4=OR&f14=cf_status_thunderbird{{CENTRAL_VERSION}}&o17=notequals&o20=notequals&v2=%2B&f21=CP&known_name=Tracking{{CENTRAL_VERSION}}%2B&f10=OP&f19=OP&f22=CP&f1=OP&f20=cf_status_thunderbird{{CENTRAL_VERSION}}&j13=OR&f8=cf_status_thunderbird{{CENTRAL_VERSION}}&f0=OP&j19=OR&o11=notequals&f18=CP&f15=CP&query_based_on=Tracking{{CENTRAL_VERSION}}%2B&f9=CP&j7=OR&v20=verified%20disabled&f4=OP&query_format=advanced&j1=OR&v17=disabled&f3=CP&f2=cf_tracking_thunderbird_esr{{CENTRAL_VERSION}}&f11=cf_status_thunderbird{{CENTRAL_VERSION}}&bug_status=RESOLVED&bug_status=VERIFIED&f5=cf_status_thunderbird{{CENTRAL_VERSION}}&f17=cf_status_thunderbird{{CENTRAL_VERSION}}&v8=fixed&v14=verified&f6=CP&f7=OP&o8=notequals&f16=OP Resolved/Fixed]
** [https://bugzilla.mozilla.org/buglist.cgi?o5=notequals&v11=unaffected&j10=OR&o14=notequals&f13=OP&o2=equals&j16=OR&f23=cf_status_thunderbird{{AURORA_VERSION}}&v5=wontfix&f12=CP&v24=affected&j4=OR&f14=cf_status_thunderbird{{CENTRAL_VERSION}}&o17=notequals&o20=notequals&f24=cf_status_thunderbird{{AURORA_VERSION}}&v2=%2B&f21=CP&known_name=Tracking{{CENTRAL_VERSION}}%2B&f10=OP&f19=OP&f22=CP&f1=OP&f20=cf_status_thunderbird{{CENTRAL_VERSION}}&j13=OR&f8=cf_status_thunderbird{{CENTRAL_VERSION}}&f0=OP&j19=OR&o11=notequals&o24=notequals&f18=CP&columnlist=bug_severity%2Cpriority%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate%2Ccf_status_thunderbird{{AURORA_VERSION}}%2Ccf_status_thunderbird{{CENTRAL_VERSION}}&f15=CP&query_based_on=Tracking{{CENTRAL_VERSION}}%2B&f9=CP&j7=OR&v20=verified%20disabled&f4=OP&o23=notequals&query_format=advanced&v23=wontfix&j1=OR&v17=disabled&f3=CP&f2=cf_tracking_thunderbird_esr{{CENTRAL_VERSION}}&f11=cf_status_thunderbird{{CENTRAL_VERSION}}&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&f5=cf_status_thunderbird{{CENTRAL_VERSION}}&f17=cf_status_thunderbird{{CENTRAL_VERSION}}&v8=fixed&v14=verified&f6=CP&f7=OP&o8=notequals&f16=OP&list_id=6873202 Nightly regressions, all security, no resolved]
** [https://bugzilla.mozilla.org/buglist.cgi?o5=notequals&v11=unaffected&j10=OR&v25=unaffected&o14=notequals&f13=OP&o2=equals&j16=OR&f23=cf_status_thunderbird21&v5=wontfix&f12=CP&f25=cf_status_thunderbird21&v24=core-security&j4=OR&f14=cf_status_thunderbird{{CENTRAL_VERSION}}&o17=notequals&o20=notequals&f24=bug_group&v2=%2B&f21=CP&known_name=Tracking{{CENTRAL_VERSION}}%2B&f10=OP&f19=OP&f22=CP&f1=OP&f20=cf_status_thunderbird{{CENTRAL_VERSION}}&j13=OR&f8=cf_status_thunderbird{{CENTRAL_VERSION}}&f0=OP&o25=notequals&j19=OR&o11=notequals&o24=equals&f18=CP&columnlist=bug_severity%2Cpriority%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate%2Ccf_status_thunderbird21%2Ccf_status_thunderbird{{CENTRAL_VERSION}}&f15=CP&query_based_on=Tracking{{CENTRAL_VERSION}}%2B&f9=CP&j7=OR&v20=verified%20disabled&f4=OP&o23=anywordssubstr&query_format=advanced&v23=wontfix%20affected&n24=1&j1=OR&v17=disabled&f3=CP&f2=cf_tracking_thunderbird_esr{{CENTRAL_VERSION}}&f11=cf_status_thunderbird{{CENTRAL_VERSION}}&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&f5=cf_status_thunderbird{{CENTRAL_VERSION}}&f17=cf_status_thunderbird{{CENTRAL_VERSION}}&v8=fixed&v14=verified&f6=CP&f7=OP&o8=notequals&f16=OP&list_id=6873222 Earlier regressions, non-security, no resolved]
== Tracked Bugs ==

<bugzilla>
{
"f1" : "cf_tracking_thunderbird_esr{{CENTRAL_VERSION}}",
"o1" : "equals",
"v1" : "?",
"include_fields": "id, summary, whiteboard, status, resolution"
}
</bugzilla>

== [https://bugzilla.mozilla.org/buglist.cgi?o2=equals&f2=cf_tracking_thunderbird_esr{{CENTRAL_VERSION}}&v2=%3F Tracking Nominations] ==
<bugzilla>
{
"f1" : "cf_tracking_thunderbird_esr{{CENTRAL_VERSION}}",
"o1" : "equals",
"v1" : "?",
"include_fields": "id, summary, whiteboard, status, resolution"
}
</bugzilla>

[https://bugzilla.mozilla.org/buglist.cgi?f1=cf_tracking_thunderbird_esr{{CENTRAL_VERSION}}&o1=equals&o2=equals&query_format=advanced&f2=bug_group&v1=%3F&v2=core-security Security tracking noms]

User:Bkerensa/tb-nightly-queries

2015-01-30T20:38:04Z

Bkerensa:

= <center>TB Nightly ({{CENTRAL_VERSION}})</center> =

== Queries ==
* [https://bugzilla.mozilla.org/buglist.cgi?o5=notequals&list_id=6873273&v11=unaffected&j10=OR&o14=notequals&f13=OP&o2=equals&j16=OR&v5=wontfix&f12=CP&j4=OR&f14=cf_status_thunderbird_esr{{CENTRAL_VERSION}}&o17=notequals&o20=notequals&v2=%2B&f21=CP&known_name=Tracking{{CENTRAL_VERSION}}%2B&f10=OP&f19=OP&f{{CENTRAL_VERSION}}=CP&f1=OP&f20=cf_status_thunderbird{{CENTRAL_VERSION}}&j13=OR&f8=cf_status_thunderbird{{CENTRAL_VERSION}}&f0=OP&j19=OR&o11=notequals&f18=CP&columnlist=bug_severity%2Cpriority%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate%2Ccf_tracking_thunderbird17%2Ccf_tracking_thunderbird18%2Ccf_status_thunderbird17%2Ccf_status_thunderbird18&f15=CP&query_based_on=Tracking{{CENTRAL_VERSION}}%2B&f9=CP&j7=OR&v20=verified%20disabled&f4=OP&query_format=advanced&j1=OR&v17=disabled&f3=CP&f2=cf_tracking_thunderbird{{CENTRAL_VERSION}}&f11=cf_status_thunderbird{{CENTRAL_VERSION}}&f5=cf_status_thunderbird{{CENTRAL_VERSION}}&f17=cf_status_thunderbird{{CENTRAL_VERSION}}&v8=fixed&v14=verified&f6=CP&f7=OP&o8=notequals&f16=OP Full unresolved tracking list]
** [https://bugzilla.mozilla.org/buglist.cgi?o5=notequals&list_id=6873481&v11=unaffected&j10=OR&o14=notequals&f13=OP&o2=equals&j16=OR&v5=wontfix&f12=CP&j4=OR&f14=cf_status_thunderbird{{CENTRAL_VERSION}}&o17=notequals&o20=notequals&v2=%2B&f21=CP&known_name=Tracking{{CENTRAL_VERSION}}%2B&f10=OP&f19=OP&f22=CP&f1=OP&f20=cf_status_thunderbird{{CENTRAL_VERSION}}&j13=OR&f8=cf_status_thunderbird{{CENTRAL_VERSION}}&f0=OP&j19=OR&o11=notequals&f18=CP&f15=CP&query_based_on=Tracking{{CENTRAL_VERSION}}%2B&f9=CP&j7=OR&v20=verified%20disabled&f4=OP&query_format=advanced&j1=OR&v17=disabled&f3=CP&f2=cf_tracking_thunderbird{{CENTRAL_VERSION}}&f11=cf_status_thunderbird{{CENTRAL_VERSION}}&bug_status=RESOLVED&bug_status=VERIFIED&f5=cf_status_thunderbird{{CENTRAL_VERSION}}&f17=cf_status_thunderbird{{CENTRAL_VERSION}}&v8=fixed&v14=verified&f6=CP&f7=OP&o8=notequals&f16=OP Resolved/Fixed]
** [https://bugzilla.mozilla.org/buglist.cgi?o5=notequals&v11=unaffected&j10=OR&o14=notequals&f13=OP&o2=equals&j16=OR&f23=cf_status_thunderbird{{AURORA_VERSION}}&v5=wontfix&f12=CP&v24=affected&j4=OR&f14=cf_status_thunderbird{{CENTRAL_VERSION}}&o17=notequals&o20=notequals&f24=cf_status_thunderbird{{AURORA_VERSION}}&v2=%2B&f21=CP&known_name=Tracking{{CENTRAL_VERSION}}%2B&f10=OP&f19=OP&f22=CP&f1=OP&f20=cf_status_thunderbird{{CENTRAL_VERSION}}&j13=OR&f8=cf_status_thunderbird{{CENTRAL_VERSION}}&f0=OP&j19=OR&o11=notequals&o24=notequals&f18=CP&columnlist=bug_severity%2Cpriority%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate%2Ccf_status_thunderbird{{AURORA_VERSION}}%2Ccf_status_thunderbird{{CENTRAL_VERSION}}&f15=CP&query_based_on=Tracking{{CENTRAL_VERSION}}%2B&f9=CP&j7=OR&v20=verified%20disabled&f4=OP&o23=notequals&query_format=advanced&v23=wontfix&j1=OR&v17=disabled&f3=CP&f2=cf_tracking_thunderbird{{CENTRAL_VERSION}}&f11=cf_status_thunderbird{{CENTRAL_VERSION}}&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&f5=cf_status_thunderbird{{CENTRAL_VERSION}}&f17=cf_status_thunderbird{{CENTRAL_VERSION}}&v8=fixed&v14=verified&f6=CP&f7=OP&o8=notequals&f16=OP&list_id=6873202 Nightly regressions, all security, no resolved]
** [https://bugzilla.mozilla.org/buglist.cgi?o5=notequals&v11=unaffected&j10=OR&v25=unaffected&o14=notequals&f13=OP&o2=equals&j16=OR&f23=cf_status_thunderbird21&v5=wontfix&f12=CP&f25=cf_status_thunderbird21&v24=core-security&j4=OR&f14=cf_status_thunderbird{{CENTRAL_VERSION}}&o17=notequals&o20=notequals&f24=bug_group&v2=%2B&f21=CP&known_name=Tracking{{CENTRAL_VERSION}}%2B&f10=OP&f19=OP&f22=CP&f1=OP&f20=cf_status_thunderbird{{CENTRAL_VERSION}}&j13=OR&f8=cf_status_thunderbird{{CENTRAL_VERSION}}&f0=OP&o25=notequals&j19=OR&o11=notequals&o24=equals&f18=CP&columnlist=bug_severity%2Cpriority%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate%2Ccf_status_thunderbird21%2Ccf_status_thunderbird{{CENTRAL_VERSION}}&f15=CP&query_based_on=Tracking{{CENTRAL_VERSION}}%2B&f9=CP&j7=OR&v20=verified%20disabled&f4=OP&o23=anywordssubstr&query_format=advanced&v23=wontfix%20affected&n24=1&j1=OR&v17=disabled&f3=CP&f2=cf_tracking_thunderbird{{CENTRAL_VERSION}}&f11=cf_status_thunderbird{{CENTRAL_VERSION}}&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&f5=cf_status_thunderbird{{CENTRAL_VERSION}}&f17=cf_status_thunderbird{{CENTRAL_VERSION}}&v8=fixed&v14=verified&f6=CP&f7=OP&o8=notequals&f16=OP&list_id=6873222 Earlier regressions, non-security, no resolved]
== Tracked Bugs ==

<bugzilla>
{
"f1" : "cf_tracking_thunderbird{{CENTRAL_VERSION}}",
"o1" : "equals",
"v1" : "?",
"include_fields": "id, summary, whiteboard, status, resolution"
}
</bugzilla>

== [https://bugzilla.mozilla.org/buglist.cgi?o2=equals&f2=cf_tracking_thunderbird{{CENTRAL_VERSION}}&v2=%3F Tracking Nominations] ==
<bugzilla>
{
"f1" : "cf_tracking_thunderbird{{CENTRAL_VERSION}}",
"o1" : "equals",
"v1" : "?",
"include_fields": "id, summary, whiteboard, status, resolution"
}
</bugzilla>

[https://bugzilla.mozilla.org/buglist.cgi?f1=cf_tracking_thunderbird{{CENTRAL_VERSION}}&o1=equals&o2=equals&query_format=advanced&f2=bug_group&v1=%3F&v2=core-security Security tracking noms]

User:Bkerensa/tb-nightly-queries

2015-01-30T20:34:56Z

= <center>TB Nightly ({{CENTRAL_VERSION}})</center> =

== Queries ==
* [https://bugzilla.mozilla.org/buglist.cgi?o5=notequals&list_id=6873273&v11=unaffected&j10=OR&o14=notequals&f13=OP&o2=equals&j16=OR&v5=wontfix&f12=CP&j4=OR&f14=cf_status_thunderbird{{CENTRAL_VERSION}}&o17=notequals&o20=notequals&v2=%2B&f21=CP&known_name=Tracking{{CENTRAL_VERSION}}%2B&f10=OP&f19=OP&f{{CENTRAL_VERSION}}=CP&f1=OP&f20=cf_status_thunderbird{{CENTRAL_VERSION}}&j13=OR&f8=cf_status_thunderbird{{CENTRAL_VERSION}}&f0=OP&j19=OR&o11=notequals&f18=CP&columnlist=bug_severity%2Cpriority%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate%2Ccf_tracking_thunderbird17%2Ccf_tracking_thunderbird18%2Ccf_status_thunderbird17%2Ccf_status_thunderbird18&f15=CP&query_based_on=Tracking{{CENTRAL_VERSION}}%2B&f9=CP&j7=OR&v20=verified%20disabled&f4=OP&query_format=advanced&j1=OR&v17=disabled&f3=CP&f2=cf_tracking_thunderbird{{CENTRAL_VERSION}}&f11=cf_status_thunderbird{{CENTRAL_VERSION}}&f5=cf_status_thunderbird{{CENTRAL_VERSION}}&f17=cf_status_thunderbird{{CENTRAL_VERSION}}&v8=fixed&v14=verified&f6=CP&f7=OP&o8=notequals&f16=OP Full unresolved tracking list]
** [https://bugzilla.mozilla.org/buglist.cgi?o5=notequals&list_id=6873481&v11=unaffected&j10=OR&o14=notequals&f13=OP&o2=equals&j16=OR&v5=wontfix&f12=CP&j4=OR&f14=cf_status_thunderbird{{CENTRAL_VERSION}}&o17=notequals&o20=notequals&v2=%2B&f21=CP&known_name=Tracking{{CENTRAL_VERSION}}%2B&f10=OP&f19=OP&f22=CP&f1=OP&f20=cf_status_thunderbird{{CENTRAL_VERSION}}&j13=OR&f8=cf_status_thunderbird{{CENTRAL_VERSION}}&f0=OP&j19=OR&o11=notequals&f18=CP&f15=CP&query_based_on=Tracking{{CENTRAL_VERSION}}%2B&f9=CP&j7=OR&v20=verified%20disabled&f4=OP&query_format=advanced&j1=OR&v17=disabled&f3=CP&f2=cf_tracking_thunderbird{{CENTRAL_VERSION}}&f11=cf_status_thunderbird{{CENTRAL_VERSION}}&bug_status=RESOLVED&bug_status=VERIFIED&f5=cf_status_thunderbird{{CENTRAL_VERSION}}&f17=cf_status_thunderbird{{CENTRAL_VERSION}}&v8=fixed&v14=verified&f6=CP&f7=OP&o8=notequals&f16=OP Resolved/Fixed]
** [https://bugzilla.mozilla.org/buglist.cgi?o5=notequals&v11=unaffected&j10=OR&o14=notequals&f13=OP&o2=equals&j16=OR&f23=cf_status_thunderbird{{AURORA_VERSION}}&v5=wontfix&f12=CP&v24=affected&j4=OR&f14=cf_status_thunderbird{{CENTRAL_VERSION}}&o17=notequals&o20=notequals&f24=cf_status_thunderbird{{AURORA_VERSION}}&v2=%2B&f21=CP&known_name=Tracking{{CENTRAL_VERSION}}%2B&f10=OP&f19=OP&f22=CP&f1=OP&f20=cf_status_thunderbird{{CENTRAL_VERSION}}&j13=OR&f8=cf_status_thunderbird{{CENTRAL_VERSION}}&f0=OP&j19=OR&o11=notequals&o24=notequals&f18=CP&columnlist=bug_severity%2Cpriority%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate%2Ccf_status_thunderbird{{AURORA_VERSION}}%2Ccf_status_thunderbird{{CENTRAL_VERSION}}&f15=CP&query_based_on=Tracking{{CENTRAL_VERSION}}%2B&f9=CP&j7=OR&v20=verified%20disabled&f4=OP&o23=notequals&query_format=advanced&v23=wontfix&j1=OR&v17=disabled&f3=CP&f2=cf_tracking_thunderbird{{CENTRAL_VERSION}}&f11=cf_status_thunderbird{{CENTRAL_VERSION}}&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&f5=cf_status_thunderbird{{CENTRAL_VERSION}}&f17=cf_status_thunderbird{{CENTRAL_VERSION}}&v8=fixed&v14=verified&f6=CP&f7=OP&o8=notequals&f16=OP&list_id=6873202 Nightly regressions, all security, no resolved]
** [https://bugzilla.mozilla.org/buglist.cgi?o5=notequals&v11=unaffected&j10=OR&v25=unaffected&o14=notequals&f13=OP&o2=equals&j16=OR&f23=cf_status_thunderbird21&v5=wontfix&f12=CP&f25=cf_status_thunderbird21&v24=core-security&j4=OR&f14=cf_status_thunderbird{{CENTRAL_VERSION}}&o17=notequals&o20=notequals&f24=bug_group&v2=%2B&f21=CP&known_name=Tracking{{CENTRAL_VERSION}}%2B&f10=OP&f19=OP&f22=CP&f1=OP&f20=cf_status_thunderbird{{CENTRAL_VERSION}}&j13=OR&f8=cf_status_thunderbird{{CENTRAL_VERSION}}&f0=OP&o25=notequals&j19=OR&o11=notequals&o24=equals&f18=CP&columnlist=bug_severity%2Cpriority%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate%2Ccf_status_thunderbird21%2Ccf_status_thunderbird{{CENTRAL_VERSION}}&f15=CP&query_based_on=Tracking{{CENTRAL_VERSION}}%2B&f9=CP&j7=OR&v20=verified%20disabled&f4=OP&o23=anywordssubstr&query_format=advanced&v23=wontfix%20affected&n24=1&j1=OR&v17=disabled&f3=CP&f2=cf_tracking_thunderbird{{CENTRAL_VERSION}}&f11=cf_status_thunderbird{{CENTRAL_VERSION}}&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&f5=cf_status_thunderbird{{CENTRAL_VERSION}}&f17=cf_status_thunderbird{{CENTRAL_VERSION}}&v8=fixed&v14=verified&f6=CP&f7=OP&o8=notequals&f16=OP&list_id=6873222 Earlier regressions, non-security, no resolved]
== Tracked Bugs ==

<bugzilla>
{
"f1" : "cf_tracking_thunderbird{{CENTRAL_VERSION}}",
"o1" : "equals",
"v1" : "?",
"include_fields": "id, summary, whiteboard, status, resolution"
}
</bugzilla>

== [https://bugzilla.mozilla.org/buglist.cgi?o2=equals&f2=cf_tracking_thunderbird{{CENTRAL_VERSION}}&v2=%3F Tracking Nominations] ==
<bugzilla>
{
"f1" : "cf_tracking_thunderbird{{CENTRAL_VERSION}}",
"o1" : "equals",
"v1" : "?",
"include_fields": "id, summary, whiteboard, status, resolution"
}
</bugzilla>

[https://bugzilla.mozilla.org/buglist.cgi?f1=cf_tracking_thunderbird{{CENTRAL_VERSION}}&o1=equals&o2=equals&query_format=advanced&f2=bug_group&v1=%3F&v2=core-security Security tracking noms]

Template:Incomplete

2015-01-16T06:05:45Z

Bkerensa: Created page with "[Incomplete] {{{1}}}"

[Incomplete] {{{1}}}

Template:In Progress

2015-01-16T06:03:31Z

Bkerensa: Created page with "[DONE] {{{1}}}"

[DONE] {{{1}}}

Release Management/Goals/2015Q1

2015-01-16T06:02:08Z

Bkerensa:

= Release Management Q1 2015 Goals =
<platform> denotes goals that are listed on the [[Platform/2014-Q4-Goals#Release_Management|platform Q4 goals list]]
== Release Management General ==
; Release Quality - Improve automation / reduce risk of manual errors
* [Sylvestre] Add capability to release notes backend (nucleus) to upload an image/video. {{bug|1117783}}, {{bug|1117786}} and {{bug|1117790}}
* [Sylvestre] Ship-it: Automatically generate partials based on current release ADI
* [Sylvestre] Ship-it: Automatically generate product details
* [Lukas] Nucleus: {{bug|1119556}} add links to staging/production notes in release edit page

; Release Quality - Find issues earlier
* [all] get assignees on bugs earlier in the cycle - ideally when bug is marked as tracking (bonus if this was in the dashboard)
* [Lawrence] Improve pre-release data quality for graphics
* [Lawrence] Improve pre-release data quality for stability
* [Lawrence] Create checkIID hook to catch required UUID bumps

; Communication
* [Lukas] Get the nag emails running again for Desktop/Mobile/ESR bugs
* [Lukas] RelmanDash v0.2: Get a dashboard up in Moz Spaces with info on where we're at in the release, and visibility into what issues there are with each channel
* [Lawrence] Publish updated documentation about release schedule and process
* [Lawrence] Make team wiki easier to find information for devs and relman
** Improve documentation about how to manage a release
** Ensure documentation for plug-in blocklist, add-on hotfix, and gfx blocklist is up-to-date
** Create release checklists for Aurora, Beta, Release, point release, and chemspill

; Release Strategy
* [Lawrence] Create release strategy document summarizing plans for improvements to measurement, process, issue mitigation, turnaround time, and automation.
* [Lukas/Sylvestre] Enable updates faster: starting with 35.0 and then again with 36.0 we'll enable updates on the Friday of release week and see how that goes - collect info, bring to post-mortem. Before 37.0 we should assess if this is going well making it the new normal
* [Lawrence] Create a Firefox distribution plan

; Expand contributor involvement
* [Lukas] put out the call for, interview, and onboard at least one new contributor
* [Benjamin] help promote Lukas's blog post for new contributor

== Firefox Desktop/Mobile ==
* Manage and coordinate active Firefox and Firefox for Android releases
** {{done|}} [Lawrence] Firefox 34
** [Lukas] Firefox 35
** [Sylvestre] Firefox 36
** [Lawrence] Firefox 37
** [Lukas] Firefox 38
** [Sylvestre] Firefox 39

== Firefox ESR ==
** [Benjamin] Release ESR Proposal to Relman and other parties
** [Benjamin] Work with User Advocacy to produce new ESR survey
** [Benjamin] Work with stakeholders to implement ESR Proposal if approved
** [Benjamin] Do ESR Wiki Documentation Housekeeping
** {{done|}} [Benjamin] Get access to /lib/product-detail to update during release

== Special Projects ==

== Personal Development ==
* [Lawrence] Chair Slice the Ice charity hockey game and raise $160,000 for neonatal care.
* [Lukas] submit a talk to OSCON "How to onboard and embed a non-coding contributor in your team"
* [Sylvestre]
* [Benjamin] Continue reading two books on Django and write first Django app

Release Management/Goals/2015Q1

2015-01-16T06:00:01Z

Bkerensa:

= Release Management Q1 2015 Goals =
<platform> denotes goals that are listed on the [[Platform/2014-Q4-Goals#Release_Management|platform Q4 goals list]]
== Release Management General ==
; Release Quality - Improve automation / reduce risk of manual errors
* [Sylvestre] Add capability to release notes backend (nucleus) to upload an image/video. {{bug|1117783}}, {{bug|1117786}} and {{bug|1117790}}
* [Sylvestre] Ship-it: Automatically generate partials based on current release ADI
* [Sylvestre] Ship-it: Automatically generate product details
* [Lukas] Nucleus: {{bug|1119556}} add links to staging/production notes in release edit page

; Release Quality - Find issues earlier
* [all] get assignees on bugs earlier in the cycle - ideally when bug is marked as tracking (bonus if this was in the dashboard)
* [Lawrence] Improve pre-release data quality for graphics
* [Lawrence] Improve pre-release data quality for stability
* [Lawrence] Create checkIID hook to catch required UUID bumps

; Communication
* [Lukas] Get the nag emails running again for Desktop/Mobile/ESR bugs
* [Lukas] RelmanDash v0.2: Get a dashboard up in Moz Spaces with info on where we're at in the release, and visibility into what issues there are with each channel
* [Lawrence] Publish updated documentation about release schedule and process
* [Lawrence] Make team wiki easier to find information for devs and relman
** Improve documentation about how to manage a release
** Ensure documentation for plug-in blocklist, add-on hotfix, and gfx blocklist is up-to-date
** Create release checklists for Aurora, Beta, Release, point release, and chemspill

; Release Strategy
* [Lawrence] Create release strategy document summarizing plans for improvements to measurement, process, issue mitigation, turnaround time, and automation.
* [Lukas/Sylvestre] Enable updates faster: starting with 35.0 and then again with 36.0 we'll enable updates on the Friday of release week and see how that goes - collect info, bring to post-mortem. Before 37.0 we should assess if this is going well making it the new normal
* [Lawrence] Create a Firefox distribution plan

; Expand contributor involvement
* [Lukas] put out the call for, interview, and onboard at least one new contributor
* [Benjamin] help promote Lukas's blog post for new contributor

== Firefox Desktop/Mobile ==
* Manage and coordinate active Firefox and Firefox for Android releases
** {{done|}} [Lawrence] Firefox 34
** [Lukas] Firefox 35
** [Sylvestre] Firefox 36
** [Lawrence] Firefox 37
** [Lukas] Firefox 38
** [Sylvestre] Firefox 39

== Firefox ESR ==
** [Benjamin] Release ESR Proposal to Relman and other parties
** [Benjamin] Work with User Advocacy to produce new ESR survey
** [Benjamin] Work with stakeholders to implement ESR Proposal if approved
** [Benjamin] Do ESR Wiki Documentation Housekeeping

== Special Projects ==

== Personal Development ==
* [Lawrence] Chair Slice the Ice charity hockey game and raise $160,000 for neonatal care.
* [Lukas] submit a talk to OSCON "How to onboard and embed a non-coding contributor in your team"
* [Sylvestre]
* [Benjamin] Continue reading two books on Django and write first Django app

Template:ESR CURRENT DOT

2015-01-16T05:37:59Z

Bkerensa:

.4.0

MozillaGamers

2015-01-05T22:08:19Z

Bkerensa: Created page with "Mozilla Gamers is a sub-community of Mozillians who like to play games the idea behind the group is to create cohesion among Mozillians. == Links == # [http://steamcommunity..."

Mozilla Gamers is a sub-community of Mozillians who like to play games the idea behind the group is to create cohesion among Mozillians.

== Links ==

# [http://steamcommunity.com/groups/mozillians Mozilla Gamers on Steam]
# [https://www.facebook.com/groups/mozillagamers Mozilla Gamers on Facebook]

Template:ESR CURRENT DOT

2014-12-17T10:06:13Z

Bkerensa: Meh

.3.0