However, that does impose some form of oversight, and given the current state of Wicket Stuff, I doubt that it will ever happen, if it doesn't come from us.
Exactly.
It is just hard to find people with a sustained interest in maintaining a project and actively working on its progress.
We have a couple of people now who want to maintain the projects. I think what our problem has been is that we have been breaking the API a lot, but haven't immediately been updating those projects for the breaks, leaving the projects most of the time in a broken state. I bet that hasn't been too encouraging. Besides that however, there really seems to be a problem with getting people all fired up and exited about those projects, as there could have been a ton more projects by now, and certainly more releases and documentation etc. I don't know what it is. I'm afraid that's just how most of such initiatives end up in OSS. Eelco
