Skip to content

NOC Governance

This document defines the governance structure of the NOC project and the decision-making process.

Roles

Leader

The project is currently led by Dmitry Volodin.

The Leader is responsible for the strategic direction of the project and has final authority on governance decisions.

The Leader may delegate responsibilities to other project members when appropriate.

The governance model may evolve as the project and community grow.

Core Team

The Core Team consists of trusted contributors who participate in project governance.

The Core Team is responsible for:

  • Reviewing and voting on NEPs and NPSs
  • Discussing important project decisions
  • Maintaining the long-term direction and health of the project
  • Proposing new Core Team members

Core Team members may have one of the following statuses:

  • Active — participating in project activities and governance
  • Dormant — no meaningful participation in the project for more than 12 months
  • Retired — voluntarily stepped down or removed from the Core Team

Dormant members may return to the Core Team by reapplying and receiving majority support.

Developers

Anyone contributing code, collections, documentation, tests, or tooling to NOC is considered a Developer.

Developers contribute by:

  • Improving the codebase
  • Adding new functionality
  • Fixing issues
  • Improving documentation
  • Participating in discussions and reviews

Users

Anyone using NOC in production or evaluation is considered a User.

Users are encouraged to:

  • Report issues
  • Provide feedback
  • Participate in discussions
  • Suggest improvements

Decision Making

Project-wide decisions are made through NEP or NPS proposals.

The decision process:

  1. A proposal enters the voting phase.

  2. Active Core Team members vote:

  3. Pro — support the proposal

  4. Contra — reject the proposal

  5. Abstain — no vote

  6. A vote is valid if more than half of eligible voters participate.

Eligible voters are Active Core Team members excluding the proposal author.

  1. A proposal is accepted if it receives a majority of votes cast.

  2. Accepted proposals are presented to the Leader for final approval.

The Leader may:

  • Accept the proposal
  • Veto the proposal

Core Team Membership

A contributor may become a Core Team member if:

  • They are nominated by at least two Active Core Team members.
  • They have demonstrated sustained contribution and commitment to the project.

New Core Team members are accepted through the standard voting process.

Core Team membership is maintained while the member remains active and trusted by the project.

Suspension and Ban

The project may restrict participation of individuals or organizations that harm the project or violate its rules.

Possible actions:

  • Suspension — temporary restriction from participation
  • Ban — permanent removal from project activities

Reasons may include:

  • Serious violations of the Code of Conduct
  • License violations
  • Abuse of project resources
  • Attempts to disrupt project development or governance
  • Harassment or threats against project participants

Any Active Core Team member may propose suspension or ban.

The standard voting process is used for decisions.

The Leader may take immediate action in urgent cases.

Restoration

Suspended participants may be restored after the reasons for suspension have been resolved.

Restoration requires approval through the standard decision process.