Inconsistent plugin structure
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 454
- Forks
- 134
- PR merge metrics
- No merged PRs in 30d
Description
The three different methods for managing Docker Scout (Docker Desktop vs. automated Docker Scout install shell script vs. manual Docker Scout extraction), use different directory structures. The first two methods use $HOME/.docker/cli-plugins, but the last method uses $HOME/.docker/scout.
In the interest of consistency, intuitiveness, and maintainability please unify these into a common directory structure.
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
Compare the Docker Desktop installation, automated Docker Scout install shell script, and manual Docker Scout extraction paths described in the issue. Determine a single directory structure for all three methods, then verify that each installation path places Docker Scout consistently and remains usable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- cli
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100