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/ripe-list@ripe.net/
[ripe-list] Draft Document: RIPE Task Forces - Definition and Guidelines - v4
- Previous message (by thread): [ripe-list] Draft Document: RIPE Task Forces - Definition and Guidelines - v4
- Next message (by thread): [ripe-list] Draft Document: RIPE Task Forces - Definition and Guidelines - v4
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Maximilian Wilhelm
max at rfc2324.org
Fri May 27 18:41:09 CEST 2022
Hi folks, I second what Markus said, this is great! Thanks to all people who contributed to that document! Best, Max Anno domini 2022 Markus de Brün scripsit: > Niall, > > thank you for the update. I find version 4 to be well written, easier to > comprehend and also more complete (with regards to its content) than the > previous versions. I support the document. > > The section "Output" contains a typo, i think: > "a task force identify alternative approaches" -> "a task force identifies > alternative approaches" > > Regards, > Markus > > > On 09.05.22 15:50, Niall O'Reilly wrote: > > On 12 Apr 2022, at 15:28, Niall O'Reilly wrote: > > > > > I also see that the text can be made clearer, and will revise it > > > accordingly before > > > making a last call for comments. > > > > The revised text is now available here: > > [https://www.ripe.net/publications/docs/ripe-documents/other-documents/ripe-task-forces-definition-and-guidelines-v4](https://www.ripe.net/publications/docs/ripe-documents/other-documents/ripe-task-forces-definition-and-guidelines-v4) > > > > > > Although I don’t believe there are any material changes, > > the result of revision for clarity and readability is that > > the new text is noticeably different from the previous draft. > > For this reason, I feel that it would be premature to make > > a last call just yet (as was originally intended). > > > > Please take the opportunity to review the latest (v4) draft, > > and to comment, if you wish, before 06:00 UTC on Monday, > > 30 May 2022. > > > > I expect to announce a 2-week last-call period shortly after > > this deadline. > > > > I am aware that acknowledgements need to be added, and plan to > > arrange to have these included during the last-call period. > > > > I am glad to take this opportunity to thank all of the following > > people for their comments and suggestions: Nigel Titley, Desiree > > Miloshevic, Mirjam Kühne, Peter Koch, Daniel Karrenberg, Randy > > Bush, Sander Steffann, Jordi Palet Martínez, Gert Döring, Kurtis > > Lindqvist, and especially Boris Duval and Antony Gollan for their > > excellent and indefatigable editorial support. > > > > Best regards, > > > > Niall O’Reilly > > > > > -- > > To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/ -- Fortschritt bedeutet, einen Schritt so zu machen, daß man den nächsten auch noch machen kann.
- Previous message (by thread): [ripe-list] Draft Document: RIPE Task Forces - Definition and Guidelines - v4
- Next message (by thread): [ripe-list] Draft Document: RIPE Task Forces - Definition and Guidelines - v4
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]