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] 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] 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
Tue Mar 30 11:35:30 CEST 2021
Very good point. I don’t agree with the “split”, I think it increases complexity instead of simplifying it, as I already mention, however if this is made in order to facilitate the work, etc., I will consent on that. That said, to be acceptable, I think we need to a couple of things: Number sections/sub-sections (to facilitate reading/inputs and so we can make cross-references, if needed across documents). Reach consensus in the documents as a “set”, not one by one, because I feel that some of the discussions, wording, etc., in one document can have important impact in the others. Regards, Jordi @jordipalet El 30/3/21 11:29, "diversity en nombre de Sasha Romijn" <diversity-bounces at ripe.net en nombre de sasha at mxsasha.eu> escribió: 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 SupportComment 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 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 _______________________________________________ diversity mailing list diversity at ripe.net https://lists.ripe.net/mailman/listinfo/diversity ********************************************** 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/ripe-list/attachments/20210330/d867ed92/attachment.html>
- Previous message (by thread): [ripe-list] [diversity] Updated Draft RIPE Code of Conduct Published for Community Review
- Next message (by thread): [ripe-list] Updated Draft RIPE Code of Conduct Published for Community Review
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]