Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit our Code of Conduct: Hyperledger Code of Conduct
Attendees
Agenda + Notes
I. Inclusive Naming List
From last week's next steps
- Blog Post https://www.hyperledger.org/blog/2021/01/26/removing-barriers-to-contribution-with-inclusive-language
Inclusive Naming Initiative discussion on our list: https://lists.hyperledger.org/g/dci-wg/message/252?p=,,,20,0,0,0::Created,,inclusive,20,2,0,78367835
- >>Besu has implemented some changes already - Grace will share on mailing list their documentation of changes
- >>After blog post bring back to the TSC for review
- >>Peter to share link to mailing list when code is deployed.
- >>Review as a group the inclusive naming list in next meeting https://github.com/petermetz/dci-lint
II. Review Recommendations to TSC and lay out next steps
For reference, here is the culmination of the WG's discussion from last year, we put together a number of TSC and Governing Board Motions, some of which have been and are being implemented, others which are included in the table below as part of our goals for 2021. Please review them here: Turning Recommendations into Proposed Motions for the GB and TSC
Proposed Motions for the TSC
- Recommendation 1: 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 2: 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 3: 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.
- Proposed Ask #4 Collaborate with DCI on the development and implementation of a new Badging criteria
- Overview: Currently Projects experience challenges meeting the DCI criteria. This motion is meant to formalize our intent to work w/ the TSC to develop a solution.
- References: Project Badging Proposal, Project maturity metrics / Badging
>>ADD YOUR AGENDA ITEMS HERE
Backlog
- Finalize TSC Recommendations
- 2021 Planning