58
edits
Changes
Correction of page name and move from https://wiki.mozilla.org/Modules/Technical_Leadership_Module_Committee
===Scope and Operation===
The Firefox Technical Leadership module (FTLM) is responsible for engineering coordination and escalation among the modules that make up Firefox, including ownership of the [[Modules/All#mozilla-toplevel|top-level module]]. The FTLM generally tries to avoid day-to-day involvement in operation of lower-level modules, but gets involved with decisions that are explicitly cross-module and with issues that cannot be resolved at lower levels, such as:
* Resolution of decisions that do not fall clearly into any specific module or set of modules
* Escalation of disputes beyond the module owner level
In addition, the [[Modules/Activities#Module_Ownership_System|Module Ownership module]] delegates its responsibilities for the modules that make up Firefox to the FTLM. This delegated authority includes topics such as those listed below, which would otherwise escalate to the [[Modules/Activities#Module_Ownership_System|Module Ownership module]]:
* 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
The FTLM decision making process attempts to form consensus among stakeholders, with the committee empowered to resolve disputes when that consensus cannot be reached, and the chair empowered when consensus cannot be reached within the committee.
===Structure===
The FTLM is governed by the Technical Leadership Module Committee (TLMC). The TLMC consists of the CTO and VP of Engineering from the Mozilla Firefox organization, plus additional members that reflect the technical leadership of the project. The additional members are selected as needed to reach a six member minimum and ensure broad coverage of domain knowledge. In most cases, we would expect those leaders to be more or less full-time on the project. These additional members will serve two-year terms. As of 2018, the current members are:
* Eric Rescorla (Firefox CTO) - Chair
* Dave Camp (Vice President, Firefox Engineering)
* Boris Zbarsky
* David Baron
* Dave Townsend
* Luke Wagner
The owner of the [[Modules/Activities#Module_Ownership_System|Module Ownership module]] (currently Mitchell Baker) is expected to revisit these membership criteria upon any substantial changes to the management structures or the relationships to corporate entities with the project.
===List of Applicable Modules===
For purposes of defining the scope of the TLMC's responsibility, the modules that make up Firefox are as follows:
* [[Modules/Firefox|Firefox]]
* [[Modules/Toolkit|Toolkit]]
* [[Modules/Core|Core]]
* [[Modules/All#Submodules|Submodules]]
* [[Modules/All#Browser|Browser]]
* [[Modules/All#Tier_1_Platforms|Tier 1 Platforms]]
* Other:
** [[Modules/All#Add-on_SDK|Add-On SDK]]
** [[Modules/All#Android_Background_Services|Android Background Services]]
** [[Modules/All#Firefox_for_Metro|Firefox for Metro]]
** [[Modules/All#BrowserID|BrowserID]]
** [[Modules/All#Firefox_Accounts|Firefox Accounts]]
** [[Modules/All#DevTools|Devtools]]
** [[Modules/All#Firefox_for_iOS_.28Fennec.29|Fennec]]
** [[Modules/All#Sync|Sync]]
** [[Modules/All#Mozilla_Location_Service_.28MLS.29|Mozilla Location Service]]
** [[Modules/All#Mozilla_Stumbler_.28.22MozStumbler.22.29|Mozstumbler]]
** [[Modules/All#URL_Classifier|URL Classifier]]
** [[Modules/All#Tree_Sheriffs|Tree Sheriffs]]
* Governance
** [[Modules/All#Security_Policy|Security Policy]]
** [[Modules/All#Mozilla_CA_Certificate_Policy|CA Certificate Policy]]
** [[Modules/All#Code_Review_Policy|Code Review Policy]]
** [[Modules/All#Performance_Regression_Policy|Performance Regression Policy]]
** [[Modules/All#CA_Certificates|CA Certificates]]
** [[Modules/All#Commit_Access_Policy|Commit Access Policy]]
The Firefox Technical Leadership module (FTLM) is responsible for engineering coordination and escalation among the modules that make up Firefox, including ownership of the [[Modules/All#mozilla-toplevel|top-level module]]. The FTLM generally tries to avoid day-to-day involvement in operation of lower-level modules, but gets involved with decisions that are explicitly cross-module and with issues that cannot be resolved at lower levels, such as:
* Resolution of decisions that do not fall clearly into any specific module or set of modules
* Escalation of disputes beyond the module owner level
In addition, the [[Modules/Activities#Module_Ownership_System|Module Ownership module]] delegates its responsibilities for the modules that make up Firefox to the FTLM. This delegated authority includes topics such as those listed below, which would otherwise escalate to the [[Modules/Activities#Module_Ownership_System|Module Ownership module]]:
* 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
The FTLM decision making process attempts to form consensus among stakeholders, with the committee empowered to resolve disputes when that consensus cannot be reached, and the chair empowered when consensus cannot be reached within the committee.
===Structure===
The FTLM is governed by the Technical Leadership Module Committee (TLMC). The TLMC consists of the CTO and VP of Engineering from the Mozilla Firefox organization, plus additional members that reflect the technical leadership of the project. The additional members are selected as needed to reach a six member minimum and ensure broad coverage of domain knowledge. In most cases, we would expect those leaders to be more or less full-time on the project. These additional members will serve two-year terms. As of 2018, the current members are:
* Eric Rescorla (Firefox CTO) - Chair
* Dave Camp (Vice President, Firefox Engineering)
* Boris Zbarsky
* David Baron
* Dave Townsend
* Luke Wagner
The owner of the [[Modules/Activities#Module_Ownership_System|Module Ownership module]] (currently Mitchell Baker) is expected to revisit these membership criteria upon any substantial changes to the management structures or the relationships to corporate entities with the project.
===List of Applicable Modules===
For purposes of defining the scope of the TLMC's responsibility, the modules that make up Firefox are as follows:
* [[Modules/Firefox|Firefox]]
* [[Modules/Toolkit|Toolkit]]
* [[Modules/Core|Core]]
* [[Modules/All#Submodules|Submodules]]
* [[Modules/All#Browser|Browser]]
* [[Modules/All#Tier_1_Platforms|Tier 1 Platforms]]
* Other:
** [[Modules/All#Add-on_SDK|Add-On SDK]]
** [[Modules/All#Android_Background_Services|Android Background Services]]
** [[Modules/All#Firefox_for_Metro|Firefox for Metro]]
** [[Modules/All#BrowserID|BrowserID]]
** [[Modules/All#Firefox_Accounts|Firefox Accounts]]
** [[Modules/All#DevTools|Devtools]]
** [[Modules/All#Firefox_for_iOS_.28Fennec.29|Fennec]]
** [[Modules/All#Sync|Sync]]
** [[Modules/All#Mozilla_Location_Service_.28MLS.29|Mozilla Location Service]]
** [[Modules/All#Mozilla_Stumbler_.28.22MozStumbler.22.29|Mozstumbler]]
** [[Modules/All#URL_Classifier|URL Classifier]]
** [[Modules/All#Tree_Sheriffs|Tree Sheriffs]]
* Governance
** [[Modules/All#Security_Policy|Security Policy]]
** [[Modules/All#Mozilla_CA_Certificate_Policy|CA Certificate Policy]]
** [[Modules/All#Code_Review_Policy|Code Review Policy]]
** [[Modules/All#Performance_Regression_Policy|Performance Regression Policy]]
** [[Modules/All#CA_Certificates|CA Certificates]]
** [[Modules/All#Commit_Access_Policy|Commit Access Policy]]
