The mini-services part refers to the fact that each high-level feature - git & hg repos, CI, bug trackers, etc - is implemented as its own standalone web application. The composable part is that you can freely use them in concert with each other to whatever extent is appropriate for your project. Consider that on GitHub, GitLab, etc, one project == one git repo == one bug tracker == one path for merge requests == one wiki == etc. SourceHut's upstream codebase, on the contrary, has several git repos, one mailing list, several CI configs, N bugtrackers where N != nrepos, and so on.
>I'm not sure what "Composable Unix-style mini-services" means.
Each service can be hosted independent from one another I'd imagine. Contrary to GitLab where each service, Git hosting, CI, ticketing, is all bundled into a single monolithic application.
It’s similar to GitLab. The composable mini-services refers to how the individual parts (git, mercurial, todo tracking, continuous integration, email lists, doc hosting, etc.) are able to be run independently.
It's basically software development project hosting (like gitlab), but for people who prefer mailing lists to web apps.
Yes it fits into roughly the same space as GitLab:
"This suite of open source tools is the software development platform you've been waiting for."
- Hosted git repositories
- Powerful continuous integration
- Mailing lists & code review tools
- Customizable ticket tracking
- Task dispatching & service integration
- Markdown- and git-driven wikis
- Sophisticated account management & security
I'm not sure what "Composable Unix-style mini-services" means.