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] The RIPE Code of Conduct
- Previous message (by thread): [ripe-list] The RIPE Code of Conduct
- Next message (by thread): [ripe-list] The RIPE Code of Conduct
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Joao Luis Silva Damas
joao at bondis.org
Thu Feb 3 11:40:58 CET 2022
Hi Mirjam, all, A code of conduct is a welcome addition to RIPE’s toolset. It is a pity we need one but such is humanity. The problem with any code/rulebook is, as has been shown, how it gets applied. Hans Peter’s was a most unfortunate action: not only was it completely out of line, showing poor judgement, it was not his to apply. This should have been a RIPE chair(team) call (or even the wg chair and the wg itself). I was happy to see the community’s reaction in this regard. Having the RIPE NCC come out the way it did is very harmful to people’s perception of what the real intent is, as has already been expressed. I was very happy to see Athina’s posting on how the RIPE NCC plans to incorporate comments. I very eagerly await Hans Peter’s. The sooner we can get most people to again believe that the CoC is a tool for good, the better. In this sense your email is most welcome. Joao > On 3 Feb 2022, at 10:56, Mirjam Kuehne <mir at zu-hause.nl> wrote: > > > Dear colleagues, > > I have been thinking about what was said on this list about people being > afraid of the Code of Conduct. > > I did not hear people were afraid of adopting a RIPE Code of Conduct. > Instead I heard broad consensus and I believe we managed to build a Code > of Conduct that encourages "good behaviour" and positive and > constructive engagement. I think as a community we can be proud of that > achievement. > > I have the impression however, that the pure existence of a Code of > Conduct can be interpreted in different ways. Some people might see a > Code of Conduct as guidance that is there in the background to remind us > all how we want to treat each other. In that scenario it might make > sense to refer to it from time to time and to nudge each other in a > friendly way. > > Other people might see a Code of Conduct as a threat and as a last > resort in case people misbehave badly. In that scenario the Code of > Conduct would be used in very exceptional cases only and would > potentially have severe consequences for a community member. > > I believe that the tone in which the RIPE Code of Conduct is written and > the way it was accepted and agreed by the community, should make people > feel safe and that it would be interpreted more in the former way. I > understand from reactions to the list that this is not necessarily the > case. How can we change that? > > I would like to remind you that the work of the RIPE Code of Conduct > Task Force is not finished yet and that they are working on the > implementation process. I would very much appreciate any feedback from > you to make sure we all feel comfortable and safe and protected by a > Code of Conduct. It should not be seen as a threat. > > Kind Regards, > Mirjam > RIPE Chair > > > -- > > To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/ >
- Previous message (by thread): [ripe-list] The RIPE Code of Conduct
- Next message (by thread): [ripe-list] The RIPE Code of Conduct
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]