Difference between revisions of "Oversight Board/Next meeting"

From Sugar Labs
Jump to navigation Jump to search
(25 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
=== Next meeting===
 
=== Next meeting===
  
Friday, 2019-04-05 at 20:00 UTC
+
* Wednesday, 2020-06-10 at 20:00 UTC, (per agreed motion 2020-06, "meet every two weeks"),
 +
* on Jitsi,
  
 
==== Agenda items ====
 
==== Agenda items ====
  
Please write to slobs at lists dot sugarlabs dot org, or an oversight-board member to add topics for the meeting.
+
Our agenda is typically negotiated as first item of business in the meeting. Add topics by either;
  
* Any pending motions from e-mail,
+
* write to sugar-devel and slobs at lists dot sugarlabs dot org (the most transparent method), or;
* Any reports from project representative (Conservancy liaison),
+
* write to slobs at lists dot sugarlabs dot org (a transparent method), or;
* Any reports from Membership and Elections Committee,
+
* write to a member of the oversight board (a non-transparent method).
* Any reports from Ombudsman,  
+
 
* Discussion of goals,
+
Standing agenda items;
 +
 
 +
* pending motions from e-mail,
 +
* reports from project representative (Conservancy liaison),
 +
* reports from Ombudsman,
 +
* reports from project teams, e.g. administrators of Google Code-in or Google Summer of Code,
 +
* discussion of goals,

Revision as of 19:25, 27 May 2020

Next meeting

  • Wednesday, 2020-06-10 at 20:00 UTC, (per agreed motion 2020-06, "meet every two weeks"),
  • on Jitsi,

Agenda items

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

Standing agenda items;

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