Skip to content

RFC_PROCESS.md

Latest commit

 

History

History
55 lines (38 loc) · 1.34 KB

RFC_PROCESS.md

File metadata and controls

55 lines (38 loc) · 1.34 KB
Raw

RFC Process

Major features and architectural changes go through an RFC (Request for Comments) process.

When to Write an RFC

An RFC is required for:

  • New Kafka API implementations
  • Changes to the wire protocol or storage format
  • New module additions (feature flags)
  • Breaking changes to public APIs
  • Cross-repo architectural decisions

An RFC is NOT required for:

  • Bug fixes
  • Documentation improvements
  • Test additions
  • Minor refactors within a module

Process

  1. Draft: Open a PR in the core repository under docs/rfcs/ using the template below
  2. Discussion: Minimum 1-week review period. Maintainers and community provide feedback
  3. Decision: Maintainers approve, request changes, or close the RFC
  4. Implementation: Approved RFCs are linked to tracking issues

Template

# RFC-NNN: Title

## Summary
One paragraph explanation.

## Motivation
Why are we doing this? What problems does it solve?

## Design
Detailed technical design. Include code examples where helpful.

## Alternatives Considered
What other approaches were evaluated and why were they rejected?

## Migration
How do existing users migrate? Is this backwards-compatible?

## Unresolved Questions
What aspects are still open?

Existing RFCs

See Architecture Decision Records for past decisions.

Last updated: 2026-02-20