Replace bin/ build tooling
Open
Nobody has claimed this yet.
area/build
rfc
- Dominant language
- Go
- Stars
- 11.5k
- Forks
- 1.4k
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 53
Description
When I wrote the `bin/docker-*` tooling, I was mostly doing so out of frustration and expediency. But, ultimately, there are better tools out there for this sort of thing that will be easier for folks to work with---especially new comers to the project.
My hunch is that we should use `make` (though, hopefully not one massive Makefile).
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 by reading the existing bin/docker-* tooling to understand what commands and workflows it covers. No tests, entry points, or acceptance criteria are named; the work is done only once an agreed replacement build-tool structure is defined and the existing tooling is replaced without losing those workflows.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- build-system, tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100