<div class="gmail_quote">On Thu, Dec 23, 2010 at 7:58 AM, Mike McQuaid <span dir="ltr"><<a href="mailto:mike@mikemcquaid.com">mike@mikemcquaid.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On 23 December 2010 12:43, David Cole <<a href="mailto:david.cole@kitware.com">david.cole@kitware.com</a>> wrote:<br>
> Neither do we:<br>
> <a href="http://public.kitware.com/Bug/view.php?id=10067" target="_blank">http://public.kitware.com/Bug/view.php?id=10067</a><br>
<br>
</div><div class="im">> As always, as developers we find ourselves constantly working to improve<br>
> what we have: fixing bugs, implementing new features, answering questions on<br>
> the mailing list, blogging/communicating about it, adding examples and<br>
> suggestions to the Wiki.<br>
><br>
> The struggle is reserving enough time to contribute to documentation when<br>
> there are always "real" (functional) bugs to be fixed. Perpetual questions:<br>
> what's "enough" documentation?, how do we make sure people can find it<br>
> easily?, how do we name this better (but still preserve the existing names<br>
> for people already using it / backwards compatibility)?<br>
<br>
> I make no excuses here: yes, the CPack and CTest documentation are lacking /<br>
> lagging behind the CMake documentation. However, it will take a very real<br>
> and concerted and time-consuming effort to improve the situation. With the<br>
> open source nature of the project, we have to be willing to accept the<br>
> organic growth that occurs in the code base: the documentation will be the<br>
> same: it will improve gradually, over time, as contributors are able to<br>
> improve it.<br>
<br>
</div>I think the main problem is that you make it very hard for people to<br>
contribute. KDE and Homebrew (two other open-source projects I've<br>
written a lot of code for over the years) make this very easy.<br>
<br></blockquote><div><br>How do we make it very hard? What about KDE and Homebrew make this very easy? Specifics, please.<br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Kitware is great, you clearly write good code and have done a great<br>
job creating CMake and CPack. They are fantastic tools. However, I<br>
think until you are more encouraging of external developers you will<br>
struggle to make huge improvements to CMake.<br></blockquote><div> <br>Thank you. Even with more external developers, I think we'll struggle -- that would just be a different sort of struggle.<br><br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">
<br>
> Until then, at least the mailing list has a reasonable response rate and, it<br>
> seems, sufficient participation from knowledgeable folks willing to pitch in<br>
> and answer. So... if you're confused about something, please ask here.<br>
</div><div class="im">> We (I hope I speak for all CMake devs, here) take no offense. We welcome<br>
> discussion, always.<br>
<br>
</div>The mailing list is OK but most people don't want to sign up to a<br>
mailing list and receive lots of emails that have nothing to do with<br>
them. I'm only signed up because I want to try and get some patches<br>
merged and was told that I should discuss things here rather than the<br>
bugtracker.<br>
<br>
I hope I don't cause any offense here either. I'm passionate about<br>
CMake because I like the tool and want to make it better.<br>
<div><div></div><div class="h5"><br></div></div></blockquote><div><br>Again, let me stress, no offense taken. There is no way you can offend me, unless you start calling me names for no reason. Reasonable discussion always welcome.<br>
<br>Thx,<br>David<br><br> <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div><div class="h5">
--<br>
Mike McQuaid<br>
<a href="http://mikemcquaid.com" target="_blank">http://mikemcquaid.com</a><br>
</div></div></blockquote></div><br>