This thought crossed my mind when thinking about the recent riot concerning trunk:
What do we do with the codebase that still has licensing issues? Does that have to remain in the incubator svn? Does it move with us to our own wicket repo once we are TLP? For instance, wicket 2.0, current trunk, is not released in the incubator. When we get 1.3-incubator-* successfully through the IPMC what is then the next thing on our agenda? 1 - do the same trick for 2.0/trunk? -> all licensing issues would be resolved for that codebase 2 - graduate? -> we have proven to be able to build a legally solid release, and other things are also fullfilled: diverse, meritocratic community (added 2 or even 3 new committers during incubation), etc. Even if we do 1, we would still have the 1.2 codebase in our repo, with licensing issues (LGPL datepicker). Can we move that with us, or does that stay in the incubator? Martijn -- Learn Wicket at ApacheCon Europe: http://apachecon.com Join the wicket community at irc.freenode.net: ##wicket Wicket 1.2.5 will keep your server alive. Download Wicket now! http://wicketframework.org
