Dear working group. We've received no comments from the working group on the updated policy. However, we have been in discussion with the RIPE Chair Team to improve this further and align with ripe-861. While there are no major changes, we're opening a new comment period until August 6. Two further suggestions came up, which we want to keep outside of the scope of this process change, but mention for you to think about for the future: - Should we have term limits? For example, in some WGs a chair can serve two consecutive terms after which they need to take a break of at least one term. - Should we have a removal clause, to remove a non-functioning chair? The security WG process has an example. Thanks to the RIPE Chair team for working on this with us! Sasha (for all co-chairs) === RIPE Open Source WG Chair Selection Process: 1. Number of Co-Chairs and Terms The Open Source WG will have two or three co-chairs. Each chair serves a three-year term. Terms must be staggered to ensure continuity (with three co-chairs, no more than two terms may end in the same year). If staggering is lost due to a resignation or unexpected changes, the WG may define a different term length to restore staggering. 2. Chair Requirements A candidate for co-chair must meet the following requirements: 2.1 The candidate has attended more than one RIPE Meeting in person and is familiar with RIPE processes and community expectations (e.g. by having studied the RIPE guide for new working group chairs and completing the RIPE NCC Academy working group chair course). 2.2. The candidate commits to attending as many RIPE Meetings as possible in person while serving as co-chair. 2.3. The candidate will attend the upcoming RIPE Meeting (either in person or online) where the selection process will take place. 3. Call for Chair Candidates Two months before every autumn RIPE meeting, those chair(s) whose term does not end (the remaining chairs) will issue a call for candidates for any position with a term ending that year. The nomination period will be 21 days. Candidates must confirm that they satisfy the requirements listed in section 2 above. Volunteers are asked to contact the remaining WG chairs directly ("off-list"). An incumbent follows the same process. 4. Selection Process 4.1. The remaining WG chairs announce all candidates to the list at the same time, after which all candidates have a chance to introduce themselves (in writing) to the working group. The remaining WG chairs will then ask the WG for feedback (ideally substantive feedback will be provided about why a candidate is being supported). 4.2. The remaining WG chairs evaluate the feedback and determine the candidate who received the most support. They then announce that candidate during the next RIPE Meeting so that the WG can give final approval. 4.3. If the WG and the WG chairs cannot clearly determine the preferred candidate, the RIPE Chair Team makes the final decision. 4.4. In any case, the RIPE Chair Team will oversee the process and formally confirm that it has been followed properly. 5. Issues Not Covered Any issues not covered here will be decided by WG consensus during a RIPE Meeting. When the WG is unable to reach consensus, the matter will be referred to the RIPE Chair Team, whose decision shall be final.