oxidecomputer / oxidecomputer/opte
MVP hit list
Open
Nobody has claimed this yet.
mvp
- Dominant language
- Rust
- Stars
- 77
- Forks
- 11
- Avg merge
- 9d 20h
- Merged PRs (30d)
- 8
Description
Tracking issue for MVP-focused work
Current
- https://github.com/oxidecomputer/opte/issues/231
- https://github.com/oxidecomputer/opte/issues/10
- https://github.com/oxidecomputer/opte/issues/197
Next up
- https://github.com/oxidecomputer/opte/issues/234
- https://github.com/oxidecomputer/opte/issues/196
- https://github.com/oxidecomputer/opte/issues/42
- https://github.com/oxidecomputer/opte/issues/61
- https://github.com/oxidecomputer/opte/issues/74
- https://github.com/oxidecomputer/opte/issues/160
- https://github.com/oxidecomputer/opte/issues/211
- https://github.com/oxidecomputer/opte/issues/228
- https://github.com/oxidecomputer/opte/issues/221
Blocked
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
This is a tracking issue rather than a self-contained code task. Start by reviewing the unchecked linked issues in the “Next up” section and their current status; this issue is done when the listed MVP work is completed or the checklist is updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100