<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>8 sep 2011 kl. 23:58 skrev Henning Westerholt:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="font-family: monospace; ">Only bug fixes in code, documentation or utilities are allowed.<br></span></span></blockquote></div><br><div>So while you are waiting you can spend time making sure</div><div><br></div><div> - That the documentation is up-to-date with your cool new code</div><div> - That all the new core functions and variables are part of the wiki cookbook and docs</div><div> - That you have configuration examples committed</div><div><br></div><div>Important question you need to ask yourself about your docs is not only if it's a good reference, but also if it clearly states the problem you are trying to solve. A reference just explains parameters - but that's not enough, you also need to explain why someone should use this module/function/pv and what's cool with it.</div><div><br></div><div>When your done with your own docs, feel free not to play games but to check existing documentation too.</div><div><br></div><div>Thanks - enjoy writing the docs before you restart coding new stuff after code freeze!</div><div><br></div><div>/O</div></body></html>