http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660I agree that active committers is a sign of health for an open source project and that NDoc wasn't healthy. From my understanding of the fiasco, a contributing factor to its demise was the lack of an updated public source repository. It is my understanding that much work had gone into supporting generics that wasn't checked in and when the lead developer quit in disgust (which I can understand given the circumstances), those revisions went with him. Hence anyone picking up the project had to learn the source code, re-implement a bunch of stuff, AND potentially deal with some pretty nasty emails/threats now directed at them. I honestly considered picking up the project when it was abandoned, but decided it wasn't worth the potential grief. Besides Sandcastle (even with all its flaws) was going to win in the end because it was free and from Microsoft. Tools like Rhino Mocks are different. The public source repository is up to date. The test suite is awesome, which means I can (and did) make changes without fear of horribly breaking something. I also use the tool every day. So active committers is only one sign of health for an open source project. A bigger one, IMHO, is how much pain do your users experience when you get hit by the bus. Is it enough for one (or more) of them to step in and take over the project? http://ayende.com/2400/on-the-health-of-open-source-projects#comment1http://ayende.com/2400/on-the-health-of-open-source-projects#comment1Thu, 17 May 2007 18:38:28 GMT