Account confirmers, Anti-spam team, Confirmed users, Bureaucrats and Sysops emeriti
4,925
edits
Governance/Reboot: Difference between revisions
Jump to navigation
Jump to search
no edit summary
(Created page with "{{draft}} The Mozilla project's governance mechanisms have not kept pace with changes within the project in terms of the breadth and scope of what we do. The [[Modules|module ow...") |
No edit summary |
||
| Line 2: | Line 2: | ||
The Mozilla project's governance mechanisms have not kept pace with changes within the project in terms of the breadth and scope of what we do. The [[Modules|module ownership system]] may now cover as little as 25% of the project's activities. Other mechanisms of governance, like the MoCo organization's management hierarchy, have naturally moved to fill the gap - but this leaves a transparency problem, as well as widening a divide between employees and volunteers. | The Mozilla project's governance mechanisms have not kept pace with changes within the project in terms of the breadth and scope of what we do. The [[Modules|module ownership system]] may now cover as little as 25% of the project's activities. Other mechanisms of governance, like the MoCo organization's management hierarchy, have naturally moved to fill the gap - but this leaves a transparency problem, as well as widening a divide between employees and volunteers. | ||
Having a comprehensive and clear community governance system promotes transparency and accountability within the project, as well as providing clear paths for contributors of all types to go from "involved" to "heavily involved" to "being a leader". | |||
This page outlines a plan to reinvigorate the community governance system. | This page outlines a plan to reinvigorate the community governance system. | ||