Difference between revisions of "Oversight Board/Next meeting"

From Sugar Labs
Jump to navigation Jump to search
(48 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
=== Next meeting===
 
=== Next meeting===
  
Friday, 2018-01-05 at 19 UTC
+
* Wednesday, 2020-06-10 at 20:00 UTC, (per agreed motion 2020-06, "meet every two weeks"),
 +
* on Jitsi,
  
Email slobs at lists dot sugarlabs dot org to propose a topic queue to be brought up.
+
==== 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 contact an oversight-board member to add topics to be considered for the meeting.
+
Standing agenda items;
  
* GCI report
+
* pending motions from e-mail,
* GSoC 2018
+
* reports from project representative (Conservancy liaison),
* Devin Ulibarri workshops
+
* reports from Ombudsman,
* Replacing Bertf
+
* reports from project teams, e.g. administrators of Google Code-in or Google Summer of Code,
* Discussion of proposal to have motions translated into Spanish (and other languages)
+
* discussion of goals,
* Discussion of process for finding/appointing a finance manager
 

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,