Publish a blob-storage port
- Dominant language
- Go
- Stars
- 0
- Forks
- 0
- Avg merge
- 3h 18m
- Merged PRs (30d)
- 26
Description
Moved off `roadmap.md`'s *Published Contract Candidates* table, where the verdict was **Publish**.
`Put`/`Get`/`Delete`/`SignedURL` over S3, R2, GCS, Azure, MinIO or local disk. Well-understood shape, many real backends, low design risk — it clears the bar in `roadmap.md` comfortably, since third parties writing adapters for their own storage backend is routine.
**Sequencing rule applies:** publish only once a second implementation actually exists, so its shape is observed rather than guessed. Blocked on the Object & Blob Storage feature pack (Pack C in `README.md`).
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with Pack C in README.md and the published-contract decision in roadmap.md, then inspect the Object & Blob Storage feature pack and its existing implementations. Done means a blob-storage port covering Put, Get, Delete, and SignedURL is published only after a second implementation exists.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, azure, go, google-cloud
- Domain
- api, backend, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100