canmove, Confirmed users
2,081
edits
Thunderbird/New Release and Governance Model: Difference between revisions
Thunderbird/New Release and Governance Model (view source)
Revision as of 06:19, 4 September 2021
, 4 September 2021add warning that this document is obsolete
(add warning that this document is obsolete) |
|||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{Warning|This is an out-of-date document stored for historical purposes. It describes the state of Thunderbird in 2012. It is no longer accurate as of 2014 when Thunderbird became a formally organized, community run project, independent of Mozilla. This reorganization was as a result of an October 2014 summit of volunteers held in Toronto. The state of Thunderbird today is described [[Thunderbird:Home#Status|here]].}} | |||
Mozilla is focusing a lot of its efforts towards important web and mobile projects, while Thunderbird remains a pure desktop only email client. We have come to the conclusion that continued innovation on Thunderbird is not a priority for Mozilla and that the most critical needs for the product are on-going security and stability. In fact, it is quite possible that Thunderbird is already pretty much what its users want and there is not a high demand for innovation in this field. | Mozilla is focusing a lot of its efforts towards important web and mobile projects, while Thunderbird remains a pure desktop only email client. We have come to the conclusion that continued innovation on Thunderbird is not a priority for Mozilla and that the most critical needs for the product are on-going security and stability. In fact, it is quite possible that Thunderbird is already pretty much what its users want and there is not a high demand for innovation in this field. | ||
| Line 9: | Line 11: | ||
There are currently two editions of Thunderbird: 'Thunderbird' and 'Thunderbird ESR'. Both will be maintained and based on the same Gecko engine release. Only 'Thunderbird' is affected by the change: | There are currently two editions of Thunderbird: 'Thunderbird' and 'Thunderbird ESR'. Both will be maintained and based on the same Gecko engine release. Only 'Thunderbird' is affected by the change: | ||
* A new release of Thunderbird ESR | * A new release of Thunderbird ESR is available since November 20th, 2012. As defined in the [http://www.mozilla.org/thunderbird/organizations/faq/ Thunderbird ESR plan], it has inherited the then-current Thunderbird feature-set. This release will be updated every six weeks, for the duration of the ESR cycle to ensure the best possible security and stability for organizations. | ||
* At the same time, Thunderbird | * At the same time, Thunderbird has been released with the same feature set as Thunderbird ESR and will be updated every six-weeks for security and stability. However, and contrary to Thunderbird ESR, Thunderbird may include an additional release during the ESR timeframe which would include extra features. | ||
The plan should therefore have no impact in the way individuals and organizations use the product and obtain updates. | The plan should therefore have no impact in the way individuals and organizations use the product and obtain updates. | ||
== Governance model == | == Governance model == | ||
Thunderbird | Thunderbird is driven by a lightweight structure, focusing on producing security updates and suited to welcome community contributed innovations: | ||
* Thunderbird [[Modules|modules owners]] | * Thunderbird [[Modules|modules owners]] remain in charge of their module and allow community contributions innovation on their own merits. Module ownership is open to any contributor and can evolve over time. | ||
* | * The Release Drivers team produces the Thunderbird updates every six weeks and works with module owners on the planning and integration of the community contributed innovations. | ||
* Mozilla | * Mozilla continues to provide paid staff, logistics and infrastructure for the release drivers team to produce updates and new releases with the same level of quality than today. Support continues to be provided by the Thunderbird community and Mozilla continues to provide the required infrastructure. | ||
= Governance = | = Governance = | ||
| Line 81: | Line 83: | ||
==== Resources provided by Mozilla ==== | ==== Resources provided by Mozilla ==== | ||
Mozilla | Mozilla provides the following resources for Thunderbird: | ||
The Thunderbird release driver team | The Thunderbird release driver team is composed of the following paid-staff: | ||
* Lead Engineer & Release Driver: Mark Banner | * Lead Engineer & Release Driver: Mark Banner | ||
* Back End Integration Engineer: Irving Reid | * Back End Integration Engineer: Irving Reid | ||
| Line 92: | Line 94: | ||
* Business Development & Legal: Jean-Baptiste Piacentino | * Business Development & Legal: Jean-Baptiste Piacentino | ||
Infrastructure to build and support Thunderbird | Infrastructure to build and support Thunderbird remains untouched (Release Engineering, Web Services and Support services). | ||
== Releases == | == Releases == | ||
| Line 158: | Line 160: | ||
* Documentation has good community involvement already, contact via the support mailing list | * Documentation has good community involvement already, contact via the support mailing list | ||
* Need to ensure that the necessary documentation for releases is co-ordinated with release drivers | * Need to ensure that the necessary documentation for releases is co-ordinated with release drivers | ||
== Engagement == | |||
* Engagement will be taken care of by a contributor. A Mozilla Reps is identified | |||
* it will cover the maintenance of current Facebook and Twitter accounts, opening new channels if needed | |||
* being a virtual module owner | |||
* managing eventual contributors event logistics | |||
* updating Start Page editorial calendar twice a year | |||
* liaising with MozGear for swags allocation to Friend of the Tree | |||
* keeping the Mozilla brand usage in line within Mozilla guidelines | |||
== Lightning == | == Lightning == | ||