One thing that would help, from my perspective, is a solid piece of documentation on how to integrate an already-existing framework into Paste. (If this documentation already exists, I apologize that I've missed it...) Seems like the application developers are pretty well-covered in documentation, but the framework developers don't have much to work on other than the Paste code itself.
That's true -- documenting configuration, and how it relates to frameworks and other pluggable pieces, is another important task. But asking questions on the mailing list is also a good way to resolve some of these things; in some cases I don't actually have an opinion on how parts should work.
I think the frantic pace of changes scared off a lot of the people who were using Paste. It certainly scared me off; Subway no longer runs on Paste. I just couldn't keep up with it when CP started having rapid changes, too.
That's disappointing to hear. The changes were largely meant to solidify the interface that other people would be using, and to give other people the flexibility to fit their systems into Paste. I did those quickly because I was working hard to get Paste into a place where those interfaces were available and stable. Core aspects of Paste have also been very stable; the Webware API, which I keep in working order, and which is more intimately tied to Paste than most frameworks normally would be, has required very few updates, even as I work on other parts of the system.
I've moved into the category of a lurker because my current projects work just fine on older code, and because when I do take the time to update myself on a particular technology or framework I prefer it to be solidified so that my new-found knowledge support me for the next six months or so. I think when Paste reaches a plateau in terms of implementation more of the sideliners will move in to hammer on smaller pieces.