I know this isn't the first time this has been discussed/blogged about: I'm proposing that we create a Wicket application that contains a summary, link and user feedback (reviews and ratings) to all the various Wicket Components/libs available, along with the version(s) of Wicket that those libraries support. The library maintainers would be responsible for updating the supported versions - the app would also serve as a release announcement for the libs. User feedback could also ask what versions of Wicket they were using the specific lib with so we could gather community feedback.
Users would have to login / validate email in order to access the information so that we can track voting responses and reviews reasonable accurately. Bringing all these together in a single place, accessible from the main web site, would present a more cohesive picture of all the components available and the extent of the Wicket libraries and community. The application would also serve as a useful reference app. What are the gating factors here (beyond dev time to build this out) - DB? App Server? Modifications to wicket.apache.org? Thoughts & comments? N
