Re: Word for the day: Undocumentation

[Michael Scott]

<snip> ...too much undocumentation going on.

One of the reasons I started putting stuff on the wiki was because I 
could see that updating documentation was not a high priority.

On the wiki I neither have to have CVS checkin rights, nor do I have to 
wait for someone with those rights to act upon what I suggest. This has 
led to my own parallel documentation - I even document the state of the 
documentation.

I know what I have put together is incomplete and inadequate, but do I 
move it forward, and I keep it up to date.

When it comes to pointing out that parrot_assembly.pod is just an 
earlier version of PDD 6, or that the "Per-entity comments" section in 
PDD 7 needs some thought, or that a submissions.pod should be added, I 
get warnocked.

I'm fine with that, I understand why - this is not a rant - but I do 
think that Parrot has a steep learning curve and that good 
documentation is essential if we want to lower it. The potential 
benefits seem obvious.

I'd like to volunteer myself as official Parrot documentation person - 
a semi-autonomous process with clearly defined protocols and goals - 
and the necessary rights to achieve them.

I'm happy to expand on what I mean by that - if I get a response.

Mike