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] [diversity] Updated Draft RIPE Code of Conduct Published for Community Review
- Previous message (by thread): [ripe-list] [diversity] Updated Draft RIPE Code of Conduct Published for Community Review
- Next message (by thread): [ripe-list] [diversity] Updated Draft RIPE Code of Conduct Published for Community Review
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
JORDI PALET MARTINEZ
jordi.palet at consulintel.es
Fri Mar 26 13:50:27 CET 2021
Hi Mirjam, The email sent to the list on sept. 8th, was crystal clear "*Please* contact us before 15 September 2020". Your email doesn't say "if you don't tell us before 15th September, you will be excluded from the TF". And even something like that, will be surprising to me, but could be acceptable. If you have 25 volunteers, I will understand that, but if you have 4 members, it doesn't make any sense. For whatever reasons I only followed that later on, when preparing for the RIPE81, but as said your email is not excluding anyone to participate *after* any date. Regards, Jordi @jordipalet El 26/3/21 13:38, "ripe-list en nombre de Mirjam Kuehne" <ripe-list-bounces at ripe.net en nombre de mir at zu-hause.nl> escribió: Dear all, Just to clarify the process we used to form the CoC TF: During the plenary at RIPE 81 and in an email I sent to the ripe-list on 8 September 2020 I asked for volunteers. Before the deadline specified in that email, four volunteers stepped forward. Together with two RIPE NCC support staff, the TF was formed and was announced to the ripe-list on 23 September 2020. On 25 October 2020 Jordi contacted the TF and asked to be added. Please find more details in the timeline below for reference. The TF mail archives are public and all meetings are minuted and published on the TF mailing list (linked from the TF page: https://www.ripe.net/participate/ripe/tf/code-of-conduct-task-force). Kind regards, Mirjam Kühne RIPE Chair ====== 08 Sep 2020: Open call for volunteers to serve on TF, transparently setting deadline https://www.ripe.net/ripe/mail/archives/ripe-list/2020-September/001959.html 15 Sep 2020: Deadline for volunteers to come forward 17 Sep 20020: RIPE Chair thanks the four volunteers and charges them to set about their work 18 Sep 2020: Code of Conduct Task Force sets to work https://www.ripe.net/ripe/mail/archives/coc-tf/2020-September/000000.html 23 Sep 2020: Announcing CoC TF to ripe-list https://www.ripe.net/ripe/mail/archives/coc-tf/2020-October/000066.html 25 Oct 2020: Request received to join TF https://www.ripe.net/ripe/mail/archives/coc-tf/2020-October/000066.html 06 Nov 2020: TF meets and considers latecomer's request 09 Nov 2020: TF Chair advises latecomer that TF is not empowered to expand its membership, explains the arrangements to be made for transparency, and encourages latecomer to contribute to the work of the TF by posting to the TF mailing list. https://www.ripe.net/ripe/mail/archives/coc-tf/2020-November/000080.html ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.
- Previous message (by thread): [ripe-list] [diversity] Updated Draft RIPE Code of Conduct Published for Community Review
- Next message (by thread): [ripe-list] [diversity] Updated Draft RIPE Code of Conduct Published for Community Review
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]