oxidecomputer / oxidecomputer/rfd-site
Making the process of creating and editing RFDs more accessible for non-engineers
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 214
- Forks
- 22
- Avg merge
- 6d 4h
- Merged PRs (30d)
- 12
Description
Currently, the process is pretty involved, especially if you're not used to dealing with git and AsciiDoc.
Dropping this issue here as a scratch pad for ways in which we can make the process of creating and editing RFDs more accessible for non-engineers and more intuitive for all.
- Ability to create RFD from the site
- Quick edit—perhaps linking to the github .dev link for a browser based editor
- AsciiDoc reference
- Grab raw AsciiDoc code from another RFD
- Inline GitHub PR info; comments, last commented on, showing diffs
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.
Research direction
The issue names no files, tests, or entry points and is a scratch pad covering several possible improvements to creating and editing RFDs. Start by mapping the current site-based and Git-based RFD workflow, then narrow the scope to one defined change with a clear completion criterion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github
- Domain
- developer-experience, documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100