What would constitute good Wicket improvement projects for Google's Summer of Code 2007? Here's a list I just came up with:

  • add support for new markup languages: WML, XUL, ...?
  • create visual editor for Eclipse, Netbeans or IntelliJ?
  • create comprehensive scalability/performance tests between Wicket, JSF and Tapestry
  • expand/improve on Wicket Kronos, a Wicket based CMS
  • write a reference manual or a doclet for generating one from our JavaDoc
  • write a conference planner for ApacheCon in Wicket
  • ...

I think this is just a short list, and I guess there are much better ideas than what I came up with. Share your ideas!