hey folks, now the D&I committee is official, I think it's time we think about the resources we want to commission
so far we have one mailing list: - diversity@apache.org we also have: - https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=112820458 - https://issues.apache.org/jira/projects/DI/issues/DI-2?filter=allopenissues at a minimum, I would like to suggest we create: - diversity-priv...@apache.org (for use akin to how priv...@tlp.apache.org lists are used) I am also wondering if we want to create: https://diversity.apache.org/ <https://community.apache.org/> this could be a more formal, polished presence for us on the Apache site. the first port of all for Apache committers/members, as well as outsiders. (whereas the wiki would be more for our own use as a committee) I'd also like to bring back the suggestion that we have a third list exclusively for off-topic threads (my rubric for "off-topic" would be "is this helping us get work done>"). people can do what they like on the other list (within reason). bring up beginner questions, request education, rehash old debates, whatever diversity-disc...@apache.org might work for this. it fits in with our other top-level foo-discuss@ mailing lists. and it's a value-neutral name I want to stress my belief that if we don't have a dedicated mailing list for "debates" and requests for education, and so on, there will be no way of dealing with that stuff on diversity@ in a way that doesn't run the risk of derailing productive threads and sapping contributor energy. I really want to be able to say "this is off-topic for this list, please move it to diversity-discuss@" (and that is something we can enforce if someone decides to cause problems) yes, trolls are likely to come straight to diversity@, but we can direct them elsewhere (see above) an alternative way of doing this would be to use diversity@ for general discussion and create diversity-dev@ for the committee to actually get work done. I don't think this solves the troll problem. they'll just join diversity-dev@ instead. but we can do the same thing, and direct them to diversity@ really, I think this comes down to the semantics of -discuss and -dev and what we think is more suitable in summary, I have three proposed actions: - create diversity-private@ - create diversity-discuss@ or diversity-dev@ - create https://diversity.apache.org/ <https://community.apache.org/> I am sending this email to see if we have consensus around one or more of these proposals after waiting a bit, I will assume lazy consensus for anything with no raised objections and request the resource thanks!
