oxidecomputer / oxidecomputer/opte
convert TODOs into issues
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 77
- Forks
- 11
- Avg merge
- 9d 20h
- Merged PRs (30d)
- 8
Description
There are many TODOs in the codebase. Some of these are overarching and probably don't fit neatly in a single issues, but many are probably small/medium scoped tasks that just need work done. Take some time to comb over the TODOs and create new issues where it makes sense. Leave the TODOs in the code; they still serve as a constant nudge of things needing to be done.
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
Search the codebase for TODOs and review them individually. Create new issues for TODOs that represent small or medium scoped work, while leaving the original TODOs in place; broader TODOs may not need separate issues.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100