operatorai / operatorai/modelstore
Figure out how modelstore can be fully functional with write-only storage
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 403
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
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
Start with the Slack discussion linked in the issue, then inspect modelstore's storage-provider entry points to determine what “write-only storage” requires. The issue does not identify files, tests, expected behavior, or acceptance criteria, so the work is not complete until those requirements and a verifiable definition of full functionality are established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100