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 ]
Randy Bush
randy at psg.com
Thu Mar 4 19:25:48 CET 2021
> An updated draft RIPE Code of Conduct (CoC) is now published for your > review. As this is intended to cover all participation within RIPE, it > applies to interactions over the Internet, mailing lists, as well as > in-person at RIPE Meetings. i can live with it. but it does seem a bit over-prescriptive and legal. the community does seem to have grown more over-prescriptive and legal in general. i suspect rob would have said it in a dozen words. when asked to make rules for fidonet, tj said don't be excessively annoying. don't be easily annoyed. but those were different times. and we have had some ugly problems that should not be shoved under the rug. i just wonder if the document's detail and rigidity will pay off or be bait for nit-picking arguments and excuses. but, again, to be clear, i can live with it. randy --- randy at psg.com `gpg --locate-external-keys --auto-key-locate wkd randy at psg.com` signatures are back, thanks to dmarc header mangling
- 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 ]