Difference between revisions of "Sugar Labs/Governance"
m (fix link to moved page) |
Karensandler (talk | contribs) |
||
Line 12: | Line 12: | ||
===Software Freedom Conservancy=== | ===Software Freedom Conservancy=== | ||
− | Sugar Labs has applied for membership within the [http://conservancy.softwarefreedom.org Software Freedom Conservancy] (SFC). This would place 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 FOSS projects can obtain the benefits of a formal legal structure while keeping themselves focused on software development." | + | Sugar Labs has applied for membership within the [http://conservancy.softwarefreedom.org Software Freedom Conservancy] (SFC). This would place 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 FOSS 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 following *proposed* 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 *proposed* governance model is largely derived from the model used by the Gnome Foundation (Please see [http://foundation.gnome.org/about/ gnome.org/about]). | ||
Line 21: | Line 21: | ||
Sugar Labs shall be governed by an Oversight Board, consisting of seven (7) members, elected annually by the Sugar community—the Sugar Membership. The Oversight Board shall meet twice per month to discuss various topics pertaining to the regular activities of the Sugar Labs Project and Sugar. The minutes to these meetings shall be posted publicly on the Sugar Labs wiki ([[Sugar Labs/OversightBoard/Minutes]]). | Sugar Labs shall be governed by an Oversight Board, consisting of seven (7) members, elected annually by the Sugar community—the Sugar Membership. The Oversight Board shall meet twice per month to discuss various topics pertaining to the regular activities of the Sugar Labs Project and Sugar. The minutes to these meetings shall be posted publicly on the Sugar Labs wiki ([[Sugar Labs/OversightBoard/Minutes]]). | ||
+ | |||
+ | [Note: Is this requirement too stringent to maintain? Consider making the required meeting frequency lower and say instead: The Oversight Board shall meet at least quarterly/monthly to discuss various topics pertaining to the regular activities of the Sugar Labs Project and Sugar. The Oversight Board expects to meet twice per month.] | ||
====Decision Panels==== | ====Decision Panels==== | ||
− | The Oversight Board's role is to manage the | + | 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.) |
+ | |||
+ | [Note: Should the oversight board be able review/ratify the decision? The way this section is written now, the people elected by the members are not able to actively participate in the decision-making process. Why not allow the board to participate or at least ratify the final decision?] | ||
===Advisory Board=== | ===Advisory Board=== | ||
Line 33: | Line 37: | ||
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. | ||
+ | |||
+ | [Note: should the advisory board be allowed to listen in (perhaps but not participate in) the board meetings or otherwise be allowed to elect a representative for participation (voting or nonvoting) in the Oversight Board meetings? Should they have their own schedule/procedure for meetings?] | ||
===Committees=== | ===Committees=== | ||
Line 38: | Line 44: | ||
The Oversight Board is responsible for establishing [[Sugar Labs/Governance/Committees|committees]] as necessary. | The Oversight Board is responsible for establishing [[Sugar Labs/Governance/Committees|committees]] as necessary. | ||
− | Each committee will include one member from the Oversight Board (non-voting), who will server as a recording secretary, and three (3) to five (5) additional members (initially | + | Each committee will include one member from the Oversight Board (non-voting), who will server as a recording secretary, and three (3) to five (5) additional members (initially appointed by the Oversight Board and subsequently elected) from the community. |
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. | 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. | ||
+ | |||
+ | [Note: as with the advisory committee, should we provide some formal way for the SIGs to provide input? For example, SIGs could have representation on the advisory committee or listen in on board meetings.] | ||
===Sugar Labs Membership=== | ===Sugar Labs Membership=== | ||
Line 47: | Line 55: | ||
Any "significant and sustained" contributor to Sugar Labs is eligible for membership. Although it is difficult to specify a precise definition, a contributor generally must have contributed to a non-trivial improvement of the Sugar project or Sugar Labs activity. Contributions may be code, documentation, translations, maintenance of project-wide resources, ''running a Sugar deployment'', or other non-trivial activities which benefit Sugar Labs. Membership eligibility is an individual determination: while contributions made in the course of employment will be considered, they will generally be ascribed to the individuals involved, rather than accruing to all employees of a "contributing" corporation. The Membership and Elections Committee will oversee membership applications (Please apply by sending email to members at sugarlabs.org). | Any "significant and sustained" contributor to Sugar Labs is eligible for membership. Although it is difficult to specify a precise definition, a contributor generally must have contributed to a non-trivial improvement of the Sugar project or Sugar Labs activity. Contributions may be code, documentation, translations, maintenance of project-wide resources, ''running a Sugar deployment'', or other non-trivial activities which benefit Sugar Labs. Membership eligibility is an individual determination: while contributions made in the course of employment will be considered, they will generally be ascribed to the individuals involved, rather than accruing to all employees of a "contributing" corporation. The Membership and Elections Committee will oversee membership applications (Please apply by sending email to members at sugarlabs.org). | ||
+ | |||
+ | [Note: is there an officially list already? Who gets to add contributors and are they ever removed? Is the Membership and Election Committee another committee of the Oversight Board without any voting members from the OB?] | ||
===Sugar Labs Referenda=== | ===Sugar Labs Referenda=== | ||
Line 52: | Line 62: | ||
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 the membership. The overall referendum process is overseen by the Membership and Elections Committee, which can be reached at elections@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 the membership. The overall referendum process is overseen by the Membership and Elections Committee, which can be reached at elections@sugarlabs.org. | ||
+ | [Note: can the membership override the Oversight Board under certain circumstance? For example, a 75% vote of all of the members?] | ||
[[Category:General public]] | [[Category:General public]] |
Revision as of 06:42, 30 June 2008
DRAFT Rules of Governance
Please comment in-line or on the discussion page.
One of the challenges that free and open-source projects face is the impact of governance on their community members: while FOSS 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 has applied for membership within the Software Freedom Conservancy (SFC). This would place 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 FOSS 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 following *proposed* governance model is largely derived from the model used by the Gnome Foundation (Please see gnome.org/about).
Oversight Board
Sugar Labs cannot have directors, since that attribution within the SFC is already taken to mean the board members of the Conservancy itself. Therefore, 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 annually by the Sugar community—the Sugar Membership. The Oversight Board shall meet twice per month to discuss various topics pertaining to the regular activities of the Sugar Labs Project and Sugar. The minutes to these meetings shall be posted publicly on the Sugar Labs wiki (Sugar Labs/OversightBoard/Minutes).
[Note: Is this requirement too stringent to maintain? Consider making the required meeting frequency lower and say instead: The Oversight Board shall meet at least quarterly/monthly to discuss various topics pertaining to the regular activities of the Sugar Labs Project and Sugar. The Oversight Board expects to meet twice per month.]
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.)
[Note: Should the oversight board be able review/ratify the decision? The way this section is written now, the people elected by the members are not able to actively participate in the decision-making process. Why not allow the board to participate or at least ratify the final decision?]
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 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.
[Note: should the advisory board be allowed to listen in (perhaps but not participate in) the board meetings or otherwise be allowed to elect a representative for participation (voting or nonvoting) in the Oversight Board meetings? Should they have their own schedule/procedure for meetings?]
Committees
The Oversight Board is responsible for establishing committees as necessary.
Each committee will include one member from the Oversight Board (non-voting), who will server as a recording secretary, and three (3) to five (5) additional members (initially appointed by the Oversight Board and subsequently elected) from the community.
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.
[Note: as with the advisory committee, should we provide some formal way for the SIGs to provide input? For example, SIGs could have representation on the advisory committee or listen in on board meetings.]
Sugar Labs Membership
The Sugar Labs membership consists of all the contributors to the Sugar project. Members can run for election to the Oversight Board, vote in the elections for the Oversight Board, and suggest referenda.
Any "significant and sustained" contributor to Sugar Labs is eligible for membership. Although it is difficult to specify a precise definition, a contributor generally must have contributed to a non-trivial improvement of the Sugar project or Sugar Labs activity. Contributions may be code, documentation, translations, maintenance of project-wide resources, running a Sugar deployment, or other non-trivial activities which benefit Sugar Labs. Membership eligibility is an individual determination: while contributions made in the course of employment will be considered, they will generally be ascribed to the individuals involved, rather than accruing to all employees of a "contributing" corporation. The Membership and Elections Committee will oversee membership applications (Please apply by sending email to members at sugarlabs.org).
[Note: is there an officially list already? Who gets to add contributors and are they ever removed? Is the Membership and Election Committee another committee of the Oversight Board without any voting members from the OB?]
Sugar 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 the membership. The overall referendum process is overseen by the Membership and Elections Committee, which can be reached at elections@sugarlabs.org.
[Note: can the membership override the Oversight Board under certain circumstance? For example, a 75% vote of all of the members?]