[documentation] API documentation for dev, not docs?

[Anisa]

On 6/23/06, Greg Knaddison - GVS <Greg at growingventuresolutions.com> wrote:
> On 6/21/06, Anisa <mystavash at animecards.org> wrote:
> > 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.
>
> Anisa,
>
> Making patches is surprisingly easy.  And finding out how to do it in
> the standard Drupal style is equally easy:
>
> http://drupal.org/diffandpatch
>
> It's confusing for like 10 minutes and then you do a couple and then
> it makes sense.  And then you can see your name in the log messages
> for Drupal CVS which is one of the most gratifying things of being
> involved in OSS in my opinion...

^.^  I like helping out in handbook documentation.  It's pretty
gratifying for me.  There's plenty of work there to do without
fiddling in things I really don't know about.  There are *reams* of
pages that use a lot of words to say absolutely nothing!  ^.^

> another person who hits the drupal.org/bug-bingo when bored,

Isn't it fun?  I do forum support too.  I can't answer any but the
most basic of questions, but it's nice.  It's something to do when
there's nothing on TV, which, in Japan, is quite often.

Still, the question remains, is API documentation, the stuff on
api.drupal.org a docs issue or a dev issue?  I just want someone to
say something either way so I can move or update the bugs.  :)

Anisa.

-- 
*********************************
www.AnimeCards.Org

16,000 scans and counting!
*********************************