You are here: Home > Publications > RIPE Document Store > Working Group Chair Job Description and Procedures

Changes to Working Group Chair Job Description and Procedures

Legend (+) Added (-) Deleted
Changed Tag Added Tag Deleted
ripe-542: ripe-692: RIPE Working Group Chair Job Description and Procedures
delete: <p> delete: <b> insert: <h2>

1. Introduction delete: </b> delete: </p> insert: </h2>

The purpose of this document is to describe the role, responsibility responsibilities, and expectations associated with RIPE Working Group (WG) Chairs. delete: </p> delete: <p>

The document is divided into the following sections:

  • delete: <p> WG chairs WG Chairs and co-chairs delete: </p> delete: </li> delete: <li> delete: <p> insert: </li>
  • insert: <li>
  • Creating WG charters delete: </p> delete: </li> delete: <li> delete: <p> insert: </li>
  • insert: <li>
  • Updating WG charters delete: </p> delete: </li> delete: <li> delete: <p> insert: </li>
  • insert: <li>
  • Policy Development Process (PDP) responsibilities delete: </p> delete: </li> delete: <li> delete: <p> insert: </li>
  • insert: <li>
  • RIPE Meeting responsibilities delete: </p>
delete: <p> delete: </p> delete: <p> delete: <b> insert: <h2>

2. Working Group Chairs and Co-Chairs delete: <br /> delete: </b> delete: </p> delete: <p> 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. delete: </p> delete: <p> 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. delete: </p> delete: <p> delete: </p> delete: <p> i) WG Chair Model delete: </p> delete: <p> insert: </h2>

insert: <p>

RIPE Working Groups operate under a co-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. delete: </p> delete: <p> delete: </p> delete: <p> ii) Equal Co-Chair Model delete: </p> delete: <p> In this model, this, the co-chairs share the responsibility for RIPE Policy Development Process (PDP) and RIPE Meeting activities. all tasks involved in chairing their working group. 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 insert: </p>

insert: <p>

A WG has either 2 or 3 co-chairs. insert: </p>

insert: <p>

When participating in RIPE discussions, WG Chairs and co-chairs serves as the primary contact for the WG and for session organisational matters. delete: </p> delete: <p> delete: </p> delete: <p> The number of chairs and co-chairs of each WG should not exceed three (3). delete: </p> delete: <p> delete: </p> delete: <p> delete: <b> endeavour to make it clear whether they speak on behalf of themselves, the organisations they work for, or the WG for which they are co-chair. insert: </p>

insert: <h2>

3. Creating Working Group Charters delete: </b> delete: </p> delete: <p> insert: </h2>

insert: <h3>

i) Working Group created Created from a Task Force delete: </p> insert: </h3>

A WG usually emerges from a Task Force. In this case, the procedure for creating the WG Charter 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.

delete: <p> delete: </p> delete: <p> insert: <h3>

ii) New Working Group Emerging from an Existing WG delete: </p> insert: </h3>

If a new WG emerges from an existing WG, then the chairs and co-chairs of both the new and existing WG should draw up the charter for the new WG. Once this has been agreed, and approved by the RIPE Chair, the charter for the new WG is officially recognised.

delete: <p> delete: </p> delete: <p> delete: <b> insert: <h2>

4. Updating Working Group Charters delete: </b> delete: </p> insert: </h2>

If a WG Chair needs to update the WG charter, he/she needs to they must 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. delete: </p> delete: <p> delete: </p> delete: <p> delete: <b> list. The RIPE Chair has final approval of the new charter. insert: </p>

insert: <h2>

5. Policy Development Process (PDP) Responsibilities delete: </b> delete: </p> insert: </h2>

WG Chairs are expected to:

  • delete: <p> Stay up-to-date with all phases of a policy proposal relevant to their WG delete: </p> delete: </li> delete: <li> delete: <p> insert: </li>
  • insert: <li>
  • Follow discussions on the relevant WG mailing list(s) delete: </p> delete: </li> delete: <li> delete: <p> insert: </li>
  • insert: <li>
  • Guide mailing list discussions as appropriate delete: </p> delete: </li> delete: <li> delete: <p> insert: </li>
  • insert: <li>
  • Take charge of PDP milestone decisions relevant to their WG delete: </p> delete: </li> delete: <li> delete: <p> insert: </li>
  • insert: <li>
  • Ensure PDP milestone decisions keep to the timeframe as described in the document delete: <b> “Policy insert: <strong> " insert: </strong> insert: <a href="http://www.ripe.net/publications/docs/pdp" data-linktype="external" data-val="http://www.ripe.net/publications/docs/pdp"> insert: <strong> Policy Development Process in RIPE” (ripe-500) delete: </b> delete: </p> delete: </li> delete: <li> delete: <p> Make a collective, final decision supported by a reasonable level of awareness as to whether a particular RIPE insert: </strong> insert: </a> insert: <strong> " insert: </strong> insert: </li>
  • insert: <li>
  • Inform the RIPE NCC when a policy proposal has received consensus delete: </p> delete: </li> delete: <li> delete: <p> Inform the RIPE NCC when a policy proposal has received consensus and should become a RIPE Document delete: </p>

