Remote Storage
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- rust
- Domain
- distributed-systems
Research direction
Start with the Remote Storage checklist and read issue #13 for the geographic-octant requirement. Identify the relevant provider and client entry points in the repository before breaking the work into single-slice verification, provider, and client tasks. Done means each listed checklist item is implemented and verified.
Written by the indexing model from the issue text.
Description
- Single slice remote verify
- Storage provider
- Providers must indicate geographic octant (0-7) (See #13)
- Storage client
- Dominant language
- Rust
- Stars
- 119
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
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.
More from bitmask-stack/carbonado
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
bitmask-stack/carbonado#31 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
bitmask-stack/carbonado#28 · 1 comment ·
-
Catalog Format v0May be free again @cryptoquick claimed this 1308 days ago, and no pull request is open. Open
bitmask-stack/carbonado#21 · 1 assignee ·
-
Web Storage ProviderOpen
Difficulty 5/5 Over a week Newbie friendliness 25/100
bitmask-stack/carbonado#18 · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
bitmask-stack/carbonado#17 ·
All issues in bitmask-stack/carbonado
Similar issues
-
type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
stackabletech/kafka-operator#1033 · 1 comment ·
Maintainers usually reply within 1 day
-
bug good first issue needs testing
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
farion1231/cc-switch#7744 · 1 comment ·
Maintainers usually reply within 1 day
-
datafusion
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
apache/iceberg-rust#3297 ·
Maintainers usually reply within 1 day