nspcc-dev / nspcc-dev/neofs-node
Inline SN internals from SDK
Open
Nobody has claimed this yet.
enhancement
I4
S2
U4
- Dominant language
- Go
- Stars
- 38
- Forks
- 51
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 38
Description
- reputation
- container size estimations
- ???
client apps aint interested in them. They are likely to be changed huge. Easier to support in single repo
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
No files, tests, or entry points are identified. Start by locating the SDK internals for reputation and container-size estimation, then clarify the scope, including the unresolved “???” item. Done means the agreed internals are supported in the single repository rather than exposed through the SDK.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100