Skip to content

MAINTAINERS.md

Latest commit

 

History

History
169 lines (126 loc) · 4.55 KB

MAINTAINERS.md

File metadata and controls

169 lines (126 loc) · 4.55 KB

Maintainers

This document lists the maintainers of the Accessibility Everywhere project.

Current Maintainers

Project Lead

  • Role: Project direction, strategy, partnerships
  • Responsibilities:
    • Overall project vision
    • Search engine outreach
    • Standards proposals (W3C, ISOC)
    • Funding and sustainability
  • Contact: lead@accessibility-everywhere.org

Technical Lead

  • Role: Architecture, core development
  • Responsibilities:
    • Technical architecture decisions
    • Code review and merge authority
    • Infrastructure management
    • Security coordination
  • Contact: tech@accessibility-everywhere.org

Community Manager

  • Role: Community engagement, documentation
  • Responsibilities:
    • Community outreach and support
    • Documentation maintenance
    • Conference submissions and speaking
    • Social media and marketing
  • Contact: community@accessibility-everywhere.org

Emeritus Maintainers

(None yet - project launched 2024)

Becoming a Maintainer

Maintainers are added based on sustained, high-quality contributions and community involvement.

Criteria

  1. Technical excellence: Consistent high-quality code contributions
  2. Project knowledge: Deep understanding of codebase and architecture
  3. Community engagement: Active in discussions, reviews, support
  4. Alignment: Commitment to project mission and values
  5. Time commitment: Able to dedicate regular time (minimum 10 hours/month)
  6. Trust: Demonstrated judgment and responsibility

Process

  1. Nomination: Any existing maintainer can nominate a contributor
  2. Discussion: Maintainers discuss the nomination (private)
  3. Vote: Unanimous approval required from current maintainers
  4. Invitation: Nominee is invited to join maintainer team
  5. Onboarding: Access granted, responsibilities explained
  6. Announcement: Public announcement to community

Maintainer Responsibilities

Code Review

  • Review pull requests within 48 hours
  • Provide constructive, actionable feedback
  • Ensure WCAG compliance on all contributions
  • Verify tests pass and code meets standards

Issue Triage

  • Label and prioritize new issues
  • Close duplicates and invalid reports
  • Direct contributors to relevant resources
  • Escalate critical bugs

Releases

  • Participate in release planning
  • Test release candidates
  • Update CHANGELOG.md
  • Coordinate release announcements

Community

  • Answer questions (GitHub, Discord, email)
  • Welcome new contributors
  • Enforce Code of Conduct
  • Foster inclusive environment

Strategy

  • Participate in roadmap discussions
  • Provide input on feature priorities
  • Represent project at conferences
  • Build partnerships

Decision Making

Consensus Model

We use lazy consensus for most decisions:

  • Proposal posted publicly (GitHub issue/discussion)
  • 7-day review period
  • If no objections, proposal passes
  • Any maintainer can raise concerns for further discussion

Voting

Required for:

  • Adding/removing maintainers
  • Major architectural changes
  • License changes
  • Code of Conduct updates

Process:

  • Simple majority for most votes
  • Unanimous for maintainer changes
  • Quorum: 50% of maintainers must participate

Vetoes

Any maintainer can veto decisions that:

  • Violate Code of Conduct
  • Compromise security
  • Break accessibility compliance
  • Contradict project mission

Vetoes must include clear reasoning and alternative proposals.

Stepping Down

Maintainers can step down at any time:

  1. Notify other maintainers
  2. Transfer ongoing responsibilities
  3. Move to emeritus status
  4. Public thank you announcement

Removal

Maintainers may be removed for:

  • Prolonged inactivity (6+ months)
  • Code of Conduct violations
  • Security negligence
  • Breach of trust

Process:

  1. Private discussion among other maintainers
  2. Attempt to resolve issues first
  3. Unanimous vote required for removal
  4. Access revoked immediately
  5. Public statement (or private, depending on circumstances)

Contact

General maintainer contact: maintainers@accessibility-everywhere.org

Individual contacts: See current maintainers section above

Governance

This project uses benevolent dictatorship governance transitioning to meritocracy:

Current phase: Single founder/lead (2024) Target phase: Maintainer committee (2025 when 3+ active maintainers) Future phase: Foundation/non-profit (2026+ if project scales)

Acknowledgments

Special thanks to maintainers past and present for their dedication to making the web accessible to all.

Last updated: 2024-01-22 Document version: 1.0