On Nov-17, Robert Spier wrote: > chromatic writes: > >My plan is to funnel all Perl 6 test patches through the normal > >process, so they may start showing up on this list. (If people > >object, we can find something else.) > > The perl6 queue is not currently active in RT. Since development is > primarilly happening on Parrot, things going into the parrot queue are > forwarded to perl6-internals. The perl6 queue is just "there". It > seems still to submit things for a project that doesn't have a > complete spec yet. > > >I'd like to get some code review on these patches, but I don't want to hold > >things up. If no one comments on them after a couple of days and if they seem > >to work, I'll probably just check them in myself. > >Everybody happy? > > I think we need a little bit of off-list discussion between the > appropriate project management to come up with a scheme for this that > prevents eggregious cross posting between mailing lists and keeps > everyone happy and efficient.
It looks like Sean (aka educated_foo) has taken ownership of those patches in RT. The last time we talked about whether perl6 should be discussed on the perl6-internals list, I believe the consensus was that it should, at least until a separate parrot-internals list is created. And it still would, after that list was formed, but the parrot discussion would move off. On the other hand, nobody seemed to be bothered enough by the list name to actually create the new list. Personally, I'm slightly in favor of creating parrot-internals immediately, but not enough to disturb either the Powers That Be (rspier, ask) or the denizens of perl6-internals. So I'd vote for either (1) making the perl6 queue go to perl6-internals the same way the parrot queue does, or (2) doing #1 and additionally redirecting the parrot queue to a new parrot-internals list. As for whether perl6 should be worked on before a language spec exists: definitely! I don't know how much of the current prototype will be kept (or what language the final version will be written in), but it has already proven to be very valuable as a test target for Parrot, and many people have been hoping all along that some prototype would be grown in parallel with the development of the spec. I want to see as much development on perl6 as is possible, and have been somewhat disappointed by the lack of interest it has garnered so far (though less so than Sean, I'm sure!)
