Hi Andrea, You are already a member of WicketStuff 'collaborators' team so you can directly push your code. But you can also ask for code review by creating a pull request. This way everyone else who is interested in better quality of WicketStuff projects can give his/her opinion. At the end you can still press the merge button yourself.
The only recommendation I have at the moment (without code review) is to use wicketstuff- as prefix for the artifact ids, to keep it consistent with the rest (maintained) modules. On Fri, Jul 26, 2013 at 4:40 PM, Andrea Del Bene <an.delb...@gmail.com>wrote: > hi, > > I've almost finished to implement and test a Wicket-based project to > implements REST API/applications with Wicket. I'd like to publish the > code as part of WicketStuff when also the documentation will be > finished. Is there any policy or process to follow to accept a module > into WicketStuff (a review of the project, a developer vote, etc...)? > The code of the project is in my personal repository at > https://github.com/bitstorm/Wicket-rest-annotations/. > > PS: as I said the documentation is not yet ready. > >
