Difference between revisions of "Oversight Board/Next meeting"

From Sugar Labs
Jump to navigation Jump to search
(→‎Agenda items: The request was made on 4 oct, 2017)
 
(97 intermediate revisions by 6 users not shown)
Line 1: Line 1:
 
=== Next meeting===
 
=== Next meeting===
  
Friday, 2017-11-03 at 19 UTC
+
* Wednesday, 2024-12-04 at 19:30 UTC, (per agreed motion 2020-06, "meet every two weeks"),
 
+
* on Matrix ([https://matrix.to/#/#sugar:matrix.org matrix.org room: Sugar])
Email slobs at lists dot sugarlabs dot org to propose a topic queue to be brought up.
 
  
 
==== Agenda items ====
 
==== Agenda items ====
  
Please contact an oversight-board member to add topics to be considered for the meeting.
+
Standing agenda items;
  
* 2017-2019 Elections Report and Welcome to new Board members
+
* pending motions from e-mail,
* Election of new Sugar Labs representative
+
* reports from Ombudsman,
* Discussion on directions to Conservancy to announce the new Board members
+
* reports from project teams, e.g. administrators of Google Code-in or Google Summer of Code,
* Discussion on Sugar Labs financial report and strategies to follow for the next period
+
* discussion of goals,
* Discussion of "process" (and "guidelines") for requesting travel advances
 
* Discussion of "guidelines" for external programs such as GCI, GSoC, Outreachy, etc.
 
* Discussion of "protocols" for internal teams such as Devel, Design, Localization, etc.
 
* Discussion of proposal to have motions translated into Spanish (and other languages)
 
* Discussion of process for finding/appointing a finance manager
 
* Report by Ombudsman about the Code of Conduct Arbitration requested by a member on October 4, 2017
 
* Follow up on Google Code In Administrators and Mentors
 

Latest revision as of 14:19, 20 November 2024

Next meeting

  • Wednesday, 2024-12-04 at 19:30 UTC, (per agreed motion 2020-06, "meet every two weeks"),
  • on Matrix (matrix.org room: Sugar)

Agenda items

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,