<div class="gmail_quote">On Sat, Aug 1, 2009 at 11:30 PM, Steve Steiner (listsin) <span dir="ltr"><<a href="mailto:listsin@integrateddevcorp.com">listsin@integrateddevcorp.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style=""><div><div class="im"><blockquote type="cite"><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Where would we put an "inventory" project for it to be most useful?<br>
<div><div></div><div></div></div></blockquote><div><br> As JP mentioned earlier in this thread, some work has already taken place here: <<a href="http://twistedmatrix.com/trac/wiki/DocumentationAnalysis" target="_blank">http://twistedmatrix.com/trac/wiki/DocumentationAnalysis</a>>.<br>
</div></div></blockquote><div><br></div></div></div><div>It doesn't really look like that effort went anywhere.</div><div></div></div></blockquote><div><br>I don't think it's quite fair to say it didn't go <i>anywhere</i>, it just didn't get anywhere particularly complete. I think the reviews that have been done thus far are still a valuable resource for someone interested in working on the documentation.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div style=""><div>Maybe we should have an auction?<br></div></div></blockquote><div>
<br>(snipped lengthy description of labor-intensive bounty resolution process)<br><br>What we really need is for people in the community to knuckle down and do the work of actually reviewing the documents, rewriting things, soliciting feedback, copy-editing the documents, checking for accuracy, etc. As Jessica did when she started the thread :).<br>
<br>Frankly, the work is boring: what the documentation needs is not a dynamic market-driven system for managing contributions and paying bounties, it's not a comprehensive overhaul of our entire documentation toolchain. What it needs is for people to sit down and read all the documentation, make a list of all of its problems, one at a time, and then write, delete, and edit as necessary, incorporating feedback from the community.<br>
<br>Once we have people taking part in that effort and working with the docs on a daily or weekly basis, <i>then</i> we can listen to the reality of the problems and frustrations that they have working with the tools or determining priorities or whatever and solve those problems.<br>
<br>Separately from that, if you're interested in contributing some time to manage a bounty program for the TSF, that might be a reasonable idea. Other projects have experimented with bounty-based systems for
resolving bugs. Unfortunately there are a number of difficulties with
those systems, which are really out of the scope of this discussion, but they're worth talking about if you have a real interest in doing it.<br>
<br></div></div>