Open-EO / Open-EO/openeo-python-driver
Introduce more automated code quality tooling
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12
- Forks
- 8
- Avg merge
- 6d 3h
- Merged PRs (30d)
- 4
Description
With more people joining the dev team and less time for fighting technical debt and deeper PR reviews, I propose to leverage more automated tooling to help with managing and monitoring code quality. There is a lot of activity about these kind of tools in the Python ecosystem and with a bit of effort to set some things up I believe you can streamline the development cycle by catching issues earlier with less human involvement.
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 reviewing the repository's existing development and quality-check configuration, then survey the Python automated tooling relevant to the stated goals. The issue is complete only when a concrete tooling plan is agreed and the selected checks are integrated into the development workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100