1 of 44

Strategic Plan

Participation, July 2016

DRAFT for discussion

2 of 44

These five documents are important context:

Mozilla Corporation Confidential - Internal Use Only

3 of 44

Participation Mission Statement

(updated 07/04/2016)

The Participation Team develops community leaders and contributors who will invent, shape and defend the internet, and activates them to supercharge Mozilla’s products and our movement.

We do this by:

Designing and implementing specific participation initiatives -- in partnership with teams around Mozilla -- that adapt and advance global best-practice on participation
Recruiting and investing in core contributors mobilizers/leaders, and developing diverse, local and global communities that make individual contribution more impactful
Delivering software/systems and practices that increase the impact of participation across Mozilla

Mozilla Confidential - Staff and NDA'd Mozillians Only

4 of 44

Sidebar: Open Innovation & Participation

In Q2, the Open Innovation and Participation teams merged under the CIO. This is some context about that, and implications for the org.

5 of 44

Merger With Innovation (updated 04/07/2016)

We seek to dramatically increase the number of people engaged in our work.
The Participation Team is building communities, tools and processes to enable distributed collaboration across the project.
Without many new products to activate around, there are fewer directed calls to participate in the Mozilla project.
The opportunity is to add participation much earlier into Mozilla’s ideation process, bringing more ideas and more diverse thinking into the project and creating more stakeholders in Mozilla.

Mozilla Confidential - Staff and NDA'd Mozillians Only

6 of 44

Open Innovation Mission Statement (updated 04/07/2016)

The Open Innovation Group serves everyone who wants to innovate across all areas of the Mozilla project by advancing our capabilities in open, distributed, collaborative innovation. We do this by adopting and adapting best practises at the management and operational levels, including by:

Providing tools, processes and information resources to innovators
Providing support to innovation projects throughout their lifecycle
Connecting the Mozilla project to aligned influencers, projects and communities
Directly managing initiatives with high potential that do not have existing sponsorship within the organization.

Mozilla Confidential - Staff and NDA'd Mozillians Only

7 of 44

Org Overview

(updated 04/07/2016)

For 2H 2016, the focus for integration is interaction amongst teams focused on open innovation. The overall structure of two groups (Participation and Open Innovation) remains. The rationale for this is to maximise for execution against needs defined in 1H 2016. The structure may be revisited in 2017.

The focus for integration is therefore “Collaborative Innovation”, prototyping new collaboration models.

This document focuses on the Participation strategy and plan.

Participation

Open Innovation

Products & Pipeline

Innovation

Capabilities

Collaborative Innovation

Participation Design

Communities & Leadership

Software

Creating and sustaining a product pipeline.

Improving the culture of innovation.

Connecting Mozilla initiatives to new, valuable allies

Designing Participation programs to Mozilla objectives

Build capabilities and activate�core contributor mobilizers/leaders & communities

Design and build tools to support a radically participative organisation

Operations

Planning overhead, Overall program mgt, Comms

Mozilla Confidential - Staff and NDA'd Mozillians Only

8 of 44

Participation �2H 2016 Strategy

9 of 44

3 Year Vision (updated 24/06/2016)

By 2019, participation of our core contributors will bring unquestionable value to all of Mozilla’s core strategies.� �We aim to have participation supercharge both our products and our movement. It will be a force for both innovation and execution for our products. It will become our most important strategy for building momentum behind our issues agenda.� Participation Team Mission: The Participation Team develops community leaders and contributors who will invent, shape and defend the internet, and activates them to supercharge Mozilla’s products and our movement. We design and implement specific participation initiatives, develop and activate core contributor mobilizers/leaders and communities, deliver software/systems and practices that increase the impact of participation across Mozilla



Key measurements: Impact on issues agenda - issues/developer sentiment, deep relationships Impact of contributions - against prioritized needs Skills of leaders/core contributors - growth in skills against key needs (existing people and new) Community capabilities - ability of communities to take action on key needs (size, health, resources)

Prior update : 01 / 01 / 2016
Significant changes since last update: Sharpened 2019 focus on core contributors and value they bring. Added key measurements.

Mozilla Corporation Confidential - Internal Use Only

10 of 44

A few important guiding insights and hypotheses for 2H...

Mozilla Corporation Confidential - Internal Use Only

11 of 44

1) Substantial change and ambiguity in Mozilla

