oxidecomputer / oxidecomputer/daft

Make oxnet depend on daft (instead of the other way around)

Open
#72 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
78
Forks
6
PR merge metrics
No merged PRs in 30d

Description

Currently, daft relies on oxnet as a dependency for its oxnet01 feature. This forces patching of oxnet in Omicron and other places when testing out oxnet changes (locally or via commit). Ideally, oxnet should rely on daft as a dependency/feature, simplifying versioning, etc.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how daft currently exposes the oxnet01 feature and how oxnet would depend on daft. Review the dependency and feature definitions in both projects, then confirm the intended direction with the maintainers. Done means oxnet changes no longer require patching oxnet through daft or Omicron, with dependency resolution and relevant builds passing.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
build-system
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.