Difference between revisions of "Oversight Board/Next meeting"

From Sugar Labs
Jump to navigation Jump to search
(30 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
=== Next meeting===
 
=== Next meeting===
  
Friday, 2019-02-01 at 20:00 UTC
+
* Wednesday, 2020-06-10 at 20:00 UTC, (per agreed motion 2020-06, "meet every two weeks"),
 +
* on Jitsi,
  
* (The March 2019 meeting is changed to 19:00 UTC for that meeting only).
+
==== Agenda items ====
  
==== 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).
  
Please write to slobs at lists dot sugarlabs dot org, or an oversight-board member to add topics for the meeting.
+
Standing agenda items;
  
* Receive report from Membership and Elections Committee,
+
* pending motions from e-mail,
* Receive report from Google Code-in project team, motion 2018-08,
+
* reports from project representative (Conservancy liaison),
* Remake Music,
+
* reports from Ombudsman,
* Marketing update,
+
* reports from project teams, e.g. administrators of Google Code-in or Google Summer of Code,
* SCALE 17x,
+
* discussion of goals,
* Discussion of 2019 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,