Stuart, I forked your NH Test repo to the NH Organisation, and have granted you access to it. I renamed it nhibernate-core-testcase - unless somebody can suggest better.
I don't think this conflicts with Patrick's improvements. I see two types of user: - those who simply want to report a bug they have encountered using NHibernate. We typically ask them for a reproduction of the issue, but they have no intention of debugging NH to provide a fix. Now they can fork the 'nhibernate-core-testcase' repository and give us a pull request to provide the repro. Diego's idea of creating a NuGet package is another good idea that would make it even easier for them to do this. - other users who have the time/inclination/motivation to improve NH by debugging the code to find the problem and provide a fix will need the source code, and therefore fork the 'nhibernate-core' repo. They will be able to take advantage of Patrick's improvements. On 3 September 2011 08:57, Patrick Earl <[email protected]> wrote: > I'm also working on a path to allow people to contribute as quickly as > possible. I've already got scripts for setting up test profiles and > such. I'm aiming to get it so that people can pull the NH core and > have a clear path to having a test up and running within a few > minutes. Since they'd have the core checked out, they could easily > start debugging the NH source to find the nature of the issue. I'd be > happy to have more involvement from folks, so I'm trying to remove the > boring barriers to getting started. > > Patrick Earl > > On Fri, Sep 2, 2011 at 5:08 PM, Julian Maughan <[email protected]> > wrote: > > The NH organisation could have another repo called nhibernate-test-case - > > the naming to avoid confusion with the actual test project. It's > definitely > > a nice idea. > > > > On 03/09/2011 4:02 AM, "Stephen Bohlen" <[email protected]> wrote: > >> Actually, that's a really good point. Let's leave it where it is then. > >> > >> -Steve B. > >> On Sep 2, 2011 4:00 PM, "Stuart Carnie" <[email protected]> > wrote: > >>> I don't see why not. It may be less of a barrier not to have to check > out > >>> the entire NHibernate repo just to build a unit test. > >>> > >>> Cheers > > >
