Modules/Activities

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 Ultimate authority within the project rests with the owner and peer(s) of this module, and project decisions can be escalated to here.
Owner:	Mitchell Baker
Peer(s):	Brendan Eich
Bugzilla Component(s):	mozilla.org::Governance
URL(s):	https://wiki.mozilla.org/GovernanceIssues
Discussion Group:	governance

Governance Sub Modules

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:	Brendan Eich
Peer(s):	Stuart Parmenter, Dan Mosedale, Robert Kaiser, Mike Connor, David Baron, Frank Hecker, David Ascher, 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.)

Name:	Commit Access Policy (#)
Description:
Owner:	Mitchell Baker
Bugzilla Component(s):	mozilla.org::Repository Account Requests
URL(s):	http://www.mozilla.org/hacking/committer/

Name:	Security Policy (#)
Description:
Owner:	Frank Hecker
URL(s):	http://www.mozilla.org/projects/security/security-bugs-policy.html

Name:	Mozilla CA Certificate Policy (#)
Description:
Owner:	Kathleen Wilson
Peer(s):	Frank Hecker, Gervase Markham, Johnathan Nightingale, Sid Stamm
URL(s):	http://www.mozilla.org/projects/security/certs/policy/

Name:	Code Review Policy (#)
Description:
Owner:	Mitchell Baker
Peer(s):	Brendan Eich
URL(s):	http://www.mozilla.org/hacking/reviewers.html

Name:	Performance Regression Policy (#)
Description:
Owner:	Mitchell Baker

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:	Robert Accettura
Peer(s):	Asa Dotzler, Reed Loden, J. Paul Reed -- collectively, planet@mozilla.org (preferred)
Bugzilla Component(s):	Websites::planet.mozilla.org

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:	Mitchell Baker
Peer(s):	Harvey Anderson, Gervase Markham, Heather Meeker, Luis Villa
Bugzilla Component(s):	mozilla.org::Licensing
Discussion Group:	governance-mpl-update

Name:	www.mozilla.org (#)
Description:	Content and policy for www.mozilla.org. Sub-modules and their owners can be found here.
Owner:	Reed Loden (technical issues), David Boswell (content issues)
Peer(s):	Elika Etemad, Robert Kaiser, Eric Shepherd
Discussion Group:	dev-mozilla-org

Name:	CA Certificates (#)
Description:	Determine which root certificates should be included in Mozilla software products and which trust bits should be set on them, and evaluate requests from Certification Authorities (CAs) for inclusion of new root certificates.
Owner:	Kathleen Wilson
Peer(s):	Frank Hecker, Gervase Markham, Johnathan Nightingale, Sid Stamm
Bugzilla Component(s):	mozilla.org::CA Certificates
URL(s):	http://www.mozilla.org/projects/security/certs/policy/
Discussion Group:	dev-security-policy

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:	David Boswell
Peer(s):	Asa Dotzler, Daniel Einspanjer, Annie Elliott, David Eaves, Pierros Papadeas, Michelle Thorne, Ryan Merkley
URL(s):	https://wiki.mozilla.org/Contribute/Dashboards
Discussion Group:	mozillians

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:	Stormy Peters
Peer(s):	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, conductors@mozilla.org.
URL(s):	http://wiki.mozilla.org/Conductors
Discussion Group:	mozilla.governance

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:	Harvey Anderson
Peer(s):	Mitchell Baker, Alex Fowler, Mark Surman
URL(s):	http://
Discussion Group:	mozilla.governance

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:	Jono Xia
Peer(s):	Asa Dotzler, MoCo Desktop IT services
URL(s):	https://wiki.mozilla.org/WeeklyUpdates
Discussion Group:	mozilla.governance

(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

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:	Brett Gaylor
Peer(s):	Michelle Thorne
URL(s):	http://www.mozillapopcorn.org/
Discussion Group:	mozilla.community.popcorn