This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ipv6-wg@ripe.net/
[ipv6-wg] Discussion period for co-chair selection until 20100208
- Previous message (by thread): [ipv6-wg] Discussion period for co-chair selection until 20100208
- Next message (by thread): [ipv6-wg] Discussion period for co-chair selection until 20100208
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
David Kessens
david.kessens at nsn.com
Wed Feb 10 01:36:50 CET 2010
Kostas, On Mon, Feb 08, 2010 at 02:45:50PM +0200, Kostas Zorbadelos wrote: > > as a relatively newcomer to this community, I would like to learn more about > the duties and responsibilities of a WG [co]chair. Please see below in the attached draft document for co-chair responsibilities. Note that this a draft document that contains some known issues and is here and there out of date but it should give you an idea on what co-chairs are supposed to do. Let me know if you have any questions, David Kessens --- Version: 2.4: May 19 2009 Working Group Chair Job Description 1) Introduction The purpose of this document is to describe the role, responsibility and expectations associated with RIPE Working Group (WG) Chairs. The document is divided into the following sections: - WG Chairs and Co-Chairs - Creating WG Charters - Updating WG charters - Policy Development Process (PDP) Responsibilities - RIPE Meeting Responsibilities 2) Working Group Chairs and Co-Chairs WG Chairs and Co-Chairs should always make it clear whether they speak on behalf of themselves, the organisations they work for or the WG for which they are Chair or Co-Chair. RIPE WGs have two different ways of dividing up the responsibilities of the WG Chair(s): WG Chair Model and Equal Co-Chair Model. The model that is used depends upon the specific needs, history and set-up of a particular WG. i) WG Chair Model In this model, a WG Chair has overall responsibility for the WG and can be supported by Co-Chairs. These Co-Chairs can assist with general WG support and can deputise for the WG Chair if he/she is not able to attend a RIPE Meeting. ii) Equal Co-Chair Model In this model, the Co-Chairs share the responsibility for PDP and RIPE Meeting activities. The Co-Chairs act together to make any formal statements (for example on policy development) that are relevant to their WG. For each RIPE Meeting, one of the Co-Chairs serves as the primary contact for the WG and for session organisational matters. 3) Creating Working Group Charters i) Working Group Created from a Task Force A WG usually emerges from a Task Force. In this case, the procedure for creating the WG Charter is as follows: The head of the Task Force creates the Charter for the new WG in consultation with other members of the Task Force. Once this has been agreed, and approved by the RIPE Chair, the Charter for the new WG is officially recognised. ii) New Working Group Emerging from an Existing WG If a new WG emerges from an existing WG then the Charter for the new WG should be drawn up by the Chairs and Co-Chairs of the new and existing WG. Once this has been agreed, and approved by the RIPE Chair, the Charter for the new WG is officially recognised. 4) Updating Working Group Charters If a WG Chair needs to update the WG charter, he/she needs to have the text approved by the WG Co-Chairs before presenting the revised charter to the WG for their approval via the WG mailing list and/or at a RIPE Meeting. 5) Policy Development Process (PDP) Responsibilities WG Chairs are expected to: - Stay up-to-date with all phases of a policy proposal relevant to their WG - Follow discussions on the relevant WG mailing list(s) - Guide mailing list discussions as appropriate - Take charge of PDP milestone decisions relevant to their WG - Ensure PDP milestone decisions keep to the timeframe as described in the RIPE PDP Document - Make a collective, final decision supported by a reasonable level of awareness as to whether a particular policy proposal has received consensus - Inform the RIPE NCC when a policy proposal has received consensus and should become a RIPE Document Note - In a WG with an equal Co-Chair model (see 2(i)), these responsibilities are shared between the Co-Chairs. 6) RIPE Meetings Responsibilities i) General/Plenary WG Chairs are expected to: - Attend RIPE Meetings or send a Co-Chair as their deputy - Help develop the RIPE Meeting Plenary Agenda through the <eofcoord at ripe.net> mailing list - Lead a Plenary session as agreed in advance of the meeting and pass on any action points that are decided in this Plenary session to the relevant WG Note - In a WG with an equal Co-Chair model (see 2(i)), these responsibilities are shared between the Co-Chairs. ii) Working Group Specific WG Chairs are expected to: - Solicit relevant presentations for the WG session - Post a draft agenda for their WG session (at least 2-3 weeks before a RIPE Meeting where possible) - Lead the WG session and encourage active participation - Present a short summary (including actions and highlights) from their WG in the closing Plenary session at the RIPE Meeting - Review and approve the minutes from their WG session (4 - 6 weeks-) - Attend WG Chair lunches during RIPE Meetings - Attend WG Chair meetings between RIPE Meetings - Update the action list of their WG after the RIPE Meeting Note - In a WG with an equal Co-Chair model (see 2(i)), one Co-Chair takes overall responsibility for these activities at a particular RIPE Meeting. ---
- Previous message (by thread): [ipv6-wg] Discussion period for co-chair selection until 20100208
- Next message (by thread): [ipv6-wg] Discussion period for co-chair selection until 20100208
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]