MAINTAINERS

This document lists the official maintainers of the Dyne framework and describes their responsibilities, permissions, and expectations.

Current Maintainers

Primary Maintainers

Individuals with full decision-making authority over the project:

  • Tabot Kevin (Lead Maintainer & Project Creator) - GitHub: https://github.com/tabotkevin - Responsibilities: architecture, releases, governance, App design, security oversight.

Additional maintainers may be added as the project grows.

Roles and Responsibilities

Lead Maintainer

  • Defines project roadmap and long-term strategy

  • Oversees major architectural changes

  • Approves breaking changes

  • Manages releases and versioning

  • Coordinates RFC review

  • Oversees security review and responsible disclosure

Core Maintainers

Responsible for daily project operations:

  • Review and merge pull requests

  • Manage issue triage and labeling

  • Maintain documentation structure

  • Ensure code consistency and style compliance

  • Participate in architectural discussions

  • Guide contributors and provide feedback

Contributor Expectations

  • Follow the Contributing Guide and Code of Conduct

  • Use semantic commits (Conventional Commits)

  • Write documentation and tests for all features

  • Open an issue before implementing large changes

  • Participate constructively in discussions

Becoming a Maintainer

New maintainers may be invited based on:

  • Quality and consistency of contributions

  • Demonstrated understanding of Dyne’s architecture

  • Constructive engagement in issue discussions

  • Helpfulness toward the community

  • Long-term interest in the health of the project

Maintainers are added by the Lead Maintainer following a proposal and internal review.

Maintainer Inactivity

A maintainer may be marked inactive if:

  • No contributions or participation for 6 months, or

  • They request to step back

Inactive maintainers may return by notifying the Lead Maintainer.

Decision Making

Dyne follows a consensus-based governance model:

  • Minor decisions: handled by any core maintainer

  • Major changes: require consensus from active maintainers

  • Breaking changes: approval of the Lead Maintainer is required

If consensus is not reached, the Lead Maintainer makes the final decision.

Contact

For maintainer-related concerns, email:

maintainers@dyne.run