Thank you for your email. I was wondering where this
'Documentation in CVS' was. ^.^;; I suppose it's IN a CVS
somewhere, but you find it in <a href="http://api.drupal.org">api.drupal.org</a>, not <a href="http://cvs.drupal.org">cvs.drupal.org</a>.
It didn't seem very userfriendly to actually have docs in the cvs...<br>
<br>
To find a reference to the quick start guide in the handbook, though, I had to dig down deep. Not good.<br>
<br>
Beside the point, though. Do both stay? Both go? One go and one stay?<br>
<br>
I can't decide for anyone, because hey, like I'd make a patch.
;p But it would be nice for it to be decided... I like
cleaning up things (like bug queues) when I am bored and should be
doing something else.<br>
<br>
Anisa.<br>
<br>
<br><br><div><span class="gmail_quote">On 6/22/06, <b class="gmail_sendername">Heine Deelstra</b> <<a href="mailto:info@ustilago.org">info@ustilago.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Tue, 20 Jun 2006 08:55:31 +0200, Anisa <<a href="mailto:mystavash@animecards.org">mystavash@animecards.org</a>> wrote:<br><br>> So, on one issue, I think it was something about the form textfield<br>> something or other (
<a href="http://drupal.org/node/19441">http://drupal.org/node/19441</a>), I was simply updating<br>> the<br>> link to the new API, and Dries said that, quote "The only way to fix API<br>> documentation, is by submitting a patch against
<br>> Drupal core. This is not an issue for the documentation team so feel<br>> free<br>> to move it to the Drupal project instead."<br>><br>> So, that makes sense to me, OK, but I know I've seen API issues moved to
<br>> docs because it was documentation so what's the consensus? If we can all<br>> agree, then <a href="http://drupal.org/node/24572">http://drupal.org/node/24572</a> should be updated. There are<br>> maybe<br>
> half a dozen API issues in docs not getting much love, I wouldn't want<br>> them<br>> to just get shifted to dev, only to have a dev person say this is docs.<br>> It'd be kinda silly.<br><br>Hi Anisa,<br><br>
There are actually two parts to documentation in CVS; the autogenerated<br>API docs (from certain comments) and the docs that reside in CVS. The<br>first can only be updated with a patch to core, because the core code<br>
contains these remarks and docs are generated from it. The second can be<br>updated by generating a patch against the documentation files itself.<br><br>See for example <a href="http://drupal.org/node/70027">http://drupal.org/node/70027
</a><br><br>Regards,<br><br>Heine<br>--<br>Pending work: <a href="http://drupal.org/project/issues/documentation/">http://drupal.org/project/issues/documentation/</a><br>List archives: <a href="http://lists.drupal.org/pipermail/documentation/">
http://lists.drupal.org/pipermail/documentation/</a><br></blockquote></div><br><br clear="all"><br>-- <br>*********************************<br><a href="http://www.AnimeCards.Org">www.AnimeCards.Org</a><br><br>16,000 scans and counting!
<br>*********************************