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] [diversity] Two Documents from the Code of Conduct Task Force
- Previous message (by thread): [ripe-list] [diversity] Two Documents from the Code of Conduct Task Force
- Next message (by thread): [ripe-list] [diversity] Two Documents from the Code of Conduct Task Force
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Gert Doering
gert at space.net
Thu Sep 15 20:29:44 CEST 2022
Hi, On Wed, Sep 14, 2022 at 07:03:29PM +0200, Vesna Manojlovic wrote: > This is a process performed by volunteers, who have the benefit of the > community at heart. Please consider volunteering, since you seem to be > very passionate about justice and fairness. Nothing here ensures that the CoC enforcement team will continue to be manned by positive and caring individuals. When this was presented first time, my thought was "this looks more like a band seeking revenge", and I stated so (and was yelled at). I do feel very much at home in the RIPE community, but if we institute a system without proper balances, I wouldn't feel comfortable anymore. In essence, what Malcolm said. Look at the process through the eyes of someone intent on harming someone else, through whatever means needed. Is it still good? > - this kind of process is proven to work in many other communities. The "other communities need this" argument has never really rang true for me. We're not "other communities", we're RIPE. > - within RIPE, we had a "lite" version for several years now, called > "Trusted Contacts" (TC) , and I have been one of the people "appointed" > to this role: difficult job, so I got a training; it's not perfect to be > appointed, nor it is perfect that I have kind-of "conflict of interest" > since I work for RIPE NCC. As TC, we were not "empowered" to take any > action, partially because we were not selected by the community, > partially because there was no CoC framework... as we have now. This is something I've liked and wholeheartly supported (and while not *formally* empowered, you were trusted to do the right thing, and the NCC had all the empowerment it needed to kick out someone from a RIPE meeting if needed). Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: </ripe/mail/archives/ripe-list/attachments/20220915/0074ffba/attachment.sig>
- Previous message (by thread): [ripe-list] [diversity] Two Documents from the Code of Conduct Task Force
- Next message (by thread): [ripe-list] [diversity] Two Documents from the Code of Conduct Task Force
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]