We're using NHibernate.Validator actively. I have a local copy modified to work with NHibernate 3.2. I've seen in few places people asking about same thing. If it will be moved to GitHub I'll be happy to contribute a patch/pull request.
And I completely agree that each active project ported from old NHContrib repo deserves a separate repository on GitHub. On Fri, Sep 2, 2011 at 5:39 PM, Patrick Earl <[email protected]> wrote: > I would think that the projects should be split off into individual > repositories. If some sort of consensus can be reached around > particular projects, I'd be happy to help convert those sections of > the nhcontrib tree to Git and put it under the nhibernate organization > for easy location. > > Since some of the nhcontrib projects are not well maintained, speak up > if you're interested in a particular project. We might be able to > ascertain that it should just be moved across without feedback > required from the inactive maintainer. > > Patrick Earl > > On Thu, Sep 1, 2011 at 6:14 PM, Stuart Carnie <[email protected]> > wrote: > > I'm voting for github - I have contributed minor fixes on my fork of that > > repo (though now redundant due to Enyim) but svn is not at all ideal for > > collaborative dev. If nhcontrib is to be community driven, github is the > > ideal place. > > Cheers, > > Stu >
