Tests assets - static files or pulled from Roboflow hosting?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.5k
- Forks
- 320
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 133
Description
Search before asking
- I have searched the Inference issues and found no similar feature requests.
Question
Can we pull some from Universe instead to make sure we don't run into any licensing issues?
Supervision has some video assets; wonder if we should also add image assets to their inventory & then use them here instead of including them in the repo.
Question asked here: https://github.com/roboflow/inference/pull/343#discussion_r1586644576
Additional
No response
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 discussion linked from pull request #343 and inspect how the current test assets are stored or retrieved. Compare the licensing and availability implications of static repository files with Roboflow Universe or Supervision assets. Done means the project has a decided, documented source for these assets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- computer-vision, testing-qa
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100