On 28/07/06, cowwoc <[EMAIL PROTECTED]> wrote:
>         I have similar questions. I generally perceive Apache as the place
> open-source projects go to die :)

What, like the Http Server, Ant, Maven, Tapestry & Tomcat? Ex-parrots,
all of them! :-)

>         Apache might be the right way to go, but I'd definitely like to hear
> more about the impacts it'll have on the future of the project. What new
> rules and regulations will Apache enforce on the Wicket release
> schedule, license, etc?

 In practice, I don't think it'll be any different from the way we've
traditionally worked, other than the edge-cases where we'll need to
ensure there's only ASF-licenced code in the project.  Wicket-stuff
will continue on SF and will probably serve as the home for any
non-ASF code.


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
Wicket-user mailing list

Reply via email to