delete: <i> Note – In a WG with an equal co-chair model [see 2(i)], that these responsibilities are shared between the co-chairs. delete: </i> delete: </p> delete: <p> delete: </p> delete: <p> delete: <b> insert: </p>

insert: <h2>

6. RIPE Meetings Meeting Responsibilities delete: </b> delete: </p> delete: <p> insert: </h2>

insert: <h3>

i) General/Plenary delete: </p> insert: </h3>

WG Chairs are expected to:

  • delete: <p> Attend RIPE Meetings or delete: <b> insert: <strong> ensure that a co-chair attends the meeting delete: </b> delete: </p> delete: </li> delete: <li> delete: <p> 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 delete: </p> insert: </strong>
delete: <p> delete: <i> Note – In a WG with an equal co-chair model [see 2(i)], these responsibilities are shared between the co-chairs. delete: </i> delete: </p> delete: <p> delete: </p> delete: <p> insert: <h3>

ii) Working Group Specific delete: </p> delete: <p> WG chairs insert: </h3>

insert: <p>

WG Chairs are expected to:

  • delete: <p> Solicit relevant presentations content for the WG session delete: </p> delete: </li> delete: <li> delete: <p> insert: </li>
  • insert: <li>
  • Post a draft agenda for their WG session (at least 2-3 weeks before a RIPE Meeting where possible) delete: </p> delete: </li> delete: <li> delete: <p> insert: </li>
  • insert: <li>
  • Lead the WG session and encourage active participation delete: </p> delete: </li> delete: <li> delete: <p> insert: </li>
  • insert: <li>
  • Review and approve the minutes from their WG session (4-6 weeks) delete: </p> delete: </li> delete: <li> delete: <p> insert: </li>
  • insert: <li>
  • Attend WG chair Chair lunches during RIPE Meetings delete: </p> delete: </li> delete: <li> delete: <p> insert: </li>
  • insert: <li>
  • Attend WG chair Chair meetings between RIPE Meetings delete: </p> delete: </li> delete: <li> delete: <p> if needed insert: </li>
  • insert: <li>
  • Update the action list of their WG after the RIPE Meeting delete: </p> delete: </li> delete: <li> delete: <p> insert: </li>
  • insert: <li>
  • Approach the RIPE Chair and the EOF Coordinator with any requests to fund a speaker's attendance at a RIPE Meeting. If the request for funding is deemed appropriate by the RIPE Chair and the EOF Coordinator, Chair, the RIPE Chair will request funding from the RIPE NCC Managing Director. The RIPE NCC Managing Director may or may not approve such a request at his their own discretion. delete: </p> insert: </li>
  • insert: <li>
  • Develop, maintain, and implement a procedure for the selection and removal of WG Chairs for the WG.

delete: <i> Note – In a WG These responsibilities may be split between co-chairs. insert: </p>

insert: <h2>

Changes Since ripe-542 insert: </h2>

insert: <p>

Minor: insert: </p>

insert: <ul>
    insert: <li>
  • Changed to Oxford comma, because we love clarity. insert: </li>
  • insert: <li>
  • Converted to gender-neutral pronouns (they). insert: </li>
  • insert: <li>
  • Updated reference to RIPE PDP. insert: </li>
  • insert: <li>
  • Chairs get "content" not "presentations" for WG sessions. insert: </li>
  • insert: <li>
  • Added "if needed" to attending WG Chairs meetings between RIPE Meetings. insert: </li>
  • insert: </ul>
insert: <p>

Major: insert: </p>

insert: <ul>
    insert: <li>
  • Eliminated the chair with an equal optional co-chair model [see 2(i)], one co-chair takes overall model. insert: </li>
  • insert: <li>
  • Added RIPE Chair as final approval of new charters. insert: </li>
  • insert: <li>
  • Changed new charter approval only to mailing list (was "and/or at a RIPE Meeting"). insert: </li>
  • insert: <li>
  • Noted that we no longer have the WG Chair responsibility for these activities at a particular RIPE Meeting. delete: </i> delete: </p> delete: <p> delete: </p> delete: <p> delete: <i> delete: <br /> delete: </i> delete: </p> to act as final approval on all new policies (outside of their own WG). insert: </li>
  • insert: <li>
  • Removed responsibility to lead Plenary sessions, since the PC now does that. insert: </li>
  • insert: <li>
  • Removed references to the EOF Coordinator since that role does not really exist now. insert: </li>
  • insert: <li>
  • Added responsibility for WG Chairs for WG selection procedure. insert: </li>
  • insert: </ul>
insert: <h2>

Approval of Document insert: </h2>

insert: <p>

This document was approved by the RIPE Chair. insert: </p>

RIPE Working Group Chair Job Description and Procedures
RIPE Documents Search