Requests for comment on platform ideas, forum changes, and system proposals before formal decisions.
RFC
RFC means Request for Comment.
This category is for open discussion, review, and feedback before an idea becomes a formal proposal, implementation plan, or BIP.
Use RFC when a change needs input, disagreement, clarification, tradeoff analysis, or early review before it becomes official.
RFC topics are not final decisions.
What Belongs Here
- platform feedback
- forum structure discussions
- proposed category changes
- early governance ideas
- policy questions
- workflow or automation proposals
- user experience improvements
- technical design discussions
- tradeoff reviews
- ideas that may later become BIPs
RFC vs BIP
| RFC | BIP |
|---|---|
| Open discussion | Formal proposal |
| Used before decisions | Used for decision-making |
| Exploratory | Structured |
| Community review and critique | Voting, approval, rejection, or implementation |
| Can be rough or unresolved | Should be clear enough to evaluate |
How to Participate
- Read the request: understand the proposed idea or question.
- Comment on tradeoffs: explain benefits, risks, edge cases, and alternatives.
- Ask for clarity: identify missing context or unclear assumptions.
- Suggest improvements: help refine the idea.
- Track outcome: the RFC may be closed, archived, implemented, or converted into a BIP.
Status Labels
When useful, RFC topics may be marked as:
- Open: accepting comments
- Needs clarity: missing key information
- Under review: being evaluated by moderators or admins
- Converted to BIP: moved into formal proposal process
- Implemented: acted on directly
- Rejected: not moving forward
- Archived: preserved for reference