12 of 44

1) Substantial change and ambiguity in Mozilla

The products many of our people were rallying around are gone. For the foreseeable future, no new products (other than Firefox) will be stable.

Hypothesis 1: �We can and should connect people with Mozilla and our Mission/Issues Agenda

13 of 44

2) Traditional areas of contribution may be different or less relevant/impactful

14 of 44

2) Traditional areas of contribution may be different or less relevant/impactful

Hypothesis 2:

We can start honest conversations about what activities do and don’t have impact and why, and aim/re-direct volunteer energy where it is valuable.

?

Cost of product and technical translation is dropping to zero … what does this mean

?

QC increasingly automated or inexpensive … what does this mean

?

Product acquisition happens through paid online marketing … what does this mean

15 of 44

3) There is much more “competition” for people’s time and attention

16 of 44

3) There is much more “competition” for people’s time and attention

Hypothesis 3:

We can “compete” if we focus on building participation programs, tools and resources that are truly excellent → deliver value for Mozilla’s mission and to our core contributors.

17 of 44

Two more hypotheses that will guide our efforts...

Hypothesis 4:

We can and need to move from a primary individual contributor lens/program design → to collective/team contribution in order to have substantial impact on our mission.

Hypothesis 5:

The areas we need to develop (and experiment with) ‘leading edge participation’ capabilities are:

Open Source contribution
Mobilizing -- online + offline
Open innovation

18 of 44

Strategic objectives and programs �for 2H 2016

Mozilla Corporation Confidential - Internal Use Only

19 of 44

Build Core Strength

Extend �Mozilla’s �Reach

Of our issues agenda, to developers, and of our products

Grow Our Influence

Help�Mozilla�Innovate

By supercharging new products/tech, and bringing new ideas and people

Prototype the Future

Strategic objectives

(revisited)

Build Capabilities of �Core Contributor Mobilizers & Communities

Through skill-building, community building programs, and software/systems and participation practices

Mozilla Corporation Confidential - Internal Use Only

20 of 44

Emerging strategy on people

Established Leaders:

Shape broad strategy + influence in the world

Super-mobilizers:

Build and operate participation/ mobilization programs

Mobilizers:

Organize and activate contributors at scale + drive excellence

Core Contributors:

Deliver value/contributions directly to Mozilla mission and strategy

Today = ~a few → grow to dozens

Tactic: Find a connect with Mozilla on specific topics/functions

Today = ~25 mostly staff → grow to dozens

Tactic: Continue investing in staff skills and keep our eye out for talent

Today = ~200 → grow to 1,000+

Tactic: Reps Next + Leadership curriculum + Gatherings + Online skill-building + Campaigns to run

Today = ~thousands → grow to tens of thousands

Tactic: Invest in Mobilizers + Activity campaigns/well designed-programs of focus + Test programs to attract superstar individual contributors

Mozilla Corporation Confidential - Internal Use Only

21 of 44

Emerging strategy on people

Embedded hypothesis: Focusing on mobilizers (vs. innovation/problem solving/strategy) is where we will get the maximum impact for our efforts.

Established Leaders:

Shape broad strategy + influence in the world

Super-mobilizers:

Build and operate participation/ mobilization strategies and programs

Mobilizers:

Organize and activate contributors at scale + drive excellence

Core Contributors:

Deliver value/contributions directly to Mozilla mission and strategy

Today = ~a few → grow to dozens

Tactic: Find a connect with Mozilla on specific topics/functions

Today = ~25 mostly staff → grow to dozens

Tactic: Continue investing in staff skills and keep our eye out for talent

Today = ~200 → grow to 1,000+

Tactic: Reps Next + Leadership curriculum + Gatherings + Online skill-building + Campaigns to run

Today = ~thousands → grow to tens of thousands

Tactic: Invest in Mobilizers + Activity campaigns/well designed-programs of focus + Test programs to attract superstar individual contributors

Focus here!

Mozilla Corporation Confidential - Internal Use Only

22 of 44

3 methods for growing mobilizer capacity

1) Recruit junior and grow into Mobilizers

→ Campus program is key

2) Upskill existing mobilizers

→ Gatherings + Skill-building program is key

3) Recruit new more experienced people

→ Need a strategy and value proposition here

Mozilla Corporation Confidential - Internal Use Only

