* Yuval Kogman ([EMAIL PROTECTED]) [060304 00:40]:
I think Perl 6 could use a wiki for several things:
Last week, I was looking for ideas/plans about the required changes in
CPAN, and it was so increadibly hard to find the documents. People tend
to use SVN as substitute means of publication and everything is spread-out
over too many websites and directories.
The danger is that just another website is started, making the confusion
even larger: good intergration is crucial. Commitment of the verious
design groups.
It would be nice to have the CPAN-ID's and password for authenication
(like RT does) to reduce the maintenance effort.
One thing which is playing in my head already for some time is:
Do we really want a translation from Perl5 modules into Perl6 on
a one-to-one basis? There are so many deceased modules occupying
beautiful name-spaces! Can we please re-arrange the name-spaces?
Could we try to kind-of pre-register name-spaces for perl6 modules?
Maybe like the european new TLD .eu is being sold. If you own a perl5
name-space on this moment, you can claim the same name with preference
for perl6, but otherwise people may suggest replacements. The Wiki as
name-space market.
Wouldn't it be nice when -for instance- the various XML-module
implementators tried to design the best new XML interface together?
IMO, a wiki is excelent for that, because discussion threads on
mailinglists are not usable as design documents.
I was unhappy so see some of MY MODULES be already translated into Perl6
by someone. Although it is nice that people put effort in building
a library for Perl6, it is IMHO incorrect to suppose that the Perl5
(sometimes even perl4) herritage should be preserved for our nice new
language. Perl5 modules should run as Perl5 on Parrot. Perl6 modules
should use the new power of Perl6: not only inside the module itself,
but especially in the interface presented to the users.
I do second your idea for perl6 design wiki! Together we can work-out
new interfaces and at the same time learn how to use the new features
we got from each other. It's quite a big leap we can -and have to- make!
NOW is THE chance to improve the quality of our code base.
--
Regards,
MarkOv
Mark Overmeer MScMARKOV Solutions
[EMAIL PROTECTED] [EMAIL PROTECTED]
http://Mark.Overmeer.net http://solutions.overmeer.net
