Parrot Developer Summit this weekend: schedule; prepare roadmap goals

[Kevin Polulak]

On Sat, Jul 30, 2011 at 3:56 AM, Moritz Lenz <moritz at faui2k3.org> wrote:

> On 07/29/2011 03:49 PM, Jonathan "Duke" Leto wrote:
>
> 2) Recently I wanted to add some search paths 'load_library' to rakudo,
> from PIR or NQP. So I went to http://docs.parrot.org/parrot/latest/html/
> and read the list of documents there... and didn't even know where I
> should start reading. None of these documents seemed to even come close
> to describing what I wanted to do.
>
> Asking in #parrot, I got a pointer to IGLOBALS_LIB_PATHS, and the whole
> documentation I could find was
> include/parrot/interpreter.h
> 280:    IGLOBALS_LIB_PATHS,         /* LoL of search paths and dynamic
> ext */
>
> Try to call that user-centric...
>
> 3) http://parrot.org/dev/docs/user doesn't mention the bug tracker at
> all, only http://parrot.org/dev does. So do you only expect developers
> to submit bug reports?
>

I understand your frustration as I experience it myself on a daily basis. I
feel very strongly about the poor quality in documentation. Right now, our
only documentation is just a long and unorganized list of pod2html pages.
There are *tons* of little bits and pieces of Parrot that were left
undocumented by somebody who left the community yet they were the only
person who knew what it did.

I would really love to see something like a PDN Parrot Developers Network.
Though I'm not sure how big or little of an effort that would require. I
would throw myself on that team in a heartbeat.

-- 
- Kevin Polulak (soh_cah_toa)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.parrot.org/pipermail/parrot-dev/attachments/20110731/e0d00ffe/attachment.html>