23 of 44

Before going into program details...

Different programs, different emphasis

Build and experiment

Production

Bottom line:

Learning/hypothesis validation + clarify future

Bottom line:

Deliver results

Mozilla Corporation Confidential - Internal Use Only

24 of 44

Strategic Roadmap (updated 12/07/2016)

Objective	Q3 2016	Q4 2016	Q1 2017	Q2 2017
Build Capabilities








Extend Mozilla’s Reach






Help Mozilla Innovate
Help Mozilla Innovate

Campus program - restructure

Reps program evolution - implementation

Campus program scaling

Reps program - scaling

Q3 Activity Campaign

1H Activity Campaign

MakerParty - plan

Experiment/design new tech contribution areas -- Servo/Quantum, Software economics, Tor, etc

Bring innovators/ideas to Mozilla - pilot experiments/strategy

Skill-building - Deliver regional gatherings

Skill-building - Deliver foundational resources

Skill-building - Experiment with online skill-building

Skill-building - Deliver global gatherings

Skill-building - Deliver online skill- building program

New tech contribution into production

Mozilla ID - IAM/Auth - delivery

Supercharge CD projects + events - further experiments incl. User-Driven Innovation pilot

Contribution to CD projects - production

MakerParty - deliver

Bring innovators/ideas to Mozilla - planning

Bring innovators/ideas to Mozilla - production

Metrics - beta implementation/learning

Volunteer Mgmt Systems/Collab Systems - Research & trials

Volunteer Mgmt Systems/Collab Systems - Actionable vision

Volunteer Mgmt Systems/Collab Systems - Prioritized implementation

Metrics - implementation post-IAM

Mozilla ID - Service/UI enhancements

Build and experiment

Production

Mozilla Confidential - Staff and NDA'd Mozillians Only

25 of 44

Participation Objectives - production (updated 12/07/2016)

Objective	2H 2016 Programs	2H 2016 Key Results
Build Capabilities of �Core Contributor Mobilizers & Communities: Through skill-building, community building programs, and software/systems and participation practices	Skill building (Mobilizer gatherings & Online education & Foundational resources) Participation systems/software	Clarity on skills we need for our mobilizers Delivered regional gatherings for making that investment in 275 people IAM implementation/integration with Mozillians.org in partnership with IT New auth implementation on Participation sites to replace Persona
Extend Mozilla’s Reach: Of our issues agenda, to developers, and of our products	Q3 activity campaign Q4 activity campaign = MakerParty	Activity campaign delivers against ambitious KPIs on: a) privacy and security behaviours, b) developer engagement, c) training in Rust, d) Test Pilot MAU/ADUs Maker Party hits all its ambitious KPIs to move the issue of copyright in the EU and to start a conversation on copyright/creativity in our countries of focus

Mozilla Corporation Confidential - Internal Use Only

26 of 44

Participation Objectives - build/experiment (updated 12/07/2016)

Objective	2H 2016 Programs	2H 2016 Key Results
Build Capabilities of �Core Contributor Mobilizers & Communities: Through skill-building, community building programs, and software/systems and participation practices	Reps program evolution (RepsNext) Campus program restructure Participation systems/software	KR here for RepsNext Active Mozilla student groups on 500 campuses Actionable vision for volunteer management and collaboration systems Every part of the organization can make data-driven decisions on participation
Extend Mozilla’s Reach: Of our issues agenda, to developers, and of our products	Experiment/design new tech contribution areas -- Servo/Quantum, Software economics, Tor, etc	KR here once conversations with CTO/Platform have happened Actionable vision for where we’ll invest in 2017
Help Mozilla Innovate: By supercharging new products/tech, and bringing new ideas and people	Supercharge Connected Devices projects and IoT events Bring innovators and new ideas to Mozilla	Pilot programs delivered that generate lessons for future of CD project participation Actionable vision (validated through experimentation) for bringing innovators/ideas to Mozilla Clear strategy for community spaces moving forward

Mozilla Corporation Confidential - Internal Use Only

27 of 44

2016 Shelved / Cancelled programs

Program	Reasoning
Inviting people to participate/contribute through Contribute page on Mozilla.org	Need to sort out ownership of /contribute section in order to take an agile approach to development Limited product management and developer resources → prioritized elsewhere Need participation program maturity → places to direct people to contribute


