RFC Index
Complete index of Request for Comments (RFCs) for the PromptPack specification.
Overview
The RFC (Request for Comments) process is how the PromptPack community proposes, discusses, and adopts changes to the specification. This index tracks all RFCs from proposal to implementation.
RFC Status Definitions
- 📝 Draft - Initial proposal under discussion
- 🔍 Review - Formal review period, seeking feedback
- ✅ Accepted - Approved for implementation
- 🚀 Implemented - Changes merged into specification
- ❌ Rejected - Not accepted (with reasoning)
- ⏸️ Deferred - Postponed to future consideration
Active RFCs
| RFC | Status | Title |
|---|---|---|
| RFC-0001 | 🚀 Implemented | Core PromptPack Schema |
| RFC-0002 | 🚀 Implemented | YAML File Format |
| RFC-0003 | 🚀 Implemented | Template Variable System |
| RFC-0004 | 🚀 Implemented | Multimodal Content Support |
| RFC-0005 | 📝 Draft | PromptPack Workflow Specification Extension |
| RFC-0006 | 🚀 Implemented | Evals Extension |
Upcoming Considerations
Future v1.x Enhancements
- Enhanced Testing Framework: More sophisticated test definitions
- Plugin System: Extensible runtime capabilities
- Performance Metadata: Benchmarking and optimization hints
- Internationalization: Multi-language prompt support
Future Versions
- Advanced Workflows: Conditional logic and branching
- Real-time Collaboration: Multi-user prompt development
- AI-Assisted Generation: Automated prompt optimization
- Enterprise Features: Advanced security and governance
How to Propose an RFC
1. Before You Start
- Search Existing RFCs: Check if your idea has been discussed
- Join Discussions: Participate in community conversations
- Gather Feedback: Get initial community input
- Consider Alternatives: Explore different approaches
2. Writing Your RFC
Use our RFC Template:
- Summary: Brief description of the proposal
- Motivation: Why this change is needed
- Detailed Design: Technical specification
- Drawbacks: Potential downsides and concerns
- Alternatives: Other approaches considered
- Adoption Strategy: How users will migrate
3. Submission Process
- Create Issue: Use the RFC template on GitHub
- Community Discussion: Gather feedback and iterate
- Formal Review: RFC enters official review period
- Decision: Community and maintainers make final decision
- Implementation: Approved RFCs get implemented
4. Review Criteria
RFCs are evaluated on:
- Technical Merit: Sound design and implementation
- Community Benefit: Value to PromptPack users
- Specification Fit: Alignment with core principles
- Implementation Feasibility: Practical to build and maintain
- Backward Compatibility: Impact on existing users
RFC Templates
Quick Links
Example RFCs
Learn from implemented RFCs:
- RFC-0001: Core Schema - Comprehensive technical design
- RFC-0002: YAML Format - User experience focused
- RFC-0003: Variables - Implementation details
- RFC-0004: Multimodal Support - Adding image/audio/video support
Community Guidelines
Participation
- Be Respectful: Constructive feedback and civil discourse
- Stay Focused: Keep discussions relevant to the RFC
- Provide Evidence: Support arguments with examples and data
- Consider Impact: Think about effects on all users
Quality Standards
- Clear Writing: Easy to understand proposals
- Complete Design: Address edge cases and integration
- Real Examples: Concrete use cases and code samples
- Migration Path: How existing users will adopt changes
Statistics
| Metric | Count |
|---|---|
| Total RFCs | 6 |
| Implemented | 5 |
| In Review | 0 |
| Draft | 1 |
| Contributors | 1+ |
Get Involved
Ready to shape the future of PromptPack? Here's how to get started:
- 🔍 Explore: Review existing RFCs and discussions
- 💡 Ideate: Identify improvements or new features
- 📝 Draft: Write your RFC using our template
- 🗣️ Discuss: Engage with the community for feedback
- 🚀 Implement: Help build approved RFCs