Firstly, my apologies for taking so long to reply - I've only just worked out why I wasn't getting any wicket emails.
Ryan Sonnek wrote: > My only concern is how apache frowns on it's projects' working with > non-Apache licensed libraries. It is worth understanding why Apache 'frowns' on non-ASL compatible libraries. Apache is strict about what can and can't be included within Apache projects so that users can easily understand the licensing consequences of using its code. It is worth noting that there are many companies that have a policy of accepting Apache code without license review, purely because of this policy. > What does this mean for the wicket-stuff or wicket-extensions projects? > Will the hibernate or spring extensions become "taboo"? They stay at SourceForge and remain available. There's nothing wrong with interfacing non ASL-compatible code with Wicket - it is just important that users are aware of the licensing consequences of doing so. > Don't get me wrong, I think wicket would gain a lot by becoming by > joining apache. Well, I hope both Wicket and Apache will gain from it :-) Regards, Upayavira ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-develop mailing list Wicket-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-develop
