Re: Roll Call
[email protected] (Jonathan Scott Duff)
| Newsgroups | perl.perl6.documentation |
|---|---|
| Message-ID | <[email protected]> |
On Fri, Nov 08, 2002 at 09:36:22AM -0800, Dave Storrs wrote: > Well, I'm here, FWIW. > > Here's my 2 copper Lincolns regarding scope and topics: You sure do need to watch your words these days, I saw "scope" and "topics" and thought I was still looking at perl6-language ;-) > I see a place for each of the following kinds of documentation: > - "How do I get started helping on Parrot"? > - "What do the guts of Parrot look like and why?" > - "I am a programmer with no Perl experience. Tell me why I > should switch to Perl6." > - "I am a Perl5 programmer. Tell me why I should switch to > Perl6." > - Online docs, a la the existing perlvar, perlfunc, etc > - Tutorials, a la the existing perltoot > > wrt the first two...some documents of this sort already exist, but we > could see what we can do to help/consolidate/clean them. > > wrt the last two...we may or may not want to use the existing formats. I think the focus should be on the last 4; primarily on the last 2. I think the documentation will grow in response to community needs but for now we can start with the seeds of existing methods/formats. > There was a discussion just recently of "cookbook" versus "online > book" style. I personally favor "book", because cookbooks are less > when you have a problem that isn't explicitly addressed, but that's > just MO. I think we need both. The book form would be more for learning the language and the cookbook form would be more for solving particular problems and, perhaps more importantly, relating perl6 to other languages. We should link the book to the recipes where appropriate and vice versa. -Scott -- Jonathan Scott Duff [email protected]