I think I see two problems:
* a lot of people want to know what's going on, but not all have the
experience to be able to follow it
* it's difficult for the design to happen through the questions
How about we do this to design the architecture and API:
perl6-internals-design is for a team of no more than 10 people. These
people should have experience either with perl5 or with a similar
system. Mail to this list goes to perl6-internals-design and to
perl6-internals.
perl6-internals is a public access list, where folks can feel free to
question and kibitz. The design team will probably want to have a few
people on the public list as well. This is where the consciousness of
the rest of us can be raised. We can see what they're doing, ask
questions, and make suggestions. Because the meta discussion happens
off the -design list, designers will be able to tune it out if they
have to focus on the task at hand.
This lets us satisfy these goals:
* open process, both for visible and participation
* small team doing the design (elephant is a mouse designed by
committee, etc)
Make sense?
Nat
