Thoughts
The head maintainer of the Catppuccin org is Hammy. His area of expertise is CI. Historically, I haven’t been the biggest fan of CI, it
alway seems less exciting than “actually working on the project.” But it’s really impressive to see how Hammy is able to use it as a tool to compensate for areas he’s not familiar with and magnify the scope of what he’s able to do. By investing time to make sure that repos have CI to handles dependency updates, check builds, and publish new versions, Hammy can handle a lot of the boring and administrative parts of maintenance. There’s a Catppuccin AUR repo that uses CI to check for updates in the underlying packages and automatically publish new versions to the AUR. Hammy doesn’t run Arch; he got other maintainers or volunteers to do the actual packaging once, then he wrote the CI configuration to do it repeatedly, automatically. If someone else built the project once, you can use CI to maintain it, keep it up-to-date, flag breakages, review and merge PRs, and publish new releases *without even cloning it locally*. Definitely very cool.