On Fri, 12 Nov 2004 00:34:59 +0100, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > Christopher Turner wrote:
> I find that wiki's tend to distract from the realy manual. I would vote > against a wiki if a vote comes up. I really hate it when I've got to > look in 7 or 8 different places to find information. Just to pickup on this particular point, as I disagree. I think that a Wiki's got a valuable role to play as something between posts on a mailing list and the 'real' manual. The two areas I envisage for it at the moment are (1) somewhere to collect information that might need discussing before it becomes published (such as you just posted?), e.g. Tips/Guidelines/BestPractices and (2) for documentation/discussion of contributions that aren't part of the core product. I'm thinking about www.intellij.org as the model here. > Wiki's also tend to have outdated information. Actually, that's the one charge against wiki's that should be least likely, as the nature of the beast means that the info can be either removed or updated much more easily than it could once it's in a manual! /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
