Sugar Labs/Governance

From Sugar Labs
< Sugar Labs
Revision as of 18:53, 9 November 2012 by FGrose (talk | contribs) (category)
Jump to navigation Jump to search

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


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.

Delegates and coordinators

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


The mission of the oversight board is to ensure that the Sugar Labs community has clarity of purpose and the means to collaborate in achieving its goals. (See Sugar_Labs/Governance)

The Oversight Board

The current oversight board members are:


  • slobs AT - A private list for the Oversight Board members; all emails that do not ask to be private (or are not obviously intended to be private) will be forwarded to the publicly archived IAEP list.
  • ombudsman AT - A neutral party with whom anyone (member or non-member) may consult privately. The ombudsman will report to the Oversight Board and the community each month that a consultation occurs. Patrica Escauriza is our Ombudsman. Feel free to contact her in confidence regarding any issues you may have with the oversight board or the community.


Next meeting

  • Wednesday, 2022-02-02 at 19:30 UTC, (per agreed motion 2020-06, "meet every two weeks"),
  • on Matrix ( room: Sugar)

Agenda items

Current draft is published at (which will later become the minutes for the meeting).

Our agenda is typically negotiated as first item of business in the meeting. Add topics by either;

  • write to sugar-devel and slobs at lists dot sugarlabs dot org (the most transparent method), or;
  • write to slobs at lists dot sugarlabs dot org (a transparent method), or;
  • write to a member of the oversight board (a non-transparent method).
  • editing the wiki page for the agenda yourself (before the meeting).

Standing agenda items;

  • pending motions from e-mail,
  • reports from Ombudsman,
  • reports from project teams, e.g. administrators of Google Code-in or Google Summer of Code,
  • discussion of goals,

Previous Meetings

Minutes from previous meeting can be found at Oversight Board/Minutes. Logs can be found at [1].


Board actions and decisions are found at Oversight Board/Decisions.

Additional roles within Sugar Labs

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

Former Board Members

We'd like to thank the follow former board members for their contributions:



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.

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

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