I agree with Dave, documentation needs to be addressed. I really like the Wiki idea. We used a Wiki for documentation on my last project with good success. Our customer resisted it at first our original idea was to get the users to help with the documentation by editing the pages. It was accepted as a documentation medium when we showed that we could have an admin user that allowed us to edit the documentation and not allow the users to alter it. We gave our user base a separate "forum" for adding notes, requests and communication amongst themselves.
<shameless_plug> I'd be willing to take a look at deploying a wiki to my NCode Sourceforge project to see if it works. NCode is a VS.Net IDE Add-In that does code completion from live templates (just like IntelliJ if anyone has used that). <url>ncode.sourceforge.net</url> </shameless_plug> -Aaron -----Original Message----- Message: 9 Date: Thu, 6 Feb 2003 07:44:23 -0500 From: Dave Sanders <[EMAIL PROTECTED]> ... Documentation. Specifically I've had to spend a lot of time just playing with it and seeing what it does. ... Have you considered hosting a Wiki for keeping and maintaining documentation? Even if you kept it hidden away for the developers list, and published out static files as the documentation - it would be a quick and easy way for all of us to contribute little snippets of information without any one person or group of people having to write full documentation. ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
