Difference between revisions of "Sugar Labs/Governance"
m (Protected "Sugar Labs/Governance": High traffic page: vandal move protection measure ([edit=autoconfirmed] (indefinite) [move=autoconfirmed] (indefinite))) |
|||
| (27 intermediate revisions by 10 users not shown) | |||
| Line 1: | Line 1: | ||
| − | <noinclude>{{TeamHeader|Oversight Board|roadmap_link=Oversight Board/Vision|roadmap_label=Vision}}</noinclude> | + | <noinclude>{{TeamHeader|Oversight Board|roadmap_link=Oversight Board/Vision|roadmap_label=Vision}} |
| − | + | [[Category:General public]] | |
| + | [[Category:Governance]] | ||
| + | [[Category:Policy]] | ||
| + | </noinclude> | ||
| + | |||
==Sugar Labs Rules of Governance== | ==Sugar Labs Rules of Governance== | ||
| − | Please comment | + | Please comment on the [[Talk:Sugar Labs/Governance|discussion page]]. |
---- | ---- | ||
| − | One of the challenges that free software projects face is the impact of governance on their community members: while FLOSS licenses assure access to source code, that doesn't guarantee a successful project. A governance model can help ensure that the project is run in a professional, disciplined, and equitable manner. Good governance lets the community engage in discourse and provides a transparent mechanism for arbitration in the hopefully rare circumstances in which it is necessary. | + | One of the challenges that free software projects face is the impact of governance on their [[Sugar_Labs/Members|community members]]: while FLOSS licenses assure access to source code, that doesn't guarantee a successful project. A governance model can help ensure that the project is run in a professional, disciplined, and equitable manner. Good governance lets the community engage in discourse and provides a transparent mechanism for arbitration in the hopefully rare circumstances in which it is necessary. |
Some attributes that are necessary for good governance include: meritocracy, transparency of process, open access to anyone who has demonstrated the skills to contribute, and a means to ensure a balance of control so that no one special interest wrests control of either the discourse or the decision-making. | Some attributes that are necessary for good governance include: meritocracy, transparency of process, open access to anyone who has demonstrated the skills to contribute, and a means to ensure a balance of control so that no one special interest wrests control of either the discourse or the decision-making. | ||
| Line 13: | Line 17: | ||
Sugar Labs is a member of the [http://conservancy.softwarefreedom.org Software Freedom Conservancy] (SFC). This places the project under the umbrella of a 501.3(c) foundation. "The Conservancy provides member projects with free financial and administrative services, but does not involve itself with technological and artistic decisions. By joining the Conservancy, member FLOSS projects can obtain the benefits of a formal legal structure while keeping themselves focused on software development." Governance must be maintained by Sugar Labs on its own behalf to provide for the long term success and stability of Sugar. | Sugar Labs is a member of the [http://conservancy.softwarefreedom.org Software Freedom Conservancy] (SFC). This places the project under the umbrella of a 501.3(c) foundation. "The Conservancy provides member projects with free financial and administrative services, but does not involve itself with technological and artistic decisions. By joining the Conservancy, member FLOSS projects can obtain the benefits of a formal legal structure while keeping themselves focused on software development." Governance must be maintained by Sugar Labs on its own behalf to provide for the long term success and stability of Sugar. | ||
| + | |||
| + | The [[Sugar_Labs/SFC_Fiscal_Agreement|agreement between Sugar Labs and the SFC is here]]. | ||
The following governance model is largely derived from the model used by the Gnome Foundation (Please see [http://foundation.gnome.org/about/ gnome.org/about]). | The following governance model is largely derived from the model used by the Gnome Foundation (Please see [http://foundation.gnome.org/about/ gnome.org/about]). | ||
| + | |||
| + | Sugar Labs adheres to the [https://github.com/conservancy/policies/blob/master/README.md policies] of the SFC. | ||
==== Transactions ==== | ==== Transactions ==== | ||
| Line 23: | Line 31: | ||
* [[Sugar_Labs/Governance/Transactions#Project_proposal_approval|Project proposal approval]] | * [[Sugar_Labs/Governance/Transactions#Project_proposal_approval|Project proposal approval]] | ||
* [[Sugar_Labs/Governance/Transactions#License_request|License request]] | * [[Sugar_Labs/Governance/Transactions#License_request|License request]] | ||
| + | * [[Sugar_Labs/Governance/Transactions#Tax_receipt|Tax receipt request]] | ||
===Oversight Board=== | ===Oversight Board=== | ||
| Line 28: | Line 37: | ||
The central administrative body of Sugar Labs is termed the [[Oversight_Board|Oversight Board]]. | The central administrative body of Sugar Labs is termed the [[Oversight_Board|Oversight Board]]. | ||
| − | Sugar Labs shall be governed by an Oversight Board, consisting of seven (7) members | + | Sugar Labs shall be governed by an Oversight Board, consisting of seven (7) members elected by the Sugar community—the Sugar Membership. The positions on the Oversight Board will be on a two-year staggered basis. The members of the Oversight Board may be removed from the position at any time by a majority vote of the Community Members. Upon the resignation or removal of a member of the Oversight Board, the Community Members shall elect a replacement Community Member to serve on the Oversight Board. The Oversight Board shall meet at least once per quarter to discuss various topics pertaining to the regular activities of the Sugar Labs Project and Sugar. (It is expected that more frequent meeting will be required in the early stages of the program.) The minutes to these meetings shall be posted publicly on the Sugar Labs wiki ([[Oversight Board/Minutes]]). |
The members of the Oversight Board may be removed from the position at any time by a majority vote of the Community Members. Upon the resignation or removal of a member of the Oversight Board, the Community Members shall elect a replacement Community Member to serve on the Oversight Board. | The members of the Oversight Board may be removed from the position at any time by a majority vote of the Community Members. Upon the resignation or removal of a member of the Oversight Board, the Community Members shall elect a replacement Community Member to serve on the Oversight Board. | ||
The Oversight Board will elect a single individual to communicate with the Conservancy (the "Representative") and shall notify the Conservancy promptly following the election of a new Representative. The Representative will have the authority to instruct the Conservancy on the Project's behalf on all matters. | The Oversight Board will elect a single individual to communicate with the Conservancy (the "Representative") and shall notify the Conservancy promptly following the election of a new Representative. The Representative will have the authority to instruct the Conservancy on the Project's behalf on all matters. | ||
| + | |||
| + | The current list of Oversight Board members is on the [[Oversight Board]] page. | ||
| + | |||
| + | '''Election Process''' | ||
| + | |||
| + | The Sugar Labs [[Sugar_Labs/Members|membership]] elects the Oversight Board each August, for terms beginning in September. Members can nominate themselves to run in the election according to each Election's calendar. The election process is overseen by the [[Sugar_Labs/Governance/Committees#Membership_and_Elections_Committee|Membership and Elections Committee]], which can be reached at elections at sugarlabs.org. | ||
====Decision Panels==== | ====Decision Panels==== | ||
| Line 46: | Line 61: | ||
Advisory board member companies pay an annual fee which helps finance the operations of the Sugar Labs Project. | Advisory board member companies pay an annual fee which helps finance the operations of the Sugar Labs Project. | ||
| − | === | + | === Special Interest Groups === |
| − | + | Special Interest Groups (SIGs) may be established by any member. They can be formed around | |
| + | any topic and, if they prove to be useful, can be designated as official committees. | ||
| + | SIGs typically organize themselves as [[Sugar Labs/Teams|Teams]], [[:Category:Project|Projects]], or [[Local Labs]]. | ||
| − | + | ===Referenda=== | |
| − | + | At times an issue may arise that merits gathering consensus from the community. Any member of the Sugar Labs Foundation can suggest a referendum. To be accepted, a request for a referendum must be endorsed by 10% of all of the membership. The overall referendum process is overseen by the [[Sugar_Labs/Governance/Committees#Membership_and_Elections_Committee|Membership and Elections Committee]], which can be reached at elections at sugarlabs.org. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | At times an issue may arise that merits gathering consensus from the community. Any member of the Sugar Labs Foundation can suggest a referendum. To be accepted, a request for a referendum must be endorsed by 10% of all of the membership. The overall referendum process is overseen by the Membership and Elections Committee, which can be reached at elections | ||
A 75% vote of all of the members can override an Oversight Board decision. | A 75% vote of all of the members can override an Oversight Board decision. | ||
| Line 67: | Line 76: | ||
{{Special:PrefixIndex/{{PAGENAMEE}}/}} | {{Special:PrefixIndex/{{PAGENAMEE}}/}} | ||
| − | |||
| − | |||
| − | |||
Revision as of 20:16, 25 April 2018
Sugar Labs Rules of Governance
Please comment on the discussion page.
One of the challenges that free software projects face is the impact of governance on their community members: while FLOSS licenses assure access to source code, that doesn't guarantee a successful project. A governance model can help ensure that the project is run in a professional, disciplined, and equitable manner. Good governance lets the community engage in discourse and provides a transparent mechanism for arbitration in the hopefully rare circumstances in which it is necessary.
Some attributes that are necessary for good governance include: meritocracy, transparency of process, open access to anyone who has demonstrated the skills to contribute, and a means to ensure a balance of control so that no one special interest wrests control of either the discourse or the decision-making.
Software Freedom Conservancy
Sugar Labs is a member of the Software Freedom Conservancy (SFC). This places the project under the umbrella of a 501.3(c) foundation. "The Conservancy provides member projects with free financial and administrative services, but does not involve itself with technological and artistic decisions. By joining the Conservancy, member FLOSS projects can obtain the benefits of a formal legal structure while keeping themselves focused on software development." Governance must be maintained by Sugar Labs on its own behalf to provide for the long term success and stability of Sugar.
The agreement between Sugar Labs and the SFC is here.
The following governance model is largely derived from the model used by the Gnome Foundation (Please see gnome.org/about).
Sugar Labs adheres to the policies of the SFC.
Transactions
As a fiscal sponsor for FOSS projects, the Conservancy provides member projects with financial and administrative services:
Oversight Board
The central administrative body of Sugar Labs is termed the Oversight Board.
Sugar Labs shall be governed by an Oversight Board, consisting of seven (7) members elected by the Sugar community—the Sugar Membership. The positions on the Oversight Board will be on a two-year staggered basis. The members of the Oversight Board may be removed from the position at any time by a majority vote of the Community Members. Upon the resignation or removal of a member of the Oversight Board, the Community Members shall elect a replacement Community Member to serve on the Oversight Board. The Oversight Board shall meet at least once per quarter to discuss various topics pertaining to the regular activities of the Sugar Labs Project and Sugar. (It is expected that more frequent meeting will be required in the early stages of the program.) The minutes to these meetings shall be posted publicly on the Sugar Labs wiki (Oversight Board/Minutes).
The members of the Oversight Board may be removed from the position at any time by a majority vote of the Community Members. Upon the resignation or removal of a member of the Oversight Board, the Community Members shall elect a replacement Community Member to serve on the Oversight Board.
The Oversight Board will elect a single individual to communicate with the Conservancy (the "Representative") and shall notify the Conservancy promptly following the election of a new Representative. The Representative will have the authority to instruct the Conservancy on the Project's behalf on all matters.
The current list of Oversight Board members is on the Oversight Board page.
Election Process
The Sugar Labs membership elects the Oversight Board each August, for terms beginning in September. Members can nominate themselves to run in the election according to each Election's calendar. The election process is overseen by the Membership and Elections Committee, which can be reached at elections at sugarlabs.org.
Decision Panels
The Oversight Board's role is to manage the day-to-day affairs of Sugar Labs and to help the community to build consensus. On the rare occasion of a contentious issue on which no general consensus can be reached, the Oversight Board is responsible for convening a Decision Panel. The Oversight Board will be responsible for determining when a Decision Panel is required and for selecting members for the Decision Panel. Members of the Oversight Board are not permitted to serve on a Decision Panel. A Decision Panel will solicit community input, discuss (in private if they deem it necessary), reach a conclusion internally, and produce a report documenting their conclusion. (Anyone may submit advice to a Decision Panel.) The Oversight Board will review and ratify Decision Panel reports.
Advisory Board
The Advisory Board is made up of organizations and companies that support Sugar Labs. The Advisory Board has no decision-making authority but provides a vehicle for its members to communicate with the Oversight Board and help the Directors guide the overall direction of Sugar and the Sugar Labs Project. The Advisory Board will appoint (up to) three (3) members who will be non-voting attendees of Oversight Board meetings. The Advisory Board will meet up to twice per year.
The Advisory Board consists of representatives from the following Sugar Labs Foundation member corporations and projects.
Advisory board member companies pay an annual fee which helps finance the operations of the Sugar Labs Project.
Special Interest Groups
Special Interest Groups (SIGs) may be established by any member. They can be formed around any topic and, if they prove to be useful, can be designated as official committees. SIGs typically organize themselves as Teams, Projects, or Local Labs.
Referenda
At times an issue may arise that merits gathering consensus from the community. Any member of the Sugar Labs Foundation can suggest a referendum. To be accepted, a request for a referendum must be endorsed by 10% of all of the membership. The overall referendum process is overseen by the Membership and Elections Committee, which can be reached at elections at sugarlabs.org.
A 75% vote of all of the members can override an Oversight Board decision.