Before I start, let me break up the NAnt build tool into a few sections. -- Core (non-tasks like the targets, logging, processing, exception management, ect; the tool infrastructure) -- Core Tasks (Core, DotNet, Win32, Linux ....) -- Optional Tasks (and dependencies: binaries) -- Tools (things that make use of NAnt Core/Tasks)
Okay, here is what I remember of the reasons for the creation of the NAntContrib project. 1.) Once NAnt reaches a 1.0 release, it won't change much. The core framework (non-task stuff) will be fairly unchanging until the next major release. 2.) The NAnt core devs (non-task devs for the most part) are the only ones that really need to change the core. 3.) There will/may be lots of people donating tasks (need someplace to put them) that aren't applicable for the core 4.) Optional Tasks dev don't need/shouldn't have direct access to the core repository (this would lead to core changes that might not be good or might change things too often) 5.) Experimental tasks and tools needed someplace, pref. outside of the core repository 6.) There was a concern that some of the new tasks, or really just adding more code, would slow down the Core development time to get to a 1.0 release (7.) The ant teams had it broken down this way :) Partly I think NAntContrib was creates to brush off some people/tasks away from the core devs and code. This would be fine, and I supported it, except we really don't have enough people/support for managing 2 projects. It is all about growing pains. After we have a 1.0 NAnt Release I think the structure we have in place will make a lot more sense than it does now. Part of the problems is that the core stuff if still changing too much. But we have to remember that these changes are bringing us close and close to that 1.0 release. Mike, I don't think you are presumptuous. It is just kinda funny because from where I'm standing I see us going in a circle a little bit. I don't see how to break out until we get a stable 1.0 release out, and/or many more people actively developing (which would get us to a 1.0). Please, feel free to make comments about what I remember of the origins of the NAntContrib project. Also, I would say that a strong lead on NAntContrib would help immensely. I took on that challenge but got too distracted by the NAnt dev to really do a good job and focus. ----- Original Message ----- From: "Mike Roberts" <[EMAIL PROTECTED]> [snip] > [a] - I actually think that some of the (smaller) tasks from > Nant-Contrib maybe better off in the main Nant download. Perhaps the > NAnt committee would want to think about each task on a case-by-case basis. > > Of course, I'm a newbie round here, and there are probably very good > reasons for the separation of the projects and I'm just being > presumptuous to suggest such a plan of action. :) ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ NAntContrib-Developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nantcontrib-developer
