NOC Enhancement Proposals (NEPs)

NOC NEPs are formal design documents describing proposed improvements to the NOC platform.
They capture architectural changes, new features, standards, or significant process updates that affect the platform and its ecosystem.

NEPs are created and maintained by the NOC core team, but contributions, feedback, and discussion from the wider community are welcome.

Each NEP follows a structured review and acceptance process and serves as a permanent record of major decisions in the evolution of NOC.

NEP Workflow

The NEP process follows these stages:

1. 📝 Draft — A new NEP is written and submitted as a draft, typically as a pull request.
2. 💬 Discussion — The NEP is reviewed, discussed, and possibly revised.
3. ✅ Accepted — Once consensus is reached, the NEP is approved and marked as Accepted.
4. 🛠️ In Progress — The NEP has been accepted and is currently being implemented.
5. ❌ Rejected — NEPs that are not approved are marked as Rejected.
6. 🚀 Done — NEPs that have been fully implemented and deployed may be marked as Done.

stateDiagram-v2
    draft: 📝 Draft
    discussion: 💬 Discussion
    accepted: ✅ Accepted
    inprogress: 🛠️ In Progress
    rejected: ❌ Rejected
    done: 🚀 Done
    [*] --> draft
    draft --> discussion
    discussion --> draft
    draft --> rejected
    discussion --> accepted
    discussion --> rejected
    accepted --> inprogress
    inprogress --> done

Index of NEPs

NEP	Title	Author	Status
NEP-0000	NOC Enhancement Proposal Process	Dmitry Volodin	🚀 Done
NEP-0001	NOC Problem Statement Process	Dmitry Volodin	🚀 Done
NEP-0002	NOC Governance	Dmitry Volodin	🚀 Done
NEP-0100	Resources	Dmitry Volodin	✅ Accepted
NEP-0101	NOC Packaging	Dmitry Volodin	💬 Discussion
NEP-0102	NOC Deploy Configuration Protocol	Dmitry Volodin	💬 Discussion
NEP-0103	Collections Bundling	Dmitry Volodin	✅ Accepted
NEP-0104	Configurable Uniqueness Constraints	Dmitry Volodin	✅ Accepted

❌ Rejected: 0 🛠️ In Progress: 0 🚀 Done: 3 📝 Draft: 0 ✅ Accepted: 3 💬 Discussion: 2