Quoting Scott Hernandez <[EMAIL PROTECTED]>: > It would help if you (or really anyone) went through the last build > (http://nant.sf.net/builds) and played the role of a user. What looks out of > date, what looks like it is missing, what need to be done?
Considering that I have just found NAnt last week, and am working on installing it and setting it up at my company, I think I can answer this question for you: Documentation. Specifically I've had to spend a lot of time just playing with it and seeing what it does. As a result, I've learned a LOT I didn't know about how builds work deep down, but it was hardly a turn-key process. Don't get me wrong - I'm heavily into OSS and love doing this, but it was hard to even know where to really start, even after reading the documentation. Two points in particular that I had, or am having a hard time with: Slingshot and the process flow to use it, and Web projects. We have a fairly complicated set up here, with a half dozen or so core objects shared by different applications, and then separate solution files that are kept outside of the normal source tree, so that each SLN only references what it needs, so the normal HelloWorld samples dont apply very far. I haven't gotten into VSS integration yet, but thats probably going to be at the top of my mind soon too. 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. Its a thought. If you need a secure place to host a wiki, I might be able to hook something up, but SF should have the base stuff for you to run it on their servers... I recommend TWiki (http://www.twiki.org) as you can set up multiple sites (say one for nant, one for nantcontrib, and maybe you can talk nunit and ndoc into hosting docs there...) and grant access controls to people. In fact, I really like the idea of seeing at least the documentation for these three projects coming together, since they can be easily integrated. So much so that I've been calling the three tools the "NFramework" around the office here. :) Damn, I gotta starting writing more concise emails.... sorry. D ------------------------------------------------------- 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
