I am now very unhappy with my role as maintainer. Over my repeated expressions of concern, the minimakefile -- which aims to replace normal shell tools with CL-based scripting facilities -- has been merged with core ASDF. Since then, almost all of my ASDF-related time has gone into wrestling with said scripting facilities. I don't mind if people think it's cool to try to make a CL scripting facility. But it's not my thing. I just want my tools to work. The CL scripting facility is, IMO, at an "alpha" level in which it works acceptably in the developer's environment, but can be expected to hiccup seriously anywhere else. I don't want to fight it any more. So I'm offering the community two choices: 1. I "un-merge" the minimakefile facilities and go back to vanilla CL and the standard Unix toolkit for maintenance. 2. Someone emerges to take over the maintenance of ASDF in its current shape, and I go back to being a simple contributor. I barely have enough time to keep up my responsibilities as maintainer; I simply don't have the time to maintain cl-launch, cl-scripting, yadda yadda yadda, as well as ASDF. Even if I did, I wouldn't want to, because this is not a direction that interests me personally. I don't say it's a wrong direction, just that it's not my thing. Fare likes this structure, and he is still the master of ASDF. Me handing off ASDF is more survivable than driving Fare away. So I believe that finding a maintainer who is intrigued by the new direction, and enjoys moving it forward, is a better choice than going back and ripping out the new framework (in retrospect, we should have *added* the new scripting facilities, rather than *replacing* the old). So consider this a call for my replacement. It's been an interesting ride, and I have learned a lot in the process, but it's probably time for someone else, who's more motivated by the new infrastructure. Best, R