[diverting to p6-doc] Luke Palmer wrote: > As for your documentation plan, I think it's a good idea, though I > concur with Dan on Just Do It. Document the language for what best > makes sense now. If there are *big* issues, ask Larry et al. on this > list. For the little ones, use common sense and they will be hashed > out later.
Close. But you're part of the Perl 6 project now, you have a much more direct route than p6-lang. Use it. Here's the proposal. Just like Parrot, the documentation project acts as a self-organizing independent unit within the larger project. You pick one person as "Chief Architect" (or whatever). He'll try to answer most questions. When he can't answer a question, he'll escalate it to me and I'll either answer it or route it to the rest of the design team. This will also help make sure the documentation project only takes up Larry's attention when it's an issue only he can answer. Allison
