Improving Diversity and Inclusion at the OpenJSF

[tobie]

There've been a few private conversations about diversity and inclusion at the OpenJSF and in OpenJS projects. Now that a lot of the CPC’s work has stabilized, I think it would be great to make diversity and inclusion an important topic of 2021, one where the foundation shows leadership. We have the opportunity to positively influence the whole industry. Let’s leverage it!

@SaraJo and I recently chatted about this. Here some of the topics and activities that came out of that conversation:

• Adding diversity requirements to the CPC and to the leadership groups of Impact level projects. Leadership teams are already expected to come from multiple vendors at this stage, why not also make them diverse?
• Organizing a survey of existing leadership teams to assess the situation and have a baseline to make progress from over the years. (Stackoverflow has experience organizing such surveys and @SaraJo could see if she can find someone to help steer us in the right direction, here.)
• Leveraging Linux Foundation tutorials such as the Inclusive Speaker Orientation to help educate ourselves on these topics.
• Forming a dedicated working group.
• Liaising with other organizations/foundations with D&I efforts (such as W3C’s Inclusion and Diversity Community Group)

Would love to hear your thoughts, suggestions, interest, etc.

Ongoing meeting notes here: https://docs.google.com/document/d/1HD_vnNkvdU9nOTrcZqaRU-_JHR_q6AZQlqjh6TXwis4/edit

[jorydotcom]

We talked about adding some sample "playbooks" for projects developing a growth plan; this could be one of the playbooks (in addition to "reaching impact stage" for example).

[tobie]

Meeting Notes 2021-01-26

Present

• Joe Sepi (@joesepi)
• Sara Chipps (@sarajo)
• Tobie Langel (@tobie)
• Robin Ginn (@rginn)
• Jory Burson (@jorydotcom)
• Rachel Romoff (@RRomoff)
• Mike Samuel (@mikesamuel)
• Darcy Clarke (@darcyclarke)
• Michael Dawson (@mhdawson)
• Tierney Cyren (@bnb)

Notes

• Robin shared D&I slides from OpenJS and LF
• Sara shared https://chaoss.community/metrics/ as a resource for determining how projects approach diversity
• Robin shared inclusive naming https://inclusivenaming.org/
• Discussion around mentorship
• Tierney says if we are talking about mentorship, we should also talk about sponsorship and leveling people up
• Michael suggests playbook around asks for projects
• Robin mentions metrics being helpful as well
• Sara asks about how we define diversity
• Robin mentions the LF’s events strategy
• Darcy shared CHAOSS “Dimensions of Demographics”: https://github.com/chaoss/wg-diversity-inclusion/tree/master/demographic-data#dimensions-of-demographics
• Tierney: enabling us to drive engagement with corporations
• Sara: Three things we are talking about:
  1. Helping projects identify how they are doing, diversity wise
  2. Providing resources depending on where they need work
  3. An initiative around helping companies realize benefits around paying underrepresented minorities to contribute to open source
• Can we take a stand around who we accept to the foundation based on diversity? (First step : how are we doing?)
• Sara and Tobie are going to take a first pass at establishing a standard around diversity for projects to help them identify how they are doing
• Diversity along multiple axes (not just gender) Add racial stats along with LGBTQIA+ representation, geography, language, etc.

[tobie]

Meeting Notes 2021-02-09

Present

• Joe Sepi (@joesepi)
• Sara Chipps (@sarajo)
• Tobie Langel (@tobie)
• Robin Ginn (@rginn)
• Jory Burson (@jorydotcom)
• Rachel Romoff (@RRomoff)
• Mike Samuel (@mikesamuel)

Notes

Survey

