Skip to content

docs: introduce formal RFC and development process#138

Open
moidx wants to merge 3 commits intoOpenPRoT:mainfrom
moidx:rfc-process
Open

docs: introduce formal RFC and development process#138
moidx wants to merge 3 commits intoOpenPRoT:mainfrom
moidx:rfc-process

Conversation

@moidx
Copy link
Copy Markdown
Collaborator

@moidx moidx commented Mar 28, 2026

Summary

This PR establishes a formal development and RFC process for OpenPRoT, ensuring a standardized path for both small and large contributions.

Changes Included

  1. Formal RFC and Development Process:
    • Adds detailing the RFC workflow for large changes.
    • Updates and the root to point to the new process.
    • Includes a Mermaid flow diagram of the contribution path.
    • Adapts criteria for firmware-only project needs (removing hardware-specific concepts like CDC/RDC).
  2. RFC Issue Template:
    • Introduces a standardized GitHub issue template in for Request for Comment (RFC) proposals.

Attribution

The process and templates are adapted from the Caliptra Contributing Process.

@moidx moidx force-pushed the rfc-process branch 2 times, most recently from b798633 to a1e58e9 Compare March 28, 2026 01:46
moidx added 3 commits March 28, 2026 03:18
Introduce a new development-process.md detailing the formal RFC
workflow for large changes, including TSC approval and specific
criteria for architectural or security-critical updates.

Update contributing.md and the root CONTRIBUTING.md to point to this
new process, ensuring a clear and standardized path for both
small and large contributions.

This process is adapted from the Caliptra Contributing Process:
https://github.com/chipsalliance/Caliptra/blob/main/doc/CaliptraContributingProcess.md

Signed-off-by: Miguel Osorio <miguelosorio@google.com>
Introduce a standardized GitHub issue template for Request for
Comment (RFC) proposals. This template guides contributors to
include all necessary details such as scope, rationale,
implementation tradeoffs, and test plans for significant changes.

Signed-off-by: Miguel Osorio <miguelosorio@google.com>
Update introduction.md and getting-started.md to use Bazel and
Pigweed commands (pw presubmit, bazel test), replacing outdated
cargo xtask commands to align with the current project workflow.

Signed-off-by: Miguel Osorio <miguelosorio@google.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants