That was one hell of a necrobump. On Thu, Apr 14, 2011 at 3:14 AM, Demis Bellot <[email protected]>wrote:
> Hey all, > > Take this from one outsiders perspective, as I don't actually use > NHibernate anymore so this will likely be my one an only post to this group. > > I do however recognize the high-level of OSS talent in the room and from > another OSS .NET developer it's hard to watch the wasted energy going into > this decision. > > Correct me if I'm wrong, we have a situation similar to the following: > > Most OSS developers who have used GitHub, love it, are currently on it and > highly recommend its use. > Only the developers that haven't had a chance to use it yet, are reluctant > to move to it? > > On this assumption, I expect a survey on 'DCVS preference' as well as 'Have > you used GitHub before' would be very telling. > > Personally as a long time .NET OSS developer I've had close to zero > contributions in the 2 years my project was on Google Code. > The only contribution from people that cared enough to comment was to ask > me to please move to GitHub which is what ultimately prompted my move to it. > Not only that, but OSS developers love it so much that they were willing to > take the time to get me up to speed and show me how to use it. > > All I can say is that my only regret is not having moved sooner. GitHub > provides much more visibility into your project and allows you to easily > track who's watching or forking the project. > GitHub remains one of the most best UI/UX experiences for any site that > I've ever had the pleasure to use. > It's not just easier, its prohibitively easier for an external developer to > contribute to. I have no doubt that NHibernate (just like any other OSS > project) would be losing valuable contributions based on the effort required > to contribute otherwise. > > I don't think the fear of losing control is at all justified as you retain > full control of the contributions that make it into the official master > repo. > What it does allow you to do is take advantage of the built-in workflow > inherent in git to make collaboration and code-reviews more transparent and > easier. > > Here is a fairly recent survey conducted by Microsoft on the results of OSS > dev preferences: > > http://blogs.msdn.com/b/codeplex/archive/2010/11/27/survey-results-open-source-developer-preferences.aspx > > It is no mistake that despite its young age, Git/GitHub is the #1 choice > for OSS developers, this is no co-incidence, it's just that much better than > anything else I've ever used. > > Anyway, rather than seeing more wasted effort and energy going into what I > consider to be a single correct outcome (for any OSS project). > Please take the time to explore why Git/GitHub is preferred, here is a good > dive into Git from Rob Connery that is well worth the price. > http://tekpub.com/productions/git > > Wish you guys all the best and for the benefit of .NET OSS as a whole make > the right decision :) > > Signing off. > > Cheers, > Demis > > >
