Mailing lists and RFCs

Nathan Torkington writes:
| Ask, please create these lists:
| 
| [email protected]
|   This list is for discussion of internals design, architecture
|   changes, embedding, extending, and so on.
| 
| [email protected]
|   This is for discussing user-visible changes to the language.
| 
| [email protected]
|   This gets copies of all the perl6-* traffic.  Intent: if you reply to
|   a message you got via this list, your reply goes to the original list.
| 
| [email protected]
|   This is a moderated list, for news of new lists, RFCs, working
|   groups, and so on.


An idea; perl6-modules.  This would _not_ be akin to c.l.p.modules, not
for general CPAN use, but for core modules.  Much has been bandied about
regarding the potential modularization of parts of the core; I don't
want to discuss that, but I do imagine that:

1)   Many current core modules might need to be updated, perhaps we
would take the opportunity to rewrite.

2)   Some new modules might be necessary to implement current core
functionality.

I imagine this to be separate, though not unrelated, to the general
language design, and such a list would focus more on how to and
prioritization of such implementation, as opposed to language
decisions.  It might also be accessible to many people who want to help
implement, but not feel comfortable messin' with the core.

Thoughts?


-- 
See, the stars are shining bright
Everything's all right tonight
	-- (Martin L. Gore, Never Let Me Down Again)