My daughter will be born soon, and I’m reflecting on what that means for my open-source work.

After a lot of thinking, I realized I’m doing too much. Basically, I’m already stretched thin with all the self-imposed obligations I have, and I’m getting through them only because of discipline.

With a baby, I expect things to become more chaotic, and discipline might not be enough.

On top of that, a lot of the projects that I created are no longer things I’m interested in, but they’re still there, generating notifications and toil, and it feels bad to ignore them.

Project diet

My plan is to add co-maintainers to the repositories I’m no longer interested in but think might still be useful (if anyone wants to do it, of course), and archive the ones I think have outlived their purpose.

So, here’s a list of repositories for which I’m looking for co-maintainers:

If no one comes forward, these will be archived soon. If you are interested, open an issue in the repository you wish to co-maintain, and after some due diligence, I might or might not add you as a co-maintainer.

There’s a couple of other projects that I’ll keep maintaining, but would love some help regardless:

I already archived a couple dozen of the repositories that I don’t think anyone will be interested in. If I’m wrong and someone is in fact interested, and that someone is you, let me know and I can unarchive it.

There’s also my repository graveyard - I created this back in the day when GitHub didn’t have the concept of archiving a repository, but I still move some playground stuff in there sometimes.

Some repositories there were not really archived yet, so I scripted it and now they are:

for repo in $(gh repo list --no-archived --limit 200 caarlos0-graveyard | awk '{print $1}'); do
 gh repo archive --yes "$repo"
done

This should allow me to focus on the remaining projects, some of which are widely used, some of which I use personally for some reason, plus, of course, GoReleaser, which has been my main focus outside work for a while now.

All this leaves me still with a whopping ~70 public repositories to maintain (between @caarlos0 and @goreleaser), some of which are auto-generated, or forks with specific changes I need in another repository. My estimate is that a couple dozen of these require active work except the occasional @dependabot merge.

Life diet

Currently, I do a bunch of outside work stuff, and I plan to find things to trim down in there as well, either by completely stopping them or by giving them much less time.

More on that once I actually decide what stays and what goes.

GoReleaser, in particular

For GoReleaser, I might eventually look for someone to help (paid, part-time), so I can focus on other stuff.

More on that in the future.

Being a dad

It can happen at any moment now.

If I disappear for a couple of days, you know what happened. 😁