On Sat, 13 Jul 2002, John Porter wrote: > > Ask Bjoern Hansen wrote: > > [EMAIL PROTECTED] (John Porter) writes: > > > > > Yeah, look at the so-called Parrot FAQ. Someone needs to > > > get serious and make a real FAQ for parrot developers. > > > > I'm sure noone would mind if you start one! > > It does not work to ask the people who need the doc to write > the doc. Those with the knowledge must write the doc, so > that those without the knowledge can read it.
You're right, but on the other hand, it doesn't work for the people who know the system to ask the questions. The people who need the doc are in the best position to know what is clear and what is obscure. If it's not even clear where to dive in, say so -- "getting started" may be a specific area in which docs are lacking. What kinds of questions do you run into trying to approach the system for the first time? What do you think there should be pointers to? What is most helpful in the docs/ directory? What is least helpful? To help even more, you could collect the answers to these questions when you receive them, and make the resulting FAQ part of your contribution to Parrot. Write the FAQ you wish had existed when you first came. > For all I know, there are no frequently asked questions on the irc > channel. For all I know, there are no newbie parrot developers on the > channel. You're mostly right here, too -- from what I've seen, IRC is more a place where "oldbies" hash things out. But it doesn't have to be this way -- #parrot is a friendly channel, and its denizens seem receptive to questions. /s
