Hi there. You opened an issue with my project on GitHub, and it’s getting kind of stale by now. I am aware of it — was kind enough to send me an email containing your report, which I scanned one morning a couple of weeks ago while I ate breakfast. I’ve even thought about it briefly a couple of times since then; once I was in the shower and I got the vague idea that I knew what caused it — but I wasn’t sure because I could not recall the specifics. GitHub Of course, you knew none of this. You may have wondered if your issue — which may be critical to your current project — has been lost to the void. Allow me a few minutes to explain why you’ve not heard anything from me. A couple of years ago, I was a freelancer and father to a new baby. The freelance hours provided me with flexibility and the baby was conveniently immobile and fairly docile. I started writing libraries and publishing them on GitHub. Seeing people use my code was and is exciting and rewarding. Collecting stars on GitHub is a guilty pleasure just as with any other kind of “fake internet points”. I had plenty of time to work on issues and improvements, and I would generally respond to (and often fix) issues within a day or two. Today, I am in full-time employment. The baby is now a toddler, and there is also another baby. Toddlers are neither docile nor immobile. If I am lucky, I can carve out an hour of free time per day — generally between 9pm and 10pm. Do you know what I like to do in that time? Unfortunately for you, the answer is not . And I don’t mean to berate; I am simply stating fact. My weary evening mind is just not up to the task most days. Usually I like to sit on the couch for a bit, and just enjoy sitting. “fire up my IDE, get the build pipeline going, start a local dev server, and try to recreate someone else’s issue” So where does that leave you, user of my library? Do I no longer care about your plight? Have you done your company a disservice by using my library in your project? In this (FOSS) reality we live in, how many parts of your company’s product are coupled to the and priorities of some lone, unpaid package maintainer? It’s something I have to think about too — in my day-job I build software on top of many FOSS libraries, many of which are probably maintained by people in similar circumstances to my own. Free and Open Source Software lifestyle As with all things in life, a trade-off is involved. There is an implicit agreement which needs to be understood by both consumers and creators of FOSS projects¹. It goes something like this: I agree to provide you with some free code which solves your problem. I recognize that in doing so, I have taken on a small portion of responsibility to you as a user of my code. I agree to try to help you if you have difficulty in using my code. I agree to try to fix bugs that you find in my code. Crucially, you agree that I, in acting without remuneration, am free to assign priority to the above points as I see fit. The last point is the reason why I haven’t fixed your issue yet. Your issue is competing for my attention with my work, my family, my couch, my other interests and of course with all the other issues that are still open — several of which are much older than yours. So, here is my message to you, to all the users of my FOSS projects, and to all developers who use and benefit from the FOSS ecosystem: I will try my best to get around to it. I do want to help you. Make things easier for me by reading and following as closely as possible the . issue template Take time to understand, research and debug your issue — don’t offload that burden onto me. Understand if I do not reply in what seems like a reasonable time. And don’t be that one guy who was extremely rude and insulting (I’ll refrain from linking the issue for his sake). Thanks for reading, and happy coding. ¹ This goes for projects which are promoted in some way. If you tell people “hey, you should use my thing”, then you’ve entered into this agreement with them. If you just throw your stuff up onto GitHub for the fun of it, then it doesn’t necessarily apply. Originally published at www.michaelbromley.co.uk .
