Consider splitting out a package for submitters
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 26
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
The current kcidb package contains everything that's running in the cloud, administrative tools, and the code using for submitting data. Consider splitting out a separate package that could be used for submitting data only, and perhaps for querying. This won't get rid of our most-cumbersome dependency - the forked jq.py package, but might still be beneficial.
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 mapping the current kcidb package into cloud, administrative, submission, and query responsibilities; the issue names no specific files or tests. Determine which submission and query functionality can form a separate package without removing the forked jq.py dependency. Done means the proposed separation is implemented and the relevant submission and query use cases continue to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- databases
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100