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]/
[diversity] *draft* CoC Team doc
- Previous message (by thread): [diversity] *draft* CoC Team doc
- Next message (by thread): [diversity] *draft* CoC Team doc
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Daniel Karrenberg
dfk at ripe.net
Mon Sep 2 17:06:07 CEST 2019
Sascha, Well spotted. I was not going to mention mailing lists for fear of being perceived as a grumpy old white man who is simply obstructionist. But since you raised it … I agree that it is extremely likely that any procedure that we design for meetings is likely to cause calls for a procedure for mailing lists whether we like it or not. And yes there will be suggestions to ‘Just have the CoC team police the mailing lists too.’ It would be good governance to be mindful of this when designing procedures. Again: the IETF has evolved procedures for mailing lists ... They are neither simple nor easy to apply. Daniel
- Previous message (by thread): [diversity] *draft* CoC Team doc
- Next message (by thread): [diversity] *draft* CoC Team doc
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]