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/[email protected]/
[ripe-list] LAST CALL EXTENDED to 18 Feb: Draft Document: RIPE Task Forces - Definition and Guidelines
- Previous message (by thread): [ripe-list] LAST CALL EXTENDED to 18 Feb: Draft Document: RIPE Task Forces - Definition and Guidelines
- Next message (by thread): [ripe-list] Call for Public Comments on the 2021 IANA Performance Matrix Summary Report
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Leo Vegoda
leo at vegoda.org
Sun Feb 20 23:40:19 CET 2022
Hi Denis, On Sun, Feb 20, 2022 at 2:23 PM denis walker <ripedenis at gmail.com> wrote: [...] > This document on Task Forces (TF) is interesting, but one problem is > that it assumes that a TF will always achieve it's goals. But what if > it doesn't? There are many reasons why it may not do so. The goals may > be unrealistic or unachievable. [etc...] One approach we could take is to try and document general process requirements for all the myriad possibilities you raised. Another is to rely on this sentence from ripe-714: "The RIPE chair ensures that the RIPE community functions well." One benefit of relying on the RIPE Chair is that it allows us to rely on whoever fulfills that role to help the TF be as successful as possible. In some cases, that might mean doing something radical, like you suggest. Kind regards, Leo
- Previous message (by thread): [ripe-list] LAST CALL EXTENDED to 18 Feb: Draft Document: RIPE Task Forces - Definition and Guidelines
- Next message (by thread): [ripe-list] Call for Public Comments on the 2021 IANA Performance Matrix Summary Report
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]