Open-EO / Open-EO/openeo-python-driver
Eliminate hardcoded VITO references and resources
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12
- Forks
- 8
- Avg merge
- 6d 3h
- Merged PRs (30d)
- 4
Description
With the "VITO" backend being deployed in multiple places and environments (and even more to come), I think we should clean up all hardcoded VITO references to avoid unintended, accidental coupling
Contributor guide
No contributing guide indexed for this repository
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 by searching the repository for hardcoded "VITO" references and resources, then group the matches by deployment or environment use. Define the replacement configuration or abstraction before changing them; done means no unintended VITO coupling remains across supported deployments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100