This always fascinating to see a person that maintains a ton of package, knowing full well that there is no way that they actively use all that software themselves. At the same time there are millions of us that just expects a package to be available, but never think to offer to at least help maintain a something. Frequently it's not even that hard, sure there are a few specialized packages which require more skills, but packaging up a Python library is something most of us could easily do.<p>Generally all of us needs to be better at pitching in where we can and not be depended on a few people overworking themselves.
I've been in this situation at a couple of companies. Very prolific in the first year, only to burn out.<p>At my new job, I'm taking it easy.
Alpine's community has always seemed kind of "slap this together" combined with "figure it out yourself". I remember trying to contribute and it being a pain. Advice to the maintainers: spend a month or two finding ways to make it easier for us to contribute, and we will.
The blessing and curse of having a prolific contributor (mostly the former). The trick is to manage burnout and figuring out continuity for these individuals to avoid massive upset in the open-source project if they decide to move on or take an extended break.
13K commits over the past year works out to almost 40 commits per day. Curious what the workflow is to accomplish that and the nature of the commits. Irrespective of that, that is super intense, sounds like she's getting a well-deserved rest.
I use alpine and on my desktop and I've seen that handle so much! Thanks for all your hard work, if you ever read this.<p>As an aside, I really should learn how to package stuff for alpine.