On Wed, 10 Nov 2004 15:03:52 +0100, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > I'd go for a seperate project. When the core stabilizes, changes to it > should be minimal. On the other hand, the contrib package should be for > very active development by hopefully more developpers than the current > 'core' devs.
Hmm, SourceForge doesn't have the capability to have different commit rights on different parts of the CVS tree within a project, does it? If not, then I guess a separate project is the only way to go, as I'm assuming that such a project will need a more open CVS policy than in the core. The downside is that it's going to be less obvious when a core change breaks something there unless there's going to be a continous integration system running somewhere, but that shouldn't be a major issue if the builds are against particular versions of the core, rather than SNAPSHOT. > That said, I also do not think that the core should be stripped from any > high level component though. But I think that specific components like > login panel should not be in there. Hmm, I don't really know either way - I'd just be concerned of effort now being spent on things that weren't moving the project towards a V1.0 release state (with examples & documentation)! /Gwyn ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ Wicket-develop mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/wicket-develop
