Governance

Dayu was founded by Dislab at Nanjing University. We welcome contributors from academia, industry, and the wider open-source community. Affiliation does not confer a seat, a vote, or repository access.

This page introduces the project's governance. GOVERNANCE.md is the authoritative policy; MAINTAINERS.md records system roles.

Who does what?

Role or office	Responsibility
Contributor	Contribute code, documentation, tests, research validation, review, triage, or support. No appointment is needed.
Maintainer	Steward repository-wide technical quality, compatibility, reviews, releases, and contributor support.
TSC member	Steward project direction, governance, community continuity, and unresolved disputes.
TSC Chair / Vice Chair	Coordinate TSC discussions, records, representation, and follow-up.

Review is open to qualified contributors. Dayu has no separate Committer rank. TSC membership and maintenance are independently held responsibilities. Officer titles do not add votes or grant technical approval or administration rights. Meet the people holding these responsibilities on the Committee page.

How are decisions made?

Discuss technical work in issues and PRs, seek consensus, and record the reasoning. Routine work follows independent Maintainer review. Significant changes need a design discussion and two independent technical approvals, including a Maintainer; see review requirements.

Unresolved disputes go to the TSC. Formal decisions identify eligible voters, conflicts, the deadline, explicit votes, and the outcome. An individual holding several roles counts once. Governance changes, TSC membership, and officer appointments follow the policy's formal thresholds.

Read the decision and conflict rules for voting thresholds, recusals, and continuity arrangements.

How can I become a Maintainer?

Anyone may express interest or nominate a Contributor. Assessment considers sustained contributions, technical and review judgment, collaboration, architectural understanding, and willingness to take responsibility. There is no fixed PR-count, employment, tenure, or weekly-time requirement.

A current Maintainer coordinates the nomination and feedback. Appointment requires independent support and resolution of substantive objections, followed by the candidate's acceptance, a recorded scope, and verified access. TSC membership and officer appointments follow their own governance process. The appointment rules explain the requirements and the process for appeals.

How are conflicts and conduct concerns handled?

People recuse themselves from their own appointment or removal and from decisions involving a direct personal conflict. Sharing an institution alone is not a conflict. Sensitive personnel and conduct matters are handled privately, with appropriate public outcomes that preserve confidentiality.

Use the conduct-reporting contacts and follow the Code of Conduct. Security reports have a separate private reporting process.

What happens when someone steps back?

Members can discuss reduced availability, handover, or Emeritus status. The project reviews the roster and access at least every six months. Graduation or a change of employer does not automatically end a role. Historical contribution credit is retained as responsibilities and access change. See the availability and transition rules.

Where are the detailed rules?

• Governance policy
• System roster
• Contribution workflow
• OWNERS and review guide
• Community administration

Website maintenance has its own roster and contribution workflow.