Re: CPAN6 (was: A Semi-Public Version Control Repository for Your CPAN Modules)

2006-06-26 Thread Mark Overmeer
 Sam Vilain wrote:
 If you are in Europe in August, you might like to come to YAPC and see
 the announcement of cpan6, this concern is included in the design
 requirements and making small changes to other's code will be natural
 and safe.

* Randy W. Sims ([EMAIL PROTECTED]) [060626 06:12]:
 Has there been any public discussion of cpan6? I've only seen vague 
 references and wishful posting. Will the design requirements be open to 
 public review and comment before it's implemented?

Sam and I work on the CPAN6 idea for a few months now.  It goes much further
than simply security and multi-developer extensions to Pause. You can use it
to create, distribute, and merge CPAN-like archives; on a meta-archiving
level.  Especially this requires new terminology, which we now try to freeze
in the YAPC-paper and other design documents.  Public discussion on this
moment would eat all our time.  Of course, we hope it will grow into a
community project after the YAPC.
-- 
Regards,
   MarkOv


   Mark Overmeer MScMARKOV Solutions
   [EMAIL PROTECTED]  [EMAIL PROTECTED]
http://Mark.Overmeer.net   http://solutions.overmeer.net



Re: CPAN6 (was: A Semi-Public Version Control Repository for Your CPAN Modules)

2006-06-26 Thread Leon Brocard

On 6/26/06, Randy W. Sims [EMAIL PROTECTED] wrote:


Has there been any public discussion of cpan6? I've only seen vague
references and wishful posting. Will the design requirements be open to
public review and comment before it's implemented?


Of course not - but in the usual Perl way, if you don't like it, you
can build your own cpan6!
And release it to, errr, CPAN.

Sorry, slightly tongue in cheek.

But as with most Perl 6 projects, I have to ask: Why do we have to
wait for Perl 6 before we get a better CPAN?

Or is this getting too meta and should I wait until your yapc talk
instead... Leon


Re: CPAN6

2006-06-26 Thread Sam Vilain
Leon Brocard wrote:
 Of course not - but in the usual Perl way, if you don't like it, you
 can build your own cpan6!
 And release it to, errr, CPAN.

 But as with most Perl 6 projects, I have to ask: Why do we have to
 wait for Perl 6 before we get a better CPAN?
   

We don't, we're building it using Moose :-).  You're waiting on good old
fashioned hubris.

 Or is this getting too meta and should I wait until your yapc talk
 instead... Leon
   

Yes, come to the talk, it's 98% meta free and no added Schema.

Sam.