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] 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 ]
Sasha Romijn
sasha at mxsasha.eu
Tue Mar 30 11:29:37 CEST 2021
Hello Leo, I’m fine with the current draft if the comment I made is addressed (and depending on how comments from others are integrated). “Support” feels like a big word, because this document is functionally incomplete without the other documents. I know that splitting into parts is the process that has been decided on, so that’s not something we can easily change now. Sasha > On 29 Mar 2021, at 10:30, Leo Vegoda <leo at vegoda.org> wrote: > > Dear RIPE Community, > > I'd like to thank everyone who has already commented on this draft update to the Code of Conduct so far. > > I have been keeping track of the comments so the TF has a good idea of what changes we need to make to the draft. I've tabulated them below and it would be good if people could let me know if I have misunderstood what they meant. Also, some people have commented but not stated if they support the daft as is, or would support the draft with a minor change. I've placed a question mark next to names where I'm not sure what a person's position is. It would be great if you could clarify your position. > > Many thanks, > > Leo Vegoda > On behalf of the RIPE Code of Conduct TF > > Commenter > Support > Comment or Delta > Eileen Gallagher > ✓ > Add: acknowledgments of earlier work done by others when presenting new work > Add: thanking people for their contribution as an example of positive behaviour > Comment: RIPE NCC might want to incorporate the CoC into contracts with venues > Randy Bush > ✓ > Keep the CoC tight > Vesna Manojlovic > ✓ > Add: definition of the CoC Team > Add: call to action > Nit: Add date and authors > Nit: Change “for more than quarter of a century” to “since 1989” > Nit: make the URL ripe.net/coc <http://ripe.net/coc> > Nit: Rename "Behaviour" title to "Inclusive Behaviour" or another alternative > Nit: "people protected" -> remove bullet points, make it a CSV line of text > Gert Doering > ✓ > — > Maximilian Wilhelm > ✓ > — > Daniel Karrenberg > ✓ > Focus more on principles and make it even clearer that the lists are examples and not comprehensive > Do not give the PC a special role > Nit: Change “national laws” to “laws” > Nit: ONly talk about roles and organisations in the community in general terms > Stated that the obligation to report crimes is very limited > JORDI PALET MARTINEZ > ? > Nit: Number all sections > Rationale must balance inclusivity against freedom of speech and cultural differences > Include all ways of communicating over the Internet > Does not understand why the PC needs to be consulted > Does contracted workers include subcontractors? > Wants the RIPE NCC staff to always intermediate if a report is made to the police and understands that there could be liability if people know of an incident and do not report it > Add protection for those who do not speak English as a first language > Does not think "calling people names" is clear for non-native speakers > Rephrase “Deliberately outing private details about someone without their consent” > Rephrase “Pushing someone to drink or take drugs” > Add a prohibition against spam > Forbid using language a non-native speaker might misunderstand > Similarly, the CoC Team should accommodate cultural differences > Wants the process in the same document > Sasha Romijn > ? > Question about how the team would determine if an act should be reported to the police and a preference for that to be controlled by the subject of the act > Jim Reid > ? > Supports Sasha on police report issue > Sander Steffann > ? > Supports Sasha on police report issue > Gergana Petrova > ? > Clarification on making a police report > Echoes the question about the role of the PC (see above) > Rob Evans > ? > Trusted Contacts training gave him the understanding that there is no obligation to make police reports. Trusted Contacts are confidential contacts > Fearghas Mckay > ? > Confidentiality and control are important in helping people have the confidence to make a report > > _______________________________________________ > diversity mailing list > diversity at ripe.net > https://lists.ripe.net/mailman/listinfo/diversity -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/ripe-list/attachments/20210330/29fcea8e/attachment.html>
- Previous message (by thread): [ripe-list] 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 ]