Use JSON syntax aware approach for defining manufacturing images
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Refactor
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- rust
- Domain
- build-system
Research direction
The issue proposes replacing textual patch files with a JSON syntax-aware, mk_rom_config()-style approach for defining manufacturing images. Start by locating the manufacturing image definitions and the existing mk_rom_config() implementation; done would require an agreed scope and validation that the image definitions work through the new approach.
Written by the indexing model from the issue text.
Description
I think it might have been better to use the JSON syntax aware mk_rom_config()-style approach for this, rather than textual patch files -- but we need to get moving so we'll use it as-is for now. Thanks!
Originally posted by @jclulow in https://github.com/oxidecomputer/helios/pull/230#pullrequestreview-3424925918
- Dominant language
- Rust
- Stars
- 481
- Forks
- 21
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 2
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from oxidecomputer/helios
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
oxidecomputer/helios#254 ·
-
oxidecomputer/helios#268 · 1 comment · 1 assignee ·
-
oxidecomputer/helios#252 · 1 comment · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
oxidecomputer/helios#245 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
oxidecomputer/helios#238 · 2 comments ·
All issues in oxidecomputer/helios
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gitbutlerapp/gitbutler#15998 · 1 comment ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100