|
From: Nat P. <nat...@gm...> - 2006-05-25 06:15:45
|
Hi Charlie (and nmock-2 dev). I have no problem with this. However, Joe has started to factor out the constraints/matchers from various projects (jMock, nMock, etc) into a new project that is intended, one day, to be shared between them and other uses. Joe: could Charlie join or use that? As for licensing, NMock2 is under a BSD style of license. Personally, I prefer copyleft licenses because they are more business friendly and protect end users, but I'm not sure how copyleft and BSD can be combined. --Nat. On 5/25/06, Charlie Poole <ch...@po...> wrote: > Hi Nat, > > I'd like to have an Assert.That syntax for both NUnit and NUnitLite. If w= e > can use your project's code, I'd as soon do that. Otherwise, we'll just b= e > inspired by you. :-) > > For NUnitLite - which would use it first - we would need to add the relev= ant > source files to our project. For NUnit, depending on when you go to a ful= l > release, we could either do it the same way or follow up with the > long-standing plan to replace our mock framework with NMock. > > How do you guys feel this would work in terms of licensing? I read the > thread where you were discussing a license and I never saw anyone actuall= y > answer the question of what you wanted to achieve with the license you > chose. BTW, NUnitLite will be copyleft - there's even a good chance it wi= ll > be GPL or LGPL. NUnit will stay what it is, at least until we do a fresh > start with 3.0. > > Feel free to take this to your discussion list if you like. > > Charlie > > > |