Sugar Labs/Governance

Team Home   ·   Join   ·   Contacts   ·   Resources   ·   FAQ   ·   Vision   ·   To Do   ·   Meetings

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).

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.

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.

Officers and coordinators

The Oversight Board is responsible for appointing officers with executive functions. Any Sugar Labs member can be appointed by the board. Existing officers include:

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.

Note: The contents of this section have been transcluded from another page, Sugar Labs/Members:

Sugar Labs Membership

The Sugar Labs members list consists of most of 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.

Membership applications are overseen by the Oversight Board.

Applying for membership

All submissions MUST be sent via email to members at sugarlabs.org. Submissions sent to other email addresses or sent after the deadline will not be processed for the year's election. Someone on the Oversight Board will reply to your query within 2 business days. If you don't get a reply after a week, please contact committee members individually.

In your email, please include:

  • Your name,
  • Your Matrix handle, Wiki username, and/or GitHub username,
  • A description of your contribution to Sugar Labs, links are preferable.

Currency assurance policy

In order to ensure that the Sugar Labs Membership list is reflective of the current status of the project and its participants, once a year members will be asked to confirm that they still wish to be a Sugar Labs Member. If this request bounces, or if a request has not been replied to after it has been a) resent, b) checked for a more current email address, and c) six months have passed, the member will be sent a removal notice with an invitation to reapply.

The most recent currency review was in June 2017.

Members List

This is our Sugar Labs/Members/List.

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 all of the membership. The overall referendum process is overseen by the Membership and Elections Committee, which can be reached at elections@sugarlabs.org.

A 75% vote of all of the members can override an Oversight Board decision.

Subpages