Quira Quira Docs
GitHub Star

RFC Process

Not all changes go through a standard PR. Significant changes to Quira's architecture, public APIs, or user-facing behavior require an RFC (Request for Comments).

When is an RFC needed?

  • New features that change the UI or user workflow
  • Changes to the Graph Query API or Plugin API
  • Architectural changes (new dependencies, storage format changes)
  • Changes to the data model or privacy guarantees

RFC workflow

  1. Submit EOpen a PR to the rfcs/ directory with your proposal following the RFC template.
  2. Review period E2-week comment period for community feedback and discussion.
  3. Decision EMaintainers approve, request changes, or close the RFC with rationale.
  4. Implementation EApproved RFCs are tracked as issues and assigned to contributors.
← Previous: Pull Requests Next: Plugin API →
Was this page helpful?
Ask AI
Q

Ask anything about the documentation

Ctrl+K to open anytime