macaroni-os / macaroni-os/mark-issues
RFC: Let's create `containers-kit`, for containerization tools, with new categories
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 5
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Currently we have packages like `app-emulation/incus` in `core-server-kit`, and in old categories that imo don't make sense anymore. Incus doesn't do emulation! (though maybe it could, I'm not sure) It is primarily a container tool that can also manage VMs, and neither of those things is emulation!
So! I propose that we create `containers-kit` and move some packages into it, from `app-emulation` to `app-containers`:
- `app-emulation/lxd` -> `app-containers/lxd`
- `app-emulation/incus` -> `app-containers/incus`
- `app-emulation/docker` -> `app-containers/docker`
- `docker-cli`
- `lxc`
- `runc`
- ...
etc.
I've created an autogen for `apptainer` and `apptainer-bin` that I put into `app-containers` in my local kit. Would like to make a nice home for it upstream!
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 listed app-emulation and app-containers package categories, including the existing autogen entries for apptainer and apptainer-bin. Clarify the proposed containers-kit scope and package moves with the project before making changes; done means the category structure and migration list are agreed and implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100