Expanding community-run community spaces	On hold until we have a shared strategy on this … continue support/focusing of existing spaces

Mozilla Corporation Confidential - Internal Use Only

28 of 44

6 Month Vision

By end 2016, we’ve delivered:

Mozilla Confidential - Staff and NDA'd Mozillians Only

29 of 44

Programs

These are high-level descriptions of the programs including some details on 2H 2016 work

30 of 44

Introducing the role of Product/Program Owner...

Works with George to establish and then own Vision/strategy, Objectives and Rough roadmap
Responsible for working with team members and other product owners to prioritize work/initiatives and KRs
Serves as the “customer” proxy
Drives iterations in work
Uses KRs and other means to set quality standards on any activity or project

Mozilla Corporation Confidential - Internal Use Only

31 of 44

Skill Building (updated 18/07/2016)

Product Owner: Ruben → NEW HIRE (Head of Community Leadership and Learning) Team: Guillermo, Francisco

Objective
A focus set of relevant training and learning opportunities for mobilizers are systematized and they regularly access these opportunities to be more effective in their contributions and as a result providing more impact to Mozilla’s main initiatives.


Key Result
A leadership toolkit focused on key skills for mobilizers and training plan is ready. 80 core mobilizers took at least Xh of coaching training and start at least 2 coaching relationships. 5 Community Gatherings are delivered including a focus on Mozilla strategy and key impact areas 80+ core mobilizers access the leadership training and put it into practice. Our mobilizers who took the leadership training report being more effective to support Mozilla by scoring 40 on the Net Promoter Score by the end of Q4.
Activities / Projects
Leadership toolkit Coaching framework Community Gatherings



Dependencies / Key Stakeholders⁽³⁾
Reps program

Prior update : XX / XX / XXXX
Significant changes since last update: _____________________
List the organisations, other than your own, with whom you’ll need significant collaboration, support or exchange

Mozilla Corporation Confidential - Internal Use Only

32 of 44

Reps Program and Communities (updated 18/JUL/2016)

Product Owner: Ruben Team: Konstantina, Guillermo, Francisco

Objective
Reps is the program for most core volunteers where many communities feel their voice represented and influencing the organization, and where mozillians join to be more aligned, grow their skills and be more impactful in mobilizing others.


Key Result
80 mentors and new mentors took at least Xh of coaching training and start at least 2 coaching relationships. 80% of the communities we act on report better shape/effectiveness thanks to the regional coaches by seeing alignment in the communities’ activities 160+ core mozillians coached by new mentors contribute to at least one focus activity.	At least 50% of the communities Regional Coaches work with report feeling represented by the Reps program 150+ Reps get involved in the Activity Campaign, participating in at least one activity and/or mobilizing others. The Review Team is working effectively by decreasing the budget review time by 30% 80% of the Reps are reporting being satisfied with the new reviewing budget system
Activities / Projects
RepsNext: New mentors approach (coaching) Reps regional coaches Participation leaders initial merge into Reps	Reps support to Activity Campaign Conflict resolution framework



Dependencies / Key Stakeholders⁽³⁾
NDA process Activity Campaign	Leadership toolkit Coaching framework

Mozilla Corporation Confidential - Internal Use Only

33 of 44

Campus Program Restructure (updated XX/XX/XXXX)

Product Owner: Lucy

Objective
The participation team has successfully launched an exciting new campus program that is connecting students all around the world to new levels of impact, new skills, and which is gaining a reputation as an excellent, competitive student program on campuses.


Key Result
200 campus clubs active 100 are have sustainable club leadership structures (exec board, leadership, contingency plans) 50 regional coordinators are submitting regular bi-weekly reports 200 club leaders go through an onboarding training about open-source, club set-up, and Mozilla There is a clearly defined process for the creation of a new club
Activities / Projects
1) Invested contributors (FSA & Campus Campaign) transition/change management to clubs 2) Develop Club materials and processes 3) Clubs support on campaigns (Maker Party)



Dependencies / Key Stakeholders⁽³⁾
Mofo Clubs - partner on branding, resources, messaging Dependent on resources to design a registration process, website, logo/brand and landing page Maker Party - clear activities for students to run Advocacy - direction for activities

Prior update : XX / XX / XXXX
Significant changes since last update: ____________________
List the organisations, other than your own, with whom you’ll need significant collaboration, support or exchange

