Modules/Activities: Difference between revisions
m (Added Wayne Thayer as peer of CA Certificates and CA Certificate Policy modules) |
No edit summary |
||
(27 intermediate revisions by 9 users not shown) | |||
Line 39: | Line 39: | ||
* Resolving conflicts among module owners | * Resolving conflicts among module owners | ||
|owner= [mailto:mitchell@mozilla.org Mitchell Baker] | |owner= [mailto:mitchell@mozilla.org Mitchell Baker] | ||
|ownersemeritus=Brendan Eich | |ownersemeritus=Brendan Eich | ||
|url= | |url= | ||
Line 46: | Line 45: | ||
{{Module | {{Module | ||
|name=Commit Access | |name=Commit Access Management | ||
|description= | |description= Governance structure for the work of implementing, managing and enforcing Mozilla's commit access systems and policies. | ||
|owner=[mailto: | |owner=[mailto:glob@mozilla.com glob] | ||
|peers= | |peers=[mailto:mconnor@mozilla.com Mike Connor], [mailto:mhristova@mozilla.com Mira Hristova], [mailto:jdirks@mozilla.com James Dirks] | ||
|ownersemeritus=Mitchell Baker | |ownersemeritus=Mitchell Baker, Josh Matthews | ||
|peersemeritus=Marcia Knous, Jonathan Lin | |||
|group= | |group= | ||
|url=http://www.mozilla.org/hacking/committer/ | |url=http://www.mozilla.org/hacking/committer/ | ||
|components=mozilla.org::Repository Account Requests | |components=mozilla.org::Repository Account Requests | ||
}} | }} | ||
Line 68: | Line 58: | ||
{{Module | {{Module | ||
|name=Security Policy | |name=Security Policy | ||
|description= | |description=Policies for handling security issues in Mozilla code | ||
|owner=[mailto:dveditz@mozilla.com Dan Veditz] | |owner=[mailto:dveditz@mozilla.com Dan Veditz] | ||
|peers=[mailto:security@mozilla.org Al Billings | |peers=[mailto:security@mozilla.org Tom Ritter] | ||
|peersemeritus= Al Billings | |||
|group=dev-security | |group=dev-security | ||
|url=http://www.mozilla.org/security/ | |url=http://www.mozilla.org/security/ | ||
Line 79: | Line 70: | ||
|name=Mozilla CA Certificate Policy | |name=Mozilla CA Certificate Policy | ||
|description=Definition and enforcement of policies governing Certification Authorities, their root certificates included in Mozilla software products, and intermediate and end-entity certificates within those CA hierarchies. | |description=Definition and enforcement of policies governing Certification Authorities, their root certificates included in Mozilla software products, and intermediate and end-entity certificates within those CA hierarchies. | ||
|owner=[mailto: | |owner= [mailto:bwilson@mozilla.com Ben Wilson] | ||
|peers= | |peers= | ||
|ownersemeritus=Frank Hecker | |ownersemeritus=Frank Hecker, Wayne Thayer, Kathleen Wilson | ||
|peersemeritus= Johnathan Nightingale, Sid Stamm, Richard Barnes | |peersemeritus= Johnathan Nightingale, Sid Stamm, Richard Barnes, Gervase Markham, Wayne Thayer, Kathleen Wilson | ||
|group=dev-security-policy | |group=dev-security-policy | ||
|url=http://www.mozilla.org/projects/security/certs/policy/ | |url=http://www.mozilla.org/projects/security/certs/policy/ | ||
Line 91: | Line 82: | ||
|name=Code Review Policy | |name=Code Review Policy | ||
|description= | |description= | ||
|owner=[mailto: | |owner=[mailto:tlmc@mozilla.com Firefox Technical Leadership Module Committee] | ||
|peers= | |peers= | ||
|peersemeritus=Brendan Eich | |peersemeritus=Brendan Eich | ||
Line 102: | Line 93: | ||
|name=Performance Regression Policy | |name=Performance Regression Policy | ||
|description= | |description= | ||
|owner=[mailto: | |owner=[mailto:tlmc@mozilla.com Firefox Technical Leadership Module Committee] | ||
|peers= | |peers= | ||
|group= | |group= | ||
Line 115: | Line 106: | ||
* which content from syndicated blogs is included | * which content from syndicated blogs is included | ||
* other planet.mozilla.org policy issues | * other planet.mozilla.org policy issues | ||
|owner= | |owner= | ||
|peers=[mailto:asa@ | |peers=[mailto:asa@mozilla.org Asa Dotzler] | ||
|group= | |group= | ||
|url= | |url= | ||
|components=Websites::planet.mozilla.org | |components=Websites::planet.mozilla.org | ||
|ownersemeritus=Robert Accettura | |ownersemeritus=Robert Accettura, Mike Hoye | ||
|peersemeritus=Reed Loden | |peersemeritus=Reed Loden | ||
}} | }} | ||
Line 130: | Line 121: | ||
* changes in FLOSS development practices which could / should be reflected | * changes in FLOSS development practices which could / should be reflected | ||
|owner=[mailto:mitchell@mozilla.org Mitchell Baker] | |owner=[mailto:mitchell@mozilla.org Mitchell Baker] | ||
|peers= | |peers=[mailto:MeekerH@gtlaw.com Heather Meeker], [mailto:villalu@gtlaw.com Luis Villa] | ||
|peersemeritus=Gervase Markham | |||
|group=governance-mpl-update | |group=governance-mpl-update | ||
|url= | |url= | ||
Line 139: | Line 131: | ||
|name=CA Certificates | |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. | |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: | |owner=[mailto:bwilson@mozilla.com Ben Wilson] | ||
|peers= | |peers= | ||
|ownersemeritus=Frank Hecker | |ownersemeritus=Frank Hecker, Kathleen Wilson | ||
|peersemeritus= Johnathan Nightingale, Sid Stamm, Richard Barnes | |peersemeritus= Johnathan Nightingale, Sid Stamm, Richard Barnes, Gervase Markham, Wayne Thayer, Ryan Sleevi, Kathleen Wilson | ||
|group=dev-security-policy | |group=dev-security-policy | ||
|url=http://www.mozilla.org/projects/security/certs/policy/ | |url=http://www.mozilla.org/projects/security/certs/policy/ | ||
Line 162: | Line 154: | ||
|group= | |group= | ||
|url=https://wiki.mozilla.org/Contribute/Dashboards | |url=https://wiki.mozilla.org/Contribute/Dashboards | ||
|components= | |components= | ||
}} | }} | ||
Line 193: | Line 168: | ||
**public campaigns or opinion pieces or educational activities, dialog with policy makers, other techniques TBD | **public campaigns or opinion pieces or educational activities, dialog with policy makers, other techniques TBD | ||
*strengthening local community capabilities to address public policy issues | *strengthening local community capabilities to address public policy issues | ||
|owner=[mailto: | |owner=[mailto:mitchell@mozilla.org Mitchell Baker] | ||
|peers= | |peers=[mailto:afowler@mozilla.com Alex Fowler], [mailto:mark@mozillafoundation.org Mark Surman] | ||
|url=https://wiki.mozilla.org/Netpolicy | |url=https://wiki.mozilla.org/Netpolicy | ||
|group=https://mail.mozilla.org/listinfo/netpolicy | |group=https://mail.mozilla.org/listinfo/netpolicy | ||
Line 201: | Line 176: | ||
}} | }} | ||
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. | 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. | ||
(It's a new thing to have a group such as "MoCo Desktop IT services" as a | (It's a new thing to have a group such as "MoCo Desktop IT services" as a | ||
Line 221: | Line 182: | ||
===Other=== | ===Other=== | ||
{{Module | {{Module | ||
|name=Tree Sheriffs | |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. | |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) | |owner=[mailto:rvandermeulen@mozilla.com Ryan VanderMeulen] (:RyanVM) | ||
|peers=[mailto: | |peers=[mailto:shengst@mozilla.com Sebastian Hengst] (:Aryx) | ||
|group= | |ownersemeritus=Ed Morley | ||
|peersemeritus=Carsten Book, Wes Kocher | |||
|group=https://mail.mozilla.org/listinfo/sheriffs | |||
|url=https://wiki.mozilla.org/Sheriffing | |url=https://wiki.mozilla.org/Sheriffing | ||
}} | }} |
Latest revision as of 19:47, 6 March 2024
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 mozilla.governance.
Name: | Governance (#) |
---|---|
Description: | Policies and process for how we distribute authority and govern ourselves; including:
|
Owner: | Mitchell Baker |
Peer(s) Emeritus: | 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:
|
Owner: | Mitchell Baker |
Owner(s) Emeritus: | Brendan Eich |
Name: | Commit Access Management (#) |
---|---|
Description: | Governance structure for the work of implementing, managing and enforcing Mozilla's commit access systems and policies. |
Owner: | glob |
Peer(s): | Mike Connor, Mira Hristova, James Dirks |
Owner(s) Emeritus: | Mitchell Baker, Josh Matthews |
Peer(s) Emeritus: | Marcia Knous, Jonathan Lin |
Bugzilla Component(s): | mozilla.org::Repository Account Requests |
URL(s): | http://www.mozilla.org/hacking/committer/ |
Name: | Security Policy (#) |
---|---|
Description: | Policies for handling security issues in Mozilla code |
Owner: | Dan Veditz |
Peer(s): | Tom Ritter |
Peer(s) Emeritus: | Al Billings |
URL(s): | http://www.mozilla.org/security/ |
Discussion Group: | dev-security |
Name: | Mozilla CA Certificate Policy (#) |
---|---|
Description: | Definition and enforcement of policies governing Certification Authorities, their root certificates included in Mozilla software products, and intermediate and end-entity certificates within those CA hierarchies. |
Owner: | Ben Wilson |
Owner(s) Emeritus: | Frank Hecker, Wayne Thayer, Kathleen Wilson |
Peer(s) Emeritus: | Johnathan Nightingale, Sid Stamm, Richard Barnes, Gervase Markham, Wayne Thayer, Kathleen Wilson |
URL(s): | http://www.mozilla.org/projects/security/certs/policy/ |
Discussion Group: | dev-security-policy |
Name: | Code Review Policy (#) |
---|---|
Description: | |
Owner: | Firefox Technical Leadership Module Committee |
Peer(s) Emeritus: | Brendan Eich |
URL(s): | http://www.mozilla.org/hacking/reviewers.html |
Name: | Performance Regression Policy (#) |
---|---|
Description: | |
Owner: | Firefox Technical Leadership Module Committee |
Name: | Planet Mozilla (#) |
---|---|
Description: | Content and policy for planet.mozilla.org, including topics such as:
|
Owner: | |
Peer(s): | Asa Dotzler |
Owner(s) Emeritus: | Robert Accettura, Mike Hoye |
Peer(s) Emeritus: | Reed Loden |
Bugzilla Component(s): | Websites::planet.mozilla.org |
Name: | Mozilla Public License (#) |
---|---|
Description: | Maintenance and development of the MPL
|
Owner: | Mitchell Baker |
Peer(s): | Heather Meeker, Luis Villa |
Peer(s) Emeritus: | Gervase Markham |
Bugzilla Component(s): | mozilla.org::Licensing |
Discussion Group: | governance-mpl-update |
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: | Ben Wilson |
Owner(s) Emeritus: | Frank Hecker, Kathleen Wilson |
Peer(s) Emeritus: | Johnathan Nightingale, Sid Stamm, Richard Barnes, Gervase Markham, Wayne Thayer, Ryan Sleevi, Kathleen Wilson |
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:
|
Owner: | Pierros Papadeas |
Peer(s): | David Boswell, Asa Dotzler, Daniel Einspanjer, Annie Elliott, David Eaves, Michelle Thorne, Ryan Merkley |
URL(s): | https://wiki.mozilla.org/Contribute/Dashboards |
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:
|
Owner: | Mitchell Baker |
Peer(s): | Alex Fowler, Mark Surman |
URL(s): | https://wiki.mozilla.org/Netpolicy |
Discussion Group: | https://mail.mozilla.org/listinfo/netpolicy |
Notes: | Area Expert Advisors: Katharina Borchert, Andrew Bridges, Hanno Kaiser, Andrew McLaughlin, Danny Weitzner, Gene Kimmelman, and Ronaldo Lemos |
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.
(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: | 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: | Ryan VanderMeulen (:RyanVM) |
Peer(s): | Sebastian Hengst (:Aryx) |
Owner(s) Emeritus: | Ed Morley |
Peer(s) Emeritus: | Carsten Book, Wes Kocher |
URL(s): | https://wiki.mozilla.org/Sheriffing |
Discussion Group: | https://mail.mozilla.org/listinfo/sheriffs |