This is a working document where we can draft potential motions to propose to the Hyperledger Governing Board and TSC based on the DCI-WG Recommendations To The TSC 2020 document that was presented to the TSC on July 30, 2020. Feedback on the recommendations has been that it would be useful to take another pass to make them more specific and actionable. For example:
- In the recommendations, we see: "Adopt inclusive terminology in coding standards; Avoid whitelist/blacklist and master/slave." That could be rephrased as a motion to the Governing Board like this: "WHEREAS, the Technical Steering Committee shall confirm by the end of December 2020 that the terms "blacklist", "whitelist", "master" and "slave" be eliminated from current and stable development branches of Hyperledger repositories."
When proposing a motion below, please also include a reference to one of the recommendations that was presented to the TSC so that we can track items back to recommendations that the DCI-WG has identified as important to address.
Proposed Motions for the GB
- Recommendation: Raise the profile of the diversity and inclusion focused efforts in the community
- Proposed motion #1: WHEREAS, the Governing Board shall task the Marketing Committee and Hyperledger staff to organize at least one diversity focused campaign each quarter in 2021 to raise the profile of the diversity and inclusion focused efforts in the community.
- Example: The Fabric Documentation Working Group earlier this year started working with community members to translate Fabric documentation into different languages. A campaign highlighting the work of these contributors would show our language diversity and show that Hyperledger is a global community. A campaign would also help us reach new people interested in translating more content into more languages. Other campaigns could be focused around Pride month, Hyperledger-based projects that are being developed by students and professors at HBCUs, or events such as the Grace Hopper conference.
- Recommendation: The board should engage contributing companies to fulfill diversity goals
- Proposed motion #2: WHEREAS, we on the Governing Board agree to commit an individual from our respective organizations currently involved in Hyperledger or blockchain activities to participation in the DCI Working Group, to attend monthly meetings and contribute in material ways.
- Recommendation: Consider partnerships with Historically Black College and Universities (HBCUs) and organizations (e.g. Girls Who Code) aimed at increasing diversity pipeline. Partnerships could be centered around recruitment, engagement in hackathons, and training.
- Proposed motion #3: WHEREAS, we on the Governing Board agree to facilitate introductions to organizations focused on bringing underrepresented groups into software development that we are working with in order to create new collaboration opportunities for the Hyperledger community.
- Recommendation: Staff responsibilities (We recommend a process where projects that want to be more inclusive can opt in to receive support from staff in auditing and updating their contribution infrastructure.)
- Proposed motion #4: WHEREAS, we on the Governing Board direct Hyperledger staff to clearly define roles and responsibilities to regularly audit the ability for new contributors to participate in the Hyperledger community and to support projects with implementing changes to make the community a more welcoming and inclusive space.
- Example: This year we have run pilot efforts to support a small number of projects with auditing their current contribution pathways and working with them to improve those pathways. We could scale this effort up and create a process for supporting all of the projects in the community that would like this assistance.
- Please feel free to add proposed motions here.
Proposed Motions for the TSC
- Recommendation: Incorporate DCI agenda directly into TSC Meetings
- Proposed ask #1: Can the Technical Steering Committee create space in their meeting agendas for at least one diversity and inclusion focused discussion each month?
- Example: Agenda topics could include: Adopting inclusive terminology in coding standards, broadening the community translation effort that is currently focused on Fabric documentation, including diversity metrics in a Community Health dashboard proposal, etc.
- Recommendation: Adopt inclusive terminology in coding standards
- Proposed ask #2: Can the Technical Steering Committee set guidelines for projects to follow around using inclusive language in both code and documentation and set expectations for when those changes should be made? The DCIWG recommends...
- Example: Replace the terms "blacklist", "whitelist", "master" and "slave" in current and stable development branches of Hyperledger repositories.
- Recommendation: Maintainer responsibilities (Maintainers should be familiar with community development best practices & Maintainers should take an active role in developing their community including a pipeline of new maintainers.)
- Proposed ask #3: Can the Technical Steering Committee develop an onboarding guide for project maintainers that documents the expectations in terms of knowledge of community building best practices?
- Example: An onboarding guide could include guidance about completing the Linux Foundation's Inclusive Speaker Orientation, information about how to work in an open source community and how to act as a mentor to new community members who want to contribute to their project.
- Please feel free to add proposed motions here.