I think the point was not that the FAQ needed those things, but the ASF
at large :D and that the different way of phrasing it was intended to
draw attention to all of those things.
-Joan
On 2019-05-13 6:45 p.m., Patricia Shanahan wrote:
I would love truly elegant documentation. However, I am neither a
Confluence expert nor a graphic designer. As you say, it needs a community.
Perhaps people who are good at graphic design could create frameworks
for the FAQ and Resources? Should each of them, long term, be Wiki pages
or pages in a D&I web site? However it is done, it cannot depend on
graphics. There are some readers who will only have access to whatever
text their browser can extract.
Curating the initial content is something that seems to me to need doing
and that I think I know how to do, so I started doing it.
On 5/13/2019 3:03 PM, Matt Sicker wrote:
This might be slightly inflammatory, but how about this: do you want
non-shitty documentation? How about graphics and logos? Maybe a nice
website? Or some helpful users for support? Hard to do without community!
On Mon, May 13, 2019 at 15:14, Patricia Shanahan <p...@acm.org> wrote:
The first and most important question is something along the lines of:
--------------------------------------------------------------
Q: Apache does everything by e-mail. I do not know or care about the
race, ethnicity, gender, age, weight, or any other personal
characteristics of other contributors. Why are diversity and inclusion
relevant issues for Apache?
--------------------------------------------------------------
Here are some elements that I think should be covered in the answer. At
this point, I am going for the big picture. Please suggest improvements
and fix errors.
--------------------------------------------------------------
1. Subconscious bias: You know the name the contributor uses. In
addition, you may know their time zone and, from how quotes are
introduced, the language in which they do most of their e-mail
interaction.
Research indicates that merely changing the name on a resume can affect
the probability of a call back. Although the results could in theory be
explained by deliberate racism and sexism, they seem more likely to be
due to subconscious bias.
2. It is not all e-mail: Apache contributors meet at open source
conferences, specialty technical conferences, and local gatherings. Not
being able to participate without fearing discrimination would itself be
discouraging.
3. Unintentional insult through stereotypes: This is a bigger risk in
e-mail than in face-to-face interactions.
I had someone on a mailing list use "try to explain X to someone's
aunt", where X was a difficult technical point, as an example of
futility. It invoked a stereotype of older women as lacking computer
science comprehension. As it happens, I already had two adult nephews
when I got my PhD in computer science. The writer would probably not
have said what they did in a live conversation including a grey-haired
woman.
4. Misuse of pronouns: If you know someone's preferred pronouns you know
something about their gender, and subconscious gender discrimination
becomes possible. If you don't, you may be making them cringe every time
you refer to them in an e-mail.
--------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: diversity-unsubscr...@apache.org
For additional commands, e-mail: diversity-h...@apache.org
--
Matt Sicker <boa...@gmail.com>
---------------------------------------------------------------------
To unsubscribe, e-mail: diversity-unsubscr...@apache.org
For additional commands, e-mail: diversity-h...@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: diversity-unsubscr...@apache.org
For additional commands, e-mail: diversity-h...@apache.org