Mozilla Corporation Confidential - Internal Use Only

34 of 44

Participation Systems (updated 19/JUL/2016)

Product Owner: The double He(lix) - Hermina & Henrik

Objective
O1: Lay foundations for increased Mozilla accessibility O2: Provide excellent fit-for-purpose Participation infrastructure to all Mozillians O3: Create a shared vision for evolution and delivery of Participation Systems


Key Result
O1KR1: A solution to provide identity and access management services for all Mozillians O2KR1: 80% of Community websites and three Participation properties are consolidated on P11N AWS account O3KR1: An actionable vision for Mozilla collaboration and volunteer management systems
Activities / Projects
Mozilla IAM Community websites migration Participation Systems research, product strategy and business analysis



Dependencies / Key Stakeholders⁽³⁾
Mozilla’s IT organization to share workload for IAM delivery Sourcing of Participation talent for infrastructure (DevOps) and product discovery/delivery

Team:

P11N Software: Pierros, Nikos, Tasos, Nemo, Yousef, +1 Frontend Dev
PMs: Arielle, Lyre, +1 PM, +1 UX/UI, +1 Researcher

Mozilla Corporation Confidential - Internal Use Only

35 of 44

Q3 Activity Campaign (updated 19/JUL/2016)

Product Owner: Brian

Objective
Mozillians around the world have multiple new and easily discoverable ways to contribute to Mozilla. These rallying points will provide value to them, and add value to Mozilla by contribution to organizational priorities and goals. Activities will be rolled out over time in Q3, with the aim of increasing engagement as it progresses.


Key Result
- Overall 1: 10 key activities are spread over 4 key buckets - Overall 2: 5000 unique contributions to the campaign - Overall 3: 1000 unique people mobilized	- Privacy 1: - Privacy 2:
- Dev Engage 1: - Dev Engage 2:	- TBD
Activities / Projects
- Activity 1: - Activity 2: - Activity 3:	- Campaign 1: Weekly internal and external (Discourse) progress checkins - Campaign 2: Tracking: interactions on web site and per activity metrics - Campaign 3:
Dependencies / Key Stakeholders
Developer Marketing Team - content + relationship tracking tool/CRM integration Key engineering teams in the org (e10s, webcompat) - Input to and co-design of activities to meet real needs Rust Community - Supplement existing community activities, make a better onboarding story, increase diversity

Mozilla Corporation Confidential - Internal Use Only

36 of 44

Maker Party (updated XX/XX/XXXX)

Product Owner: Lucy

Objective
Maker Party mobilizes Mozilla communities in EU and globally to take action on copyright and creativity, and have started to learn about Mozilla's issues agenda and Open Innovation specifically.


Key Result
Clear on-the-ground field organizing models moving forward after Maker Party, how they relate to one another, how they are supported/owned and common resources they employ
Activities / Projects
1) Maker Party planning and support 2) Organizing model learning and synthesis



Dependencies / Key Stakeholders⁽³⁾
Reps Council - commit to engaging Reps in Maker Party and create a joint plan for rolling this out to Reps Hive Leads - are willing to work together to plan a global kick-off event Regional Community Leads - come together to roll out Maker Party in their local communities Maker Party organizers - creation of Maker party promotional materials, clear resources about how to get involved, clear vision for community involvement.

Mozilla Corporation Confidential - Internal Use Only

37 of 44

Bring innovators and new ideas to Mozilla (updated XX/XX/XXXX)

Product Owner: Rosana

Objective



Key Result

Activities / Projects




Dependencies / Key Stakeholders⁽³⁾

Prior update : XX / XX / XXXX
Significant changes since last update: _____________________
List the organisations, other than your own, with whom you’ll need significant collaboration, support or exchange

Mozilla Corporation Confidential - Internal Use Only

38 of 44

Supercharge CD Projects and IoT Events (updated XX/XX/XXXX)

Product Owner: Natalia or Michael (TBD)

Objective



Key Result

Activities / Projects




Dependencies / Key Stakeholders⁽³⁾

Prior update : XX / XX / XXXX
Significant changes since last update: _____________________
List the organisations, other than your own, with whom you’ll need significant collaboration, support or exchange

Mozilla Corporation Confidential - Internal Use Only

39 of 44

Experiment/design new tech contribution (updated XX/XX/XXXX)

