Joan Touzet wrote on 3/30/19 12:52 AM: ...snip... > Precisely the point. I'm in favour of this, though I know others are > actively against it. I talked about this at length during my > ApacheCon 2018 talk, proposing options that are well thought-out and > fair, drawing from a wide variety of sources; I encourage you to > listen to the full recording and read my slides before passing > judgement.
For the benefit of list readers: https://speakerdeck.com/wohali/building-and-sustaining-inclusive-communities?slide=10 https://feathercast.apache.org/2018/09/29/building-and-sustaining-inclusive-communities-joan-touzet/ ...snip... > Again as Rich says, there's explicit approval to proceed with a D&I > initiative already, from both the Board and the President. People like > Naomi and I have been through the "prove it to me" request many times > over, and I'm tired of responding to this particular email. There's not even a need for explicit approval for volunteers here to spend their own time finding a space to work, and building Apache 2.0 licensed content anywhere on the ComDev website, at upcoming ApacheCons, or within their own Apache projects. I'm excited to see several dedicated people showing up in this thread, and once we have a new space for the ideas Naomi and Gris and others want to work on, I'll join. ---- But this thread does show an unfortunate classic meta-issue in many broad volunteer-run communities: people not actively working on a specific issue bringing sufficient tangential discussion, questions, and vague opposition to effectively kill new work on that issue. A situation that's happened to me personally with saddening regularity: I come up with a new idea to improve a process or document, and ask for feedback. Some of the feedback asks "why are we bothering with this" or "I think that's wrong because X", or merely asks clarifying questions / requests for more additional data, or or or... and often ends up being an endless game of "fetch me a rock". After attempting to answer a half-dozen of these questions - many tangential or merely expressing opposition *without providing useful alternatives*, I simply run out of volunteer energy and give up on the idea completely, and I find some other place to spend my time. The opposition of just a couple of people spending the time to keep asking for clarifications can often turn into a de facto veto for all sorts of new ideas. Apache communities work better when people who think a new idea is [dumb | annoying | not useful | whatever ] simply raise the general concern once, but otherwise get out of the way. We're all volunteers; we all have opinions; we all have things we want to work on in our different communities. We can respectfully say we don't like some new idea, but it's not up to any of us to stop other volunteers from doing that new idea that they're passionate about. Even better: when you don't like a new idea, come up with a better idea, and volunteer your own time in a new thread to productively work on it. ---- Bonus link, that I hadn't seen before but I really like the *explanations* behind this organization's social rules: https://www.recurse.com/social-rules -- - Shane ComDev PMC & Member The Apache Software Foundation --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
