The RIPE Code of Conduct
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
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@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://lists.ripe.net/mailman/listinfo/ripe-list
Hi Joao,
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.
I fully agree with you. I would like to see Hans Petter's clarification on how he intended his message. To me it read like the "last resort in case people misbehave badly" way that Mirjam described, and after some sleep I really hope HPH meant it as a gentle reminder and some of us interpreted it differently.
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.
Indeed. Thanks to you both! Sander
Hi Mirjam, all, You can't declare consensus in something that was developed by a TF that discriminated even a single participant from being part of the TF. That creates a problem since minute cero, and basically invalidates the process. Regards, Jordi @jordipalet El 3/2/22 10:57, "ripe-list en nombre de Mirjam Kuehne" <ripe-list-bounces@ripe.net en nombre de mir@zu-hause.nl> escribió: 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://lists.ripe.net/mailman/listinfo/ripe-list ********************************************** 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.
On Sun, Feb 20, 2022 at 12:01:49PM +0100, JORDI PALET MARTINEZ via ripe-list wrote:
You can't declare consensus in something that was developed by a TF that discriminated even a single participant from being part of the TF.
Consensus is not unanimity. And task forces or workgroups have no inherent need to include everyone. In fact, consensus decision-making tries to cope with social situations where a few participants are unable or unwilling to learn, understand and adhere to established (by consensus) social interaction parameters. Since I have no relevant standing and no reputational damage to fear, I will just go and opine that you, JORDI, fall into that category. It is my impression that you might be unable to participate in a constructive manner. I am regretfully not skilled in how to express this in a way that may help you more to address this. If I were, I certainly would. I would also like to point out that the tolerance you've enjoyed hitherto can have negative impact and costs in alienating others from participating in this forum. I do not have the necessary insight to make that determination but am painfully aware and afraid of the possibility. -David (I have said my piece and will not be reading or responding in any manner on this matter, neither on-list nor on any other channel. I'm pretty close to being alienated-out myself here.)
Hi David, I know very well what is consensus: Been contributing in IETF and all the RIRs since 20+ years ago. Of course, you're free to think this way if I'm able to be constructive or not. However, facts from 20 years and around 100 or policy proposals among all the RIRs, which reached consensus, show otherwise. I've proven many times that I'm able to support and even defend objectively ideas/proposals that are against my personal subjective view point. Regards, Jordi @jordipalet El 20/2/22 14:29, "ripe-list en nombre de David Lamparter" <ripe-list-bounces@ripe.net en nombre de equinox@diac24.net> escribió: On Sun, Feb 20, 2022 at 12:01:49PM +0100, JORDI PALET MARTINEZ via ripe-list wrote: > You can't declare consensus in something that was developed by a TF > that discriminated even a single participant from being part of the > TF. Consensus is not unanimity. And task forces or workgroups have no inherent need to include everyone. In fact, consensus decision-making tries to cope with social situations where a few participants are unable or unwilling to learn, understand and adhere to established (by consensus) social interaction parameters. Since I have no relevant standing and no reputational damage to fear, I will just go and opine that you, JORDI, fall into that category. It is my impression that you might be unable to participate in a constructive manner. I am regretfully not skilled in how to express this in a way that may help you more to address this. If I were, I certainly would. I would also like to point out that the tolerance you've enjoyed hitherto can have negative impact and costs in alienating others from participating in this forum. I do not have the necessary insight to make that determination but am painfully aware and afraid of the possibility. -David (I have said my piece and will not be reading or responding in any manner on this matter, neither on-list nor on any other channel. I'm pretty close to being alienated-out myself here.) -- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/ripe-list ********************************************** 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.
participants (5)
-
David Lamparter
-
Joao Luis Silva Damas
-
JORDI PALET MARTINEZ
-
Mirjam Kuehne
-
Sander Steffann