Product Owner: Don Marti

Objective



Key Result

Activities / Projects




Dependencies / Key Stakeholders⁽³⁾

Prior update : XX / XX / XXXX
Significant changes since last update: _____________________
List the organisations, other than your own, with whom you’ll need significant collaboration, support or exchange

Mozilla Corporation Confidential - Internal Use Only

40 of 44

<Program Title>(updated XX/XX/XXXX)

Objective



Key Result

Activities / Projects




Dependencies / Key Stakeholders⁽³⁾

Strategic Planning

Can use any format that speaks to program Name, objective, key result of program, description & critical dependencies with teams other than your own. One slide for each strategic program (initiative).

Purpose:

Share with NDA Mozillian the Leadership level view of planned programs in your organization

Updated : Quarterly (or monthly if desired)

Horizon : 3-6 months

Altitude : Actionable for organization leaders (SCVP & Organization leadership teams)

Basis : Agile Planning Model, Product Roadmap Template

Recommended Owner : Product or Program Owners

Prior update : XX / XX / XXXX
Significant changes since last update: _____________________
List the organisations, other than your own, with whom you’ll need significant collaboration, support or exchange

Mozilla Corporation Confidential - Internal Use Only

41 of 44

Org Structure

42 of 44

Org Overview

(updated 04/07/2016)

For 2H 2016, the focus for integration is interaction amongst teams focused on open innovation. The overall structure of two groups (Participation and Open Innovation) remains. The rationale for this is to maximise for execution against needs defined in 1H 2016. The structure may be revisited in 2017.

The focus for integration is therefore “Collaborative Innovation”, prototyping new collaboration models.

This document focuses on the Participation strategy and plan.

Participation

Open Innovation

Products & Pipeline

Innovation

Capabilities

Collaborative Innovation

Participation Design

Communities & Leadership

Software

Creating and sustaining a product pipeline.

Improving the culture of innovation.

Connecting Mozilla initiatives to new, valuable allies

Designing Participation programs to Mozilla objectives

Build capabilities and activate�core contributor mobilizers/leaders & communities

Design and build tools to support a radically participative organisation

Operations

Planning overhead, Overall program mgt, Comms

Mozilla Confidential - Staff and NDA'd Mozillians Only

43 of 44

Org Overview With Programs

(updated 04/07/2016)

Participation

For 2H 2016, the focus for integration is interaction amongst teams focused on open innovation. The overall structure of two groups (Participation and Open Innovation) remains. The rationale for this is to maximise for execution against needs defined in 1H 2016. The structure may be revisited in 2017.

Open Innovation

Products & Pipeline

Innovation

Capabilities

Collaborative Innovation

Participation Design

Communities & Leadership

Software

Internal

Consultancy

Incubator / Entrepreneur in Residence

Focus Areas

Pipeline: Innovation Council

Skill Building

Toolkit

Gym

Innovation Prizes

User-Driven Innovation Program

Connected Devices Collaboration

Mobilization campaigns

Leading-edge technical contribution

Mozilla Reps/ Communities

Campus Program

Skill-building

Enable Mozilla ID

Deliver Volunteer Management Systems

Evolve Collaboration Systems

Mozilla Confidential - Staff and NDA'd Mozillians Only

44 of 44

Org Overview With Roles

(updated 15/07/2016)

Innovation

Capabilities (4)

Innovation Consultant (lead)

Project Managers (2)

Content Manager

CIO

Products & Pipeline (7)

Innovation Consultant (lead)

Product Research Specialist

Product Mgt Specialist

Visual Designer

Incubator Managers (2)

Entrepreneur in Residence

Operations (2) Chief of Staff (lead) Comms Lead

Collaborative Innovation (5)

Outreach Lead

Open Innovation Strategist

Innovation Prize Project Manager

Connected Devices Specialists (2)

Communities & Leadership (10)

C&L Lead

Reps/Comm. Lead

Reps/Comm. Team (4)

Campus Lead

Campus Team (2)

Edu Team (1)

Participation

Design (2)

Participation Strategist

Participation Partnerships

Software (5)

Program Lead

Product Mgr (contractor)

Eng Mgr

UX Team (1) (contractor)

Dev Team (5) (incl 2 contractors)

Mozilla Confidential - Staff and NDA'd Mozillians Only