Skip to content

Latest commit

 

History

History
63 lines (44 loc) · 2.74 KB

ROADMAP.md

File metadata and controls

63 lines (44 loc) · 2.74 KB

ROADMAP

The OpenEBS ROADMAP lives within the main repo.

Roadmap change process

For a CNCF sandbox project with a small maintainer team, the roadmap change process should be lightweight, pragmatic, and efficient, while still being transparent and community-driven. The process below balances inclusiveness with agility.

1. Principles

  • Keep it Simple: Avoid bureaucratic overhead while maintaining transparency.
  • Consensus First: Decisions should aim for agreement among maintainers, with voting as a fallback.
  • Community Input, Maintainer Decision: Contributors and users provide feedback, but maintainers make the final call.
  • Code of Conduct Compliance: Discussions follow the CNCF Code of Conduct.

2. Change Request Process

2.1 Proposal Submission

  • Where? Submit a GitHub Issue or a Pull Request modifying docs/roadmap.md.
  • What to include?
    • Brief description of the change (e.g., new feature, priority shift).
    • Why it matters (business or technical impact).
    • Potential risks (breaking changes, complexity, etc.).
    • Expected timeline (if applicable).

2.2 Quick Community Discussion (Asynchronous & Lightweight)

  • Proposal is open for discussion for at least 5 business days.
  • Discussion happens via:
    • GitHub Issue comments (preferred)
    • Pull Request
    • CNCF Slack
    • Monthly community call (if timing aligns)
  • Feedback is encouraged but optional – if no objections are raised, the process moves forward.

2.3 Maintainer Decision

  • After discussion, maintainers assess the proposal.
  • Approval Criteria:
    • If 66%+ of maintainers agree and there are no strong objections, the change is accepted.
    • If there's disagreement, maintainers discuss internally and vote if needed (66% majority wins).
    • Decision is documented on GitHub (Issue/PR closed with final reasoning).

2.4 Implementation & Communication

  • Once approved:
    • The roadmap (OpenEBS ROADMAP) is updated.
    • The change is shared in the next community update (GitHub Discussions, Slack, or meeting notes).

3. Conflict Resolution

  • If a proposal is contested:
    • Maintain a respectful discussion in line with the Code of Conduct.
    • If needed, bring in an external CNCF mentor for mediation.
    • If deadlocked, escalate to the CNCF TOC for a neutral decision.

4. Continuous Process Review

  • Periodically, maintainers review and adjust the roadmap change process based on project needs.