On Fri, Jul 2, 2010 at 16:16, Nuno 'smash' Carvalho <mestre.sm...@gmail.com> wrote: > Greetings, > > On Fri, Jul 2, 2010 at 7:54 PM, Chas. Owens <chas.ow...@gmail.com> wrote: >> On Fri, Jul 2, 2010 at 14:35, Caleb Cushing <xenoterrac...@gmail.com> wrote: >>> On Fri, Jul 2, 2010 at 10:03 AM, Chas. Owens <chas.ow...@gmail.com> wrote: >>>> If you want to sign up for the Perl 5 Documentation Team, leave an >>>> email here or email me directly. If you know what you want to work on >>>> mention it, otherwise I will assign you a task. >>>> >>> >>> me too (putting money where mouth is). >>> >>> can't look now but I recall some inaccuracy I found in perlre ... (or >>> related) docs... and I'd like to improve the docs on use features >>> 'state'; (note: not a regexpert) >>> >>> both of those are pretty small though... so what could I work on that's >>> bigger? >> snip >> >> Right now we need people reviewing [perlopquick][1] for mistakes and clarity. >> >> [1]: http://github.com/cowens/perlopquick > > Although I'm not a native english speaker i would like to try to find > some time to give a hand to this project. I will have a look at > perlopquick, but do let me know if you have a more suitable task for > me. Thank you. > > smash >
At this time, the high priority list looks like * reading perlopquick descriptions for correctness and clarity (this needs as many people as possible) * discussion of the proposed items in the list (this needs as many people as possible) * work on the logo/mascot * first draft about how to document documentation changes added to perlpolicy * finding a way to have one document that creates both a <DOC>.pod and <DOC>ref.pod -- Chas. Owens wonkden.net The most important skill a programmer can have is the ability to read.
