paritytech / paritytech/web3-storage
Productionalize and Fine-Tune
Open
Nobody has claimed this yet.
enhancement
good first issue
- Dominant language
- Rust
- Stars
- 12
- Forks
- 3
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 33
Description
Tracking issue (for Q2>=)
Specific issues will be created as sub-tasks.
Hints
- review all the stuff and implementations
- clean the repo structure
- clean the provider-node structure (submodules/subdirs)
- refactor, simplify, remove what is not needed, de-claude
- correct logging (target + structured)
- cli and setup
-
#[allow(dead_code)] - ...
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 broad tracking issue rather than a self-contained task. Start by reviewing the repository structure and any sub-tasks, then inspect the provider-node layout, logging, CLI, and setup areas named here. Done requires the specific cleanup, refactoring, logging, and setup goals to be split into defined tasks with clear completion checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, cli, tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100