Page 1

THE STUFF YOU NEED TO KNOW TO WORK HERE

MOZILLA


THINGS IN THIS DOCUMENT WITH PAGE NUMBERS

The QUESTION IS NOT “HOW DO WE BECOME THE BEST IN THE WORLD?” BUT “HOW DO WE BECOME THE BEST FOR THE WORLD?”

~UFFE ALBAEK, F OUNDER KAOS PILOTS

INSTRUCTIONS GOVERNANCE AND ROLE OF STEERING COMMITTEE AND COMMUNITY AND DECISION-MAKING (RACI) PRODUCTS FIREFOX DESKTOP RELEASE CYCLE FIREFOX MOBILE FIREFOX OS GROUPS / ORG STRUCTURE GOALS & PRIORITIES COMMUNICATIONS COMMUNICTION TOOLS PHONEBOOKS EMAIL EMAIL LISTS AND ALIASES IRC IM TELEPHONE VIDYO YAMMER FORUMS NEWSLETTERS BLOGS AIR MOZILLA BROWNBAGS RYPPLE (SEE PERFORMANCE) BUGZILLA SERVICE NOW (SEE IT) INTRANET / MANA MOZILLA WIKI MEETINGS STEERING COMMITTEE DIRECTORS MONDAY MORNING PROJECT MOCO MEETING BOARD MEETING + SLIDE REVIEW 1:1S WORK WEEKS PUBLIC RELATIONS (ROLE OF) MEDIA TRAINING PR REVIEW PEOPLE HR BUSINESS PARTNERS IMPORTANT CONTACTS

RECRUITING - THE MANNER IN WHICH WE HIRE GREATNESS JOB POSTING HIRING PROCESS INTERVIEWING EMPLOYEE REFERRALS IMMIGRATION RELOCATION TRAVEL & EXPENSE EGENCIA EXPENSES BENEFITS & PAYROLL NEWBIE THINGS IT THE “X” REMOTIE THINGS PERFORMANCE LEARNING & CAREER DEVELOPMENT MOBB SAFARI BOOKS ROSETTA STONE EVENTS MOZ CAMP RECOGNITION & REWARD RYPPLE YAMMER FRIENDS OF THE TREE BADGES COMMUNITY & VOLUNTEERS POLICIES & EXPECTATIONS WHAT NOT TO WEAR MOZILLA SPACES EMPLOYMENT AT WILL (U.S.?) EQUAL EMPLOYMENT & DISCRIMINATION AMERICANS WITH DISABILITIES HARASSMENT FREE WORKPLACE EMPLOYEE RECORDS AND DATA BUSINESS ETHICS CONDUCT IN THE WORKPLACE PERSONAL PROPERTY AT WORK LEAVING MOZILLA SAFETY, SECURITY, AND HEALTH WEATHER POLICY EROGNOMICS Page 3 - STUFF YOU NEED TO KNOW TO WORK HERE


INSTRUCTIONS

governance AND MODULAR OWNERSHIP

Need to talk about how much stuff there is and how this is a bit of a map. This document is a revolutionary breakthrough in technology: no wires, no electric circuits, no batteries, nothing to be connected or switched on. It’s easy to use. Just flip its cover. Compact and portable, it can be used anywhere – even sitting in an armchair by the fire. Here's how it works... Each handbook is constructed of sequentially numbered pages, each capable of holding thousands of bits of information. These pages are locked together with a custom-fit device which keeps the pages in their correct sequence. There are a lot of links to a lot more content; content that would take you a lifetime to get through. And, if you’re brave enough, journey deeper. Just know, it is endless. If you get lost along the way, you know you can always come back here. We’ve tucked “Lil’ Bits of Awesome” throughout the book. These are places where you can link out to the wiki to add or interact with content. These call out boxes are in grey. If you have feedback on this book, please contact mozilla.handbook.project@mozilla.com

Governance is a word we use a lot at Mozilla. To help you understand how it works, we’ve pulled some key content from the wiki about Modular Ownership (you can read more here: https://www. mozilla.org/hacking/module-ownership. html). Modular ownership is how the project is governed: “The Mozilla project is far too big for any one person -- or even a small set of people -- to make the decisions. Instead, decision-making is distributed to a range of participants through the project through “Modules”, each of which has a Module Owner. A module is, in the case of code, a piece of functionality, or in the case of non-code, an activity, with reasonably well-defined boundaries. Of course, “reasonably well-defined boundaries” doesn’t provide absolute clarity. Trying to create absolute definitions would require elaborate rules and exceptions that aren’t needed in most cases. Rather than spend energy devising such definitions, we prefer to let module owners manage any overlap or shared ownership if possible, with mediation when necessary. The work of the module owners and the health of the system are overseen by the owner and peers of the “Module Ownership” module. A number of larger

modules like Firefox, have sub-modules subordinate to them. The module owner and peers of the appropriate module is responsible for sub-module ownership appointment and removal in those areas. Mozilla uses its wiki to track modules, module owners and peers.” If you’re interested in a story about decision-making and the delegation of authority at Mozilla, read this lovely blog post on the topic by our Chair, Mitchell Baker: http://blog.lizardwrangler. com/2011/07/12/watching-brendan-delegate-authority-now-june-2011-and-thenjan-1999/ There is also a book by David R. Booth called Peer Participation and Software, which explains it well. Here’s a quote: “Modularity arguably is part of the open source definition because the organization of source files into chunks within a software program isolates tasks on the basis of functionality. A volunteer developer dedicates himself to the specific fix he deems necessary within the parameters set by the module. He chooses a topic he is most qualified to work on. Because modularity dedicates the programmer to a single component of the code base, it is the basis for specifying, soliciting, and organizing contributions from volunteers.”

Page 5 - STUFF YOU NEED TO KNOW TO WORK HERE


We actually have a real community of people doing something useful.

~Mitchell Baker, chair

The Mozilla Corporation’s senior executive team is known as the Steering Committee. The Steering Committee is responsible for leadership, coordination among the various groups working together to produce Mozilla’s consumer products. The Steering Committee stays abreast of market conditions, charts Mozilla’s path through this environment, and sets the direction of Mozilla’s general consumer product offerings. The Steering Committee also performs traditional management tasks such as hiring, planning, and resource allocation. It does so in ways that align with Mozilla’s non-profit, open-source, community-based identity. The Steering Committee seeks to absorb, distill and reflect Mozilla community values in the exercise of its responsibilities.

GOVERANCE AND THE ROLE OF STEERING COMMITTEE

Members of the Mozilla Corporation Steering Committee are listed here: http://www.mozilla. org/foundation/mocosc.html Mitchell Baker, Mozilla Chair, describes the Steering Committee’s goals and roles here: http:// blog.lizardwrangler.com/2008/02/28/steering-committee/

Page 7 - STUFF YOU NEED TO KNOW TO WORK HERE


Page 8 - STUFF YOU NEED TO KNOW TO WORK HERE


Handbook v1 TEST  

Handbook v1 TEST

Read more
Read more
Similar to
Popular now
Just for you