Hi all,
One of the challenges of open source software, especially that managed by a hobbyist individual, is the lack of exit ramps. For ten years, while I've had ups and downs in terms of availability, energy, and passion for managing mountebank, all of it has been on nights, weekends, and vacations. Simply put, that is no longer an option for me.
I've mostly tried to ignore the problem, hoping one day I'd miraculously find the time and passion to re-enervate the product, but in my experience, as I've gotten older, I've also grown busier with my paid work and a more complicated family life, more varied in my interests, and more reliant on a predictable sleep schedule. My current approach will lead to mountebank dying on the vine.
That is, of course, an option, one that happens quite often in the open source world. It would solve my bandwidth constraints, but would obviously be disappointing for a product I've helped grow for ten years, and even more disappointing for many of you who depend on mountebank for your paid work and would have to pay the switching costs (or manage your own fork).
A better option, if possible, is to donate mountebank. My past experience makes me skeptical that donating to another hobbyist maintainer eager to give their free time up for unpaid work supporting something they didn't create is sustainable. I'm not looking for any money (and have never accepted any for the work I've done), but I believe a more credible option would involve a company willing to take ownership of the codebase. who could justify funding the required support.
In any case, I'm open to suggestions. I've learned a lot from both the successes and challenges of managing an open source product, have greatly appreciated the community who have used and offered support, and would love to find a viable path that enables the community to get the support they deserve.
-Brandon