Use markdown as source of truth for RISC profile
Open
Nobody has claimed this yet.
wg-process
- Dominant language
- Makefile
- Stars
- 78
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
Right now, RISC profile is defined in xml. This makes it hard to edit/maintain. We use markdown instead.
Not required for v1. Just an dev experience thing.
Contributor guide
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.
Research direction
Locate the current XML definition of the RISC profile and check the repository for any existing Markdown source or generation workflow. Determine how the profile is consumed and what validation is available; done means Markdown is the maintained source of truth without changing the resulting profile.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- markdown, xml
- Domain
- developer-experience
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100