Skip to content

Latest commit

 

History

History
62 lines (41 loc) · 3.47 KB

project-access.md

File metadata and controls

62 lines (41 loc) · 3.47 KB
Raw

Project Access

Question: To what extent does your project provide access and help those with various access needs?

Overview

Project Access: measures how accessible different parts of the project are for community members and new contributors. Data points consist of an assessment of potential barriers to access, such as technology, governance, resources, internet access, or inattention to accessibility concerns. Open source projects should be accessible to all. Community members and maintainers want their projects to be as accessible as possible for all with an interest in contributing. By documenting and cataloging measures to improve access taken by the project team, community members can be empowered to contribute to a project and take on leadership roles more easily and transparently. Considerations for access may include physical ability, neurodiversity, a contributor’s location, their native language, available internet bandwidth, or other potential barriers to participating in an open source project.

Depending on the size of the project, the key considerations for project accessibility, includes code and documentation access, platform compatibility, adherence to accessibility standards, global-friendly meeting formats, diverse communication methods, support for non-code contributions, global mentorship programs, regional chapters, and translation support.

Want to Know More?

Click to read more about this metric.

Data Collection Strategies

There are several different ways to signal attention to this metric which may include:

  • Survey the community about project access. Potential survey questions for community members include:
    • [Survey Likert Item 1-x] The code and documentation are easily available to me
    • [Survey Likert Item 1-x] The project has a public-facing repository that is easy to contribute to
    • [Survey Likert Item 1-x] The project has a system for periodic accessibility audits
    • [Survey Likert Item 1-x] The project has meetings in different global locations
    • [Survey Likert Item 1-x] The project actively reaches out to a diverse, global population for contributions or support
  • Perform regular accessibility audits
  • Perform regular reviews of project Event Location Inclusivity, Documentation Accessibility, and Chat Platform Inclusivity

Filters

  • Type of access provided (e.g., translation, meeting times, documentation, chat platform)
  • Goal of access (e.g., international inclusion, accessibility)

References

Contributors

  • Matt Germonprez
  • Kevin Lumbard
  • Elizabeth Barron
  • Anita Ihuman
  • Sean Goggins
  • Armstrong Foundjem
  • Peculiar C Umeh

Additional Information

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=4953