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 17:55:25 CET 2021
Common sense for me is on the other way around. A TF with 5 people is much better than just 4. Even 10 people, maybe not 25. Common sense is to define up-front what is the allowed membership, not afterwards having a discussion about that and then making an arbitrary decision, because the original email on the call for the TF was non crystal clear. Furthermore, it seems, it was not just the chairs decision? It is interesting to see that, unless I missed it, there is nothing about that discussion in the minutes (I read this morning the emails in the list for September-October-November). So, if there was such discussion in the TF, then it was not minuted (so not so transparent). So how to trust the rest of the minutes, if that's the case? I recall also that the archive of the mailing list was open only once I asked for it. So the goal of transparency was not there from day 1. El 26/3/21 17:33, "ripe-list en nombre de Mirjam Kuehne" <ripe-list-bounces at ripe.net en nombre de mir at zu-hause.nl> escribió: Hi Alex, On 26/03/2021 15:55, Alex de Joode wrote: > On Fri, 26-03-2021 13h 38min, Mirjam Kuehne <mir at zu-hause.nl> wrote: > > 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 > <https://www.ripe.net/ripe/mail/archives/coc-tf/2020-November/000080.html> > > Thank Mirjam, > > I > <https://www.ripe.net/ripe/mail/archives/coc-tf/2020-November/000080.html>'m > a bit curious about the word 'empowered'. > > Does that mean that a TF can only do what is explicitly allowed, and > there is no room for 'common sense'/'filling in the blancs' ? > > There is always room for common sense in RIPE. The request was discussed by the TF and as a result, the TF communicated that the membership of the TF had been decided and that it wouldn't make sense at that point to add more members as the work was well underway. In addition to that the TF took a number of steps to increase transparency and to make it easier to contribute to the work of the TF. Kind regards, Mirjam ********************************************** 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 ]