Perhaps we should write up some goals for Wicket Stuff.
In my opinion Wicket Stuff is used as a Wicket specific incubator for projects that will end up in core. At least for projects that have 'use' as intent. Projects within Wicket have different intentions: - actual use (i.e. wicket, extensions, spring, velocity) - example (i.e. examples, auth-roles?, contrib-data/hibernate?) - proof of concept (i.e. fvalidate, wicket-flickr) - testing (thread test, performance test) I would like to be able to distinguish between these projects better, but I am not sure how to implement that. Wicket Stuff must be able to host all these different types of projects. But it should also be easy to find what the intent is of a project without putting too much burden on the users. Maybe a repo layout as follows would help? trunk/projects trunk/examples trunk/testing trunk/concepts branches/wicket-1.2/projects branches/wicket-1.2/examples branches/wicket-1.2/testing branches/wicket-1.2/concepts Where the projects directory contains the 'use' usecase, etc. Efforts under trunk/projects could be required to perform releases for at least newer wicket versions within a couple of months, and be moved to concepts if they fail to do so. This is not to discount the effort put in by the original author, but to give people an easy path to the actively maintained projects. 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. It is just hard to find people with a sustained interest in maintaining a project and actively working on its progress. Databinder has a great maintainer, as does Dojo, and scriptaculous. I also think gmap is maintained but it could benefit from a release IMO. Martijn -- Learn Wicket at ApacheCon Europe: http://apachecon.com Join the wicket community at irc.freenode.net: ##wicket Wicket 1.2.6 contains a very important fix. Download Wicket now! http://wicketframework.org
