Version: 1.0 | Date: 2026-06-30 | Status: Draft
-
Executive Summary
Problem Statement: We do not have a consistent platform to develop, test, and build certification tests. This leads to configuration drift, unreproducible test results, and onboarding friction for contributors.
Project Goal: Create a standardized, automated set of virtual machine (VM) and container images capable of building and running RISC-V compliance/certification tests in a highly repeatable, isolated environment.
Target Parent Community: RISC-V ACT (Architectural Compatibility Test) SIG
AI Usage/Expectation: There are no concerns about using AI to help assess and build the metadata to create these artifacts.
Copyright/Patent or other issues/concerns? There are no copyright/patent concerns.
-
Roles & Staffing
Project Lead (Mentor): Greg Sterling/greg@riscv.org
Contributor Skillset: VM/Docker Image Creation
Primary Contributor(s) (Mentees): [Name/Email]
Stakeholder Sponsor: RISC-V International
Estimated Effort: 5-10 hours per week for 5 weeks
-
Phased Build Plan
Phase 1
Setup & Initial PR
Create a GitHub repository to host the infrastructure-as-code recipes (Dockerfiles/Packer scripts). Successfully package baseline versions of spike and gcc tools.
Phase 2
Core Logic / Feature
Develop and validate distinct image matrices:
-
Development Environment: Interactive containers/VMs pre-configured with complete toolchains, debuggers, and IDE hooks for developers.
-
Testing Environment: Lightweight, stripped-down images optimized for rapid execution inside automated CI/CD pipelines to validate PRs.
-
Certification Suite Environment: Locked-down, verifiable images dedicated strictly to compiling, signing, and running the official final test suites.
Phase 3
Upstream / Integration
Submit a comprehensive Pull Request to the parent community/mainline (RISC-V ACT Team) with the final build manifests and automation workflows.
Phase 4
Documentation & Demo
Technical blog post drafted explaining how to pull and deploy the images; demo video recorded; LF Badge awarded.
-
Graduation & Exit Strategy
Select the intended path for this project upon completion:
[ ] Upstream: Merge code into [Parent Project].
[X] Hand-off: Transition to ACT4.
[ ] Incubate: Move toward a formal LF/Eclipse Project.
[ ] Other: [Specify]
-
Maintenance & Support
Post-Graduation Owner: ???
Sunset Criteria: If this project is unable to produce functioning images, it will be sunset.
-
Recognition & Badging
Earnable Badges for this SOW:
[X] First PR Milestone
[X] Upstream Navigator
[X] Dev Partner Project Graduate
Publicity Plan:
Featured article on the RISC-V International Blog
Technical deep-dive demonstration to the ACT4 Team
Potential presentation or lightning talk submission for the RISC-V Summit
Version: 1.0 | Date: 2026-06-30 | Status: Draft
Executive Summary
Problem Statement: We do not have a consistent platform to develop, test, and build certification tests. This leads to configuration drift, unreproducible test results, and onboarding friction for contributors.
Project Goal: Create a standardized, automated set of virtual machine (VM) and container images capable of building and running RISC-V compliance/certification tests in a highly repeatable, isolated environment.
Target Parent Community: RISC-V ACT (Architectural Compatibility Test) SIG
AI Usage/Expectation: There are no concerns about using AI to help assess and build the metadata to create these artifacts.
Copyright/Patent or other issues/concerns? There are no copyright/patent concerns.
Roles & Staffing
Project Lead (Mentor): Greg Sterling/greg@riscv.org
Contributor Skillset: VM/Docker Image Creation
Primary Contributor(s) (Mentees): [Name/Email]
Stakeholder Sponsor: RISC-V International
Estimated Effort: 5-10 hours per week for 5 weeks
Phased Build Plan
Phase 1
Setup & Initial PR
Create a GitHub repository to host the infrastructure-as-code recipes (Dockerfiles/Packer scripts). Successfully package baseline versions of spike and gcc tools.
Phase 2
Core Logic / Feature
Develop and validate distinct image matrices:
Development Environment: Interactive containers/VMs pre-configured with complete toolchains, debuggers, and IDE hooks for developers.
Testing Environment: Lightweight, stripped-down images optimized for rapid execution inside automated CI/CD pipelines to validate PRs.
Certification Suite Environment: Locked-down, verifiable images dedicated strictly to compiling, signing, and running the official final test suites.
Phase 3
Upstream / Integration
Submit a comprehensive Pull Request to the parent community/mainline (RISC-V ACT Team) with the final build manifests and automation workflows.
Phase 4
Documentation & Demo
Technical blog post drafted explaining how to pull and deploy the images; demo video recorded; LF Badge awarded.
Graduation & Exit Strategy
Select the intended path for this project upon completion:
[ ] Upstream: Merge code into [Parent Project].
[X] Hand-off: Transition to ACT4.
[ ] Incubate: Move toward a formal LF/Eclipse Project.
[ ] Other: [Specify]
Maintenance & Support
Post-Graduation Owner: ???
Sunset Criteria: If this project is unable to produce functioning images, it will be sunset.
Recognition & Badging
Earnable Badges for this SOW:
[X] First PR Milestone
[X] Upstream Navigator
[X] Dev Partner Project Graduate
Publicity Plan:
Featured article on the RISC-V International Blog
Technical deep-dive demonstration to the ACT4 Team
Potential presentation or lightning talk submission for the RISC-V Summit