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] 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] 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 Apr 20 12:06:26 CEST 2021
Hi Hank, I agree with those points, we had similar discussions in other RIRs. Not being a lawyer, I believe that instead of “copyright”, we should use “intellectual property”, as copyright is one form of presenting that. Regarding the law violation. It is not clear how that should be formulated, because, it is impossible that everyone knows the law of Netherlands and it may be even in simple things very different from your own country. In fact, if that happens, it will be a legal issue, which is always on top of any code of conduct that we want to set. I understand that most of the CoC aspects, could be considered against law in many countries, and we want to make them “explicit”. However, for that specific point I’ve “confronted sentiments”. In my opinion, if something violating law is posted which is not clearly described in all the other points of the CoC, it is up to the Dutch LEA/courts to decide and it is up to RIPE NCC to inform them about “their feeling that it may be the case”. Let me go a bit further: This is also relevant to the email archives. They should reflect all what happens in the list, like a meeting recording, minutes, etc., uncensored. Deleting from email archives something that could be a law violation should be only done if the law ask for it. Regards, Jordi @jordipalet El 20/4/21 7:30, "ripe-list en nombre de Hank Nussbacher" <ripe-list-bounces at ripe.net en nombre de hank at efes.iucc.ac.il> escribió: On 19/04/2021 20:12, Randy Bush wrote: The RIPE NCC regularly organizes events for communities which are distinct from RIPE. When preparing for such an event, the RIPE NCC will ascertain whether the respective community has adopted the RIPE Code of Conduct and, if not, also ascertain which Code must be applied. my naïve view is that, if the ncc is an organiser, then the coc MUST apply. if i am asked to be on (or chair) a panel which has no under-represented folk, i decline, making the reason very clear. randy Reviewing the CoC I have noticed a few items that maybe need to be included (not sure): - violating someones copyright or trademark - distributing malware with the intention of infecting participants - reposting private emails without the express permission of the sender - posting something that would violate the law in the Netherlands - posting commercial/advertisement content Probably each is open to debate. Regards, Hank Caveat: The views expressed above are solely my own and do not express the views or opinions of my employer ********************************************** 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/20210420/62d5e10c/attachment.html>
- Previous message (by thread): [ripe-list] 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 ]