Skip to content

MAINTAINERS.md

CeloHT edited this page Aug 1, 2026 · 1 revision

MAINTAINERS.md

CeloHT Maintainers

Overview

The CeloHT Maintainers are trusted community members responsible for maintaining the quality, security, stability, and long-term sustainability of the CeloHT ecosystem.

Maintainers review contributions, guide contributors, enforce project standards, and help ensure that CeloHT remains an open, transparent, and community-driven project.


Responsibilities

Maintainers are expected to:

  • Review Pull Requests.
  • Review and triage Issues.
  • Maintain project documentation.
  • Enforce the Code of Conduct.
  • Ensure code quality and consistency.
  • Improve developer experience.
  • Coordinate releases.
  • Review security-related changes.
  • Mentor new contributors.
  • Participate in governance discussions.
  • Promote transparency in project decisions.

Expectations

Every maintainer should:

  • Act with integrity.
  • Be respectful and professional.
  • Make decisions in the best interest of the community.
  • Encourage open collaboration.
  • Respond to community feedback.
  • Maintain transparency whenever possible.
  • Protect the project's security and reputation.

Becoming a Maintainer

Maintainers are selected based on:

  • Consistent, high-quality contributions.
  • Technical expertise.
  • Community involvement.
  • Constructive communication.
  • Commitment to CeloHT's mission and values.
  • Demonstrated leadership.

There is no fixed timeline. Selection is based on merit and community trust.


Decision-Making

Maintainers work collaboratively whenever possible.

For significant technical or governance decisions, maintainers seek community input and follow the project's governance process.

See:

  • GOVERNANCE.md
  • DECISION_PROCESS.md
  • VOTING_SYSTEM.md

Conflict of Interest

Maintainers must disclose any conflicts of interest that could influence project decisions.

When appropriate, they should recuse themselves from discussions or decisions where impartiality could be compromised.


Inactive Maintainers

A maintainer may be considered inactive if they:

  • Have not participated in reviews or discussions for an extended period.
  • No longer wish to serve.
  • Repeatedly fail to uphold project standards.

Inactive maintainers may be moved to an emeritus status or removed after community discussion.


Current Maintainers

Founder

Johnny Dubic

Founder of CeloHT and steward of the project's long-term vision.

Community Maintainers

Additional maintainers are appointed by the community as the ecosystem grows.

This section will be updated as new maintainers join the project.


Contact

For maintainer-related questions or requests, please use the official GitHub Discussions or Issues, or other official CeloHT communication channels.


Related Documents

  • COMMUNITY.md
  • CODE_OF_CONDUCT.md
  • CONTRIBUTING.md
  • GOVERNANCE.md
  • DECISION_PROCESS.md
  • SECURITY.md

Maintained by the CeloHT Community

Welcome to the official CeloHT documentation. This knowledge base provides comprehensive documentation for users, developers, contributors, partners, researchers, and ecosystem participants. Explore architecture, APIs, smart contracts, developer guides, governance, security, educational resources, roadmap, transparency reports, and community initiatives. Built with openness, collaboration, and long-term sustainability in mind, the CeloHT documentation follows international open-source documentation standards to make learning, building, and contributing accessible to everyone.

Clone this wiki locally