Question: How well are project issues labelled to invite new contributors, skilled contributors, non-code contributors, and other types of contributors?
Issue Label Inclusivity measures the accessibility and inclusiveness of project issues for contributors of various skill levels and backgrounds. Data points include the number and types of labels used, the clarity of issue titles and descriptions, and the presence of labels that indicate the level of skills needed to tackle the issue. The Issue Label Inclusivity metric can help a project ensure: newcomer friendly issues are created, issue list diversity, usable titles and descriptions, and consistent use of labels to identify types of contributor or skill level needed to work on an issue. Inclusive labelling practices help create a more equitable and accessible environment for contributors from all backgrounds. Providing clear and informative labels, helps projects reduce the learning curve for new contributors, encourage participation and promote diversity within the community.
Click to read more about this metric.
-
Identify the published list of issue labels used for each project
- General labels identify general needs of the project (e.g.Feature, Bug, and Documentation)
- Newcomer friendly labels identify issues that are appropriate for first-time contributors (e.g., newcomer, good first issue)
- Skill labels identify skills needed (e.g, Java, Python, HTML, machine learning)
-
Observe the frequency of each label used across issues in a project
None Identified
- Type of repository
- Age of open issue
- Number of open issues
- Date an issue was opened
- Code-related issues vs. documentation-related issues
- Elizabeth Barron
- Georg Link
- Matt Germonprez
- Peculiar C Umeh
To edit this metric please submit a Change Request here
To reference this metric in software or publications please use this stable URL: https://chaoss.community/?p=3533