Take, for example, the Wizard project. Now, this is something that I initially whipped up in two afternoons in September '05. It's a small library - it's attracted six contributors since then, who've all made valuable contributions. I tend to do work on it sporadically, for a couple days every 4-6 months. At most I've put 2 weeks work into it. With contributors, the pattern is that it's people who are using the library and want a feature that isn't there. They implement it, and get on with doing what they wanted to use the library for, which is as it should be. If somebody wanted to take on an ongoing role, that would be great, but I'm not holding my breath.
According to Ohloh, this weekend project represents (!)
I mean, think about it: Especially with small projects (IMO in a perfect world, most library projects should be small and tackle one thing well), a positive goal is for the project to reach a steady state where it does not need a great deal of, or ideally any, maintenance. If software rotted like fruit, there wouldn't be any progress in the software industry. There is such a thing as a library that can be finished!
What was that quote about lies, damned lies and statistics?