Thanks for the great direction. I'll let you know once I have a home for the code.
Just to sum up, the best way to contribute new code to the Wicket project is: 1- Find a place to share the new code (ie wicket-stuff or a git-hub) 2- Listen to feedback from the community, improving the code 3- If there is a large enough need (and enough interested folks in maintaining that specific code) then it may get accepted into the Wicket code itself. -Clint On Wed, May 11, 2011 at 6:37 PM, Jeremy Thomerson <jer...@wickettraining.com > wrote: > Clint, > > We (Wicket devs and community) are always happy to see new developers and > development teams (especially) show interest in contributing back to the > Wicket community. On behalf of both, welcome! > > As all developers understand, maintaining code is much more costly than > initially developing it. Especially is this true with framework code like > Wicket. It must be very robust and fit so many individual needs of > different users. Maintaining code written by others is doubly hard. For > that reason, for any wicket-* integration projects as well as other large > Wicket plugins / add-ons, we like to see the code incubate on its own > before > considering the merit of it entering the Wicket codebase. Once it enters > the Wicket codebase, we then have to maintain it ad infinitum. If your > project gains widespread adoption within the community, and there is a > developer base that is willing to support it, we may later pull it into the > core codebase. > > Although Wicket Stuff is a viable option for contributing this code, if > you would like more control over the project, you may also want to consider > creating a GitHub account for your team or company. You could create the > project there, and easily add contributors, manage contributions, etc. > Google Code or Sourceforge.net are other options. > > As one last point, there is a little bit of paperwork required to take any > large contribution of code into any Apache Software Foundation codebase. > See the two subheadings here: > http://www.apache.org/licenses/#clas("Contributor License Agreements" > and "Software Grants"). > > -- > Jeremy Thomerson > http://wickettraining.com > *Need a CMS for Wicket? Use Brix! http://brixcms.org* > > On Wed, May 11, 2011 at 1:35 PM, Martin Grigorov <mgrigo...@apache.org > >wrote: > > > Hi, > > > > I think it will be better to put it in wicketstuff/core for the > beginning. > > We are kinda conservative to accept more code to support officially. > > We don't have much resources anyway. > > And I don't remember someone else to ask for such flow so maybe it is > > not that common needed functionality. > > But if the project gain more popularity, who knows - one day it may > > become part of the Apache Wicket project. > > > > On Wed, May 11, 2011 at 6:26 PM, Checketts, Clint > > <clint.checke...@usaa.com> wrote: > > > Wicket Devs, > > > > > > As part of a rollout of Wicket, we had a requirement to externalize the > > page flow from the Java code. As the result of that effort we created an > > integration layer for Wicket to work with Spring Web Flow ( > > http://www.springsource.org/webflow ) Now I'd like to open source that > > layer and contribute it back to the Wicket project. > > > > > > What are your thoughts? After you all have viewed the code and agree > with > > the overall design (and unit tests), I could see the code being a new > > separate module like the wicket-spring one is, ie wicket-spring-web-flow. > > > > > > Thanks, > > > > > > -Clint Checketts > > > > > > > > > > > > > > -- > > Martin Grigorov > > jWeekend > > Training, Consulting, Development > > http://jWeekend.com > > >
