2009-09-01 05:54:08 UTC
See my note dated 3/13/2008 for some info on the approach we're taking with NUnit.
Currently we have an NUnit Extended Testing Platform project group on Launchpad (see
http://launchpad.net/nunit-xtp. It has several member projects including the NUnit 2.5 project and the framework portion for NUnit 3.0. I can see NUnitForms as another one of those projects, with it's own team lead and developers. The current copyright and license of NUnitForms would not change.
I'm pretty happy using Launchpad and Bazaar though so I suggest looking at it. It has a number of cool features, including the ability to file a bug that affects several projects - which could apply if NUnit caused a problem in NUnitForms for example.
However, if the guys working on NUnitForms prefer to stay on Sourceforge, we can create a mirror project of the project, which would be used to build release copies for bundling with NUnit.
We are already doing this with PNUnit, which is maintained by the company that develops it. I can't say it works perfectly, but it's getting better. Obviously, coordination is required.
To go ahead, I think we need a few of the current commiters to step up for continuing to work on it and one of them should probably take the lead / release manager role. Let's hear from some of those guys on this thread. :-)
I haven't heard any response from the mailing list but I also haven't seen my own message echoed back to me so maybe I'll send it again.
Charlie
