1 of 24

1

2 of 24

3. Insights

2. Who Participated

  1. Background & Goals

6. Questions?

5. Standards & Best Practices

So far...

4. What We Learned

About data & metrics for diversity & inclusion

2

Agenda

3 of 24

Background & Goals

Why a cross-project survey?

3

Distribution

Privacy & Legal C

Standards for Data

Metrics that Matter

2017 Research

Goal-Setting & Planning

Outreach

4 of 24

Who Participated?

4

                  • 202

Open Projects

                  • 489

Open Source Contributors

Stat option 1

Mozilla Confidential

5 of 24

5

Gender Identity

Transgender?

6 of 24

Regions

6

11.9 %

Asia

44.2%

North America

33.6%

Europe

2.9%

Africa

4.1%

South America

3.7 %

Austria

.9 %

Oceana

Mozilla Confidential

7 of 24

7

Age

8 of 24

8

Disability

9 of 24

9

Technical Confidence,

Access to Technology,

City/Suburb/Rural/Town

10 of 24

10

Community Role

11 of 24

Insights

12 of 24

Insights - Leadership

Mentorship Matters - Those who had been helped by others in the past, nearly 20% more likely to believe leadership roles were achievable; 11% more for non-male identities.

12

All gender-identities

Non-Male identities

13 of 24

Insights - Leadership

“Any status I've had in a FOSS project has always come from the aggregate strength of those who have had chance encounters with my contributions.

“I've been sort of 'blessed' by leaders before me, that also paved the way for me to step into leadership roles. We need to nurture inclusive leadership, and should do more succession planning”

13

I love that drupal.org profiles lets you list people as mentors."

Mentorship Matters

14 of 24

Insights - Leadership

Strategies for Inclusive Leadership are Critical

A number of people not themselves targets listed these types of behaviors as a reason they leave.

  • Formalize informal roles, especially less technical roles.

  • Ensure cycles of renewability, including succession planning.

  • Address toxic behavior - including (especially?) star contributors

  • Shut down behaviors that isolate and exclude like sexism, racism and ageism. *

  • Specifically invite people to opportunities

14

“ Leadership roles are obtainable, but it's much more difficult as a woman. Not only are leadership positions harder to obtain, the levels of scrutiny, backlash, and criticism are much higher.

Female leaders have to be above reproach in every area, whereas male leaders are defended even when they're acknowledged throughout the community as harassers, criminals, or destructive to community morale. “

15 of 24

Insights - Leadership

Not everyone wants to lead!

“ Open-source leadership is a big commitment. I prefer to contribute to many projects rather than lead one.”

“I'm not sure I want to be in a leadership position in the open source community..”

I’m done leading, time for younger folks to do the leading, I will follow and offer (probably unwanted)advice”

15

16 of 24

Insights - Inclusive Design

Our differences make us stronger

16

I was not encouraged to pursue computer science as a girl

I have trouble following conversation when there's noise, overlapping speech, or slurred speech

We (neurodiverse people) are an over-represented group in tech, yet technical events are skewed towards neurotypical attendees

  • Watch Technical Jargon (it’s not about ability!)!

  • Make space (and give air) to less dominant personalities.

  • Add captioning, transcription and other text-based ways for people to interact.

  • Accommodate low or limited bandwidth in comms and opportunities.

  • Make ‘how to start’ documentation a priority and policy.

  • Invite and accommodate neurodiverse perspectives.

17 of 24

Insights - Inclusive

Motivations, Recognition & Value

  • Do not give people mentorship, or leadership roles merely because they are good coders, or accomplished at one thing. Select appropriate roles for persona goals.

17

Appreciation or thanks sent in private usually have a deeper impact on me

Further inclusion is the most flattering, though I'll always prefer to have something on paper to back up my experience.

As a non-binary trans person from an emerging country, I was delighted at finding some amazing and inspiring queer people working in open source. It motivated me more to contribute.

  • Say Thank you! In issues, in blog posts, in email, in chat, in.. Happiness Packets.

  • First bugs for learning is nice, but seeing contribution as part of a project or initiative matters most.

  • Provide assigned roles with appropriate influence *

  • Help connect people to the community and your project mission.

  • Contributing is sometimes a significant part of professional workflows and learning pathways.

  • Help people create or join identity groups.

18 of 24

Insights - Obstacles & Blockers

  • Do not give people mentorship, or leadership roles merely because they are good coders, or accomplished at one thing. Select appropriate roles for persona goals.

18

“ We did not have much money growing up and i did not have regular access to a computer or internet until college.

  • I get too busy
  • Confusing documentation
  • Technical confidence (not about ability)
  • Toxic People
  • Not sure where to start
  • I don’t agree with how things are run
  • Childcare eldercare

.

19 of 24

What people know….

D&I in Open Communities Survey

Does your community have a code of conduct?

If so, is it effectively enforced?

19

Trans people

Mozilla Confidential

20 of 24

Do people feel safer & more empowered when there is a CoC?

20

They didn't have a CoC when I was involved. They later created one, but it was heavily lobbied against, watered down, and rarely enforced because of the power of the men who harass and hate the most. So they think they have a CoC, but they don't. They only have a mess. -survey response

Mozilla Confidential

21 of 24

Insights - Inclusive Design

Our differences make us stronger

It would be nice to have a rating for communities, but that might be simplistic

21

“ They created a COC, but it was heavily lobbied against, watered down, and rarely enforced”. So they think they have a CoC, but they don't. “

There should be no such Code. Because it always ends up with far-Leftists and other undesirables writing it. The tech is fine. It's the Communists that are the problem.

“ Having a code of conduct makes me feel safer, but I'm uncertain whether it would ever be enforced; our community is so white and so cis that I feel completely invisible as a minority. ”

  • As a contributor, it’s really hard to tell if CoC/CPG are enforced. *

  • Even if a CoC/CPG is enforced, it’s hard to tell to what extent to trust

  • Enforcement is sometimes perceived to be in the hands of the wrong people.

  • A vocal minority are sometimes against CoC

  • Few if any projects have visibility for their processes.

  • Many projects have yet to tackle NDA in their approaches to resolving community health issues.

  • We need better strategies for anonymous reporting.

22 of 24

What we learned building this survey

a lot...

23 of 24

What we Learned

23

  • We failed at Ethnicity.

  • We need Regional Strategies for Diversity & Inclusion including Data & metrics

  • Qualitative vrs. Quantitative

  • Project list was inadequate

  • Oceania

  • Multiple checkboxes for gender

  • Questions were sometimes leading (blockers, motivations etc)

  • Force top choices in some cases (vrs all that apply).

  • Consider hostile responses in filtering

  • Set of rules for when to ask questions - i.e. why are you asking about x identifier?

  • Cross-project queries are important in helping us understand where to work together most effectively.

24 of 24

Standards & Best Practices

github.com/mozilla/diversity