Re: Guidelines for internals proposals and documentation

At 07:35 AM 11/15/00 +0000, Mike Lacey wrote:
>----- Original Message -----
>From: "Dan Sugalski" <[email protected]>
>To: <[email protected]>
>Cc: <[email protected]>; <[email protected]>; "Nathan Torkington"
><[email protected]>
>Sent: Tuesday, November 14, 2000 10:59 PM
>Subject: Guidelines for internals proposals and documentation
>
>
> > Here are some guidelines for the design process for internals-level docs.
>
>(good stuff ommitted)
>
> > 7) These are *not* brainstorming documents! These are solid, concrete
> > proposals for either the design or implementation of perl 6. If you have a
> > brainstorm but don't currently have the skillset (or requisite brain
> > damage... :) to make a concrete proposal, get in touch with either the
> > correct WG chair or Nat or me, and we'll do our best to hook you up with
> > someone in a position to make your ideas concrete.
>
>Dan,
>
>Shouldn't there be another stage (that other people could contribute to)
>before you pass a wild-but-maybe-useful idea to
>someone?

Yup. That's what the lists are for. If the split list format doesn't work 
(and it might) it'll be on perl6-internals, otherwise it'll be on the 
appropriate sub-list.

					Dan

--------------------------------------"it's like this"-------------------
Dan Sugalski                          even samurai
[email protected]                         have teddy bears and even
                                      teddy bears get drunk