Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -56,6 +56,8 @@
56	56	1. The __Technologists Committee__ meets on the third Tuesday of each month
57	57	1. The __Project & Organizational Managers Committee__ meets on the fourth Tuesday of each month
58	58
	59	+* All meetings accessible to read or listen into, but there should be a simple degree of role-based access to contribute. Anyone with an interest can join, but this way each team should have its discussion quality trend up rather than down. The purpose is to have effective scalabilty, yet provide Coordinators a straightforward way to maintain focus.
	60	+
59	59	The monthly calls have their audio streamed externally, and also produce published minutes __with NO attribution__.
60	60
61	61	The OSI-EDU-WG seeks active participation in the Working Committees, at both individual and organizational levels. Committee Participants as well as OSI Board representation are listed in an annex to this Charter. Except for the Chair, no formal relationship with the OSI is required to be a participant in the OSI-EDU-WG.
...	...	@@ -64,15 +64,17 @@
64	64
65	65	* **"Working Committee Coordinator"**:
66	66	** Facilitates maintenance of the Committee's mandate, and operational alignment with the OSI-EDU-WG generally.
67		-** Collaborates with other Team Coordinators in a Steering Committee.
	69	+** The Coordinators of each Working Committee create a Steering Cttee with the Chair of the OSI-EDU-WG
68	68	* **"Working Committee Participant"**:
69	69	** Has been identified as a Participant in an online OSI-EDU-WG forum (i.e. a published record);
70	70	** Speaks in monthly conference call.
71	71	** Requirement for being a Committee Participant is that s/he must work professionally in the discilpline named by each theme, __OR__ may be voted in by working consensus of current team members (all either in favour or neutral, none opposed).
72	72	** Each participant's accession must be ratified by the OSI Board with regard to consistency with FLOW principles, versus conflict of interest.
73		-* **"Working Committee Contributor"**: Identified as a Contributor in the online FLOW-EDU-WG forum; Live audio output and text participation access to the monthly discussion and minutes. Anyone may be a contributor.
74		-* Coordinators of each WG create a Steering Cttee
75		-* All meetings accessible to read or listen into, but there should be a simple degree of role-based access to contribute. Anyone with an interest can join, but this way each team should have its discussion quality trend up rather than down. The purpose is to have effective scalabilty, yet provide Coordinators a straightforward way to maintain focus.
	75	+* **"Working Committee Contributor"**:
	76	+** Identified as a Contributor in the online OSI-EDU-WG forum;
	77	+** Live audio output and text participation access to the monthly discussion and minutes.
	78	+** Anyone may be a contributor.
	79	+
76	76	Meritocracy in team discussions will require sensitivity. The Coordinators might make discrete offline comments to participants or contributors.
77	77	* Ultimately, "good facilitation" depends on a "quality without a name" (C. Alexander)
78	78	* Etherpad will be useful during meetings