• Input from Sara: CHAOSS work on this is actually really good: https://chaoss.community/metrics/#user-content-focus-area---governance
• Self-reporting seems to be the answer
• Scope: projects (but it is hard to dictate these things for projects if we’re not reflecting it internally)
• Goal: start with an assessment
• Dea-nonymization helped by combining the data for the different projects
• Q: Does it matter what projects members are on?
• Q: Do we want to reach out to gather more info? Or help them solve the problem of diversity? A: Projects might feel they are diverse, possible around different planes. Reporting this information might be scary to projects. Projects might get defensive.
• Q: How can the foundation help with this?
• What if we start with the CPC, first? +1 for dogfooding
• Important to account for size of project (different projects will have different needs)
• Linux Foundation focuses mainly on gender. Unclear why?
• LF questionnaire just asks the question about whether you identify with an underrepresented group without specifying which.
• Requirements from other CPC members to have more axes (race, notably).
• DECISION: create a set of questions using Stackoverflow survey as a basis. Present questionnaire to CPC. See if CPC is OK to take the questionnaire themselves. Gather input (especially if there’s pushback). Take the questionnaire. Then bring it to the broader community.

Tools to help projects improve diversity and inclusion; show that they are a welcoming space

• Checklist of “easy wins” to give to projects esp. smaller maintainer teams, e.g.: renaming branch names; adopting a diversity/inclusion statement; adopting policies RE project representation
• One issue here is making decisions without having members of some underrepresented minorities that we want to help present.
• Important to work with organizations to make this happen.
• Can we lend our platform to promote minoritized communities?
• Important to lift the voices of those who are doing really good work already.
• No formal program/process but marketing is really happy to retweet, etc.
• Partnership with orgs work better.
• Goal this year to better leverage communication channels of the projects

Next steps

• [x] Sara to share survey questions from Stackoverflow
• [X] Decide whether we want new call on this topic during next CPC session

[tobie]

@SaraJo shared the survey questions from Stackoverflow:

Screenshots of the survey questions

     

Questions typed out: https://docs.google.com/document/d/12ZN8JvCxJhFnrDr0xNNrUknJor7MoVGxVeztXxEfD0k/edit

[tobie]

I’m so impressed by these questions and how thoughtfully they've been laid out.

Are there similar sets around income, location, and native language?

Looking at those, however, I’m concerned about the privacy implications of collecting this data for such a small sample set as the CPC. Do we have someone that could explain the sample size needed to be able to truly protect the privacy of the respondents, here?

WRT to tooling, I’m wondering if the foundation has a preferred toolset or an account it could share. Typeform has significant accessibility problems and a track record of not caring to fix it (see https://a11y.reviews/#typeform), so I’d rather we used something else.

[SaraJo]

There are similar sets around those questions, I can grab them. You make a good point about the sample size, maybe this is us learning about our approach. Do you have any thoughts on how we can make that less of an issue?

Happy to use something besides Typeform, not tied to it at all. Google forms is also good.

[designMoreWeb]

The templates for DUA (Data Usage Agreement) :

1. DUAToolkit This is a guide on how to create and use a DUA, also when and whom the DUA is for, depending on the data collected.

2. The DUA template This is a DUA word template which is between Center for Disease Control and Prevention (“CDC”), National Healthcare Safety Network (“NHSN”)

Hopefully these can help and provide assistance

[sendilkumarn]

Before we deep dive into collecting data, can we take a step back and list down what we would like to achieve in OpenJSF?

1. There are some easy wins, like ensuring our documentation/ communication and project's documentation / communication are always inclusive (we can even have a system that proactively monitors this and ensures that we are always inclusive and alerts).

2. How to enable more and more less represented communities in the project and enable them to contribute? This is one of the hardest problem out there to aolve.

3. How to educate or the steps to do when there is a mistake?

4. Add D&I process to our project on boarding checklist. Every project will be at different stage here, how we can guide them in this process.

IMO, if we have specific targets, then it will be easier for us to decide on what data do we need and how we can collect them.

[SaraJo]

@sendilkumarn I like this approach.

1. This sounds like a great task to take on. This seems like value we can contribute immediately.

2. It is. Additionally, all of this is volunteer work which is something that is easier for some than from others. I would love to solve this problem, but given we are not experts, I think that partnering with organizations that do. I like the idea of partnering with the folks at CHAOSS as they can share their learnings with us, and may have actionable feedback.

3. This is something there is research around. Any thoughts on the best way to distribute this kind of info?

4. Yes! I think this is the goal of this project.

I also want to cc @designMoreWeb as I know he wanted to join the conversation/work here.

[bnb]

Closing, as we've moved this work to other more specific initiatives. Please feel free to reopen if necessary.