Well, from my POV, -core would be for things that are licenced under the Apache licence, likely to be used in a majority of projects & are intended to be supported by the core team, -extensions is for things that are licenced under the Apache licence, likely to be used in a significant number of projects & are intended to be supported by the core team, while -stuff does not require Apache licencing and is not specifically supported by the core team.
(As an aside, we don't seem to have anything obvious on the main site mentioning the various modules, extentions or stuff - Must try & remember to see if I'm overlooking something...) One issue with using -stuff for this would be that at the moment, the licencing is such that it can be easily put into -extensions, whereas to put it into -stuff then later 'promote' it to -extensions would require a certain amount of re-doing of the work. On the other hand, if it goes into -extensions, it seems to me that /if/ it were to be too much of a drain on resources (which would seem to be the only reason to do so), it whould be relatively easy to move it 'out' to -stuff at a later date. /Gwyn On Tue, Jun 3, 2008 at 9:16 AM, Nino Saturnino Martinez Vazquez Wael <[EMAIL PROTECTED]> wrote: > +1 for extensions > +2 for wicketstuff > > I'd still like a clear definition on when what goes where.. Thats when is > wicketstuff appropriate and when are extensions and when are wicket core > appropriate. > > Martijn Dashorst wrote: >> >> The IP clearance for the kittens got approved through lazy consensus. >> Now we can integrate the kittens into our project. I believe the >> target was extensions? >> >> Martijn >> >> > > -- > -Wicket for love > > Nino Martinez Wael > Java Specialist @ Jayway DK > http://www.jayway.dk > +45 2936 7684 > >
