Perl 6 - the future is here, just unevenly distributed

IRC log for #perl6-toolchain, 2016-10-11

| Channels | #perl6-toolchain index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:21 tbrowder okay, i see the whole thing is a bit more complicated than it seems at first glance.  i will look but is the current ecosystem spec in one place or described in parts in perl6/ecosystem?
00:31 tbrowder ok, it seems to be in various parts of perl6/modules.perl6.org.  any docs anywhere else you know of (probably lots encapsulated in zef and panda)?
01:48 ilbot3 joined #perl6-toolchain
01:48 Topic for #perl6-toolchain is now Fire is step THREE! | https://github.com/perl6/toolchain-bikeshed | Channel logs: http://irclog.perlgeek.de/perl6-toolchain/today | useful prior art: https://metacpan.org/pod/CPAN::Meta::Spec
05:35 domidumont joined #perl6-toolchain
05:39 domidumont joined #perl6-toolchain
06:02 domidumont joined #perl6-toolchain
08:36 sjn__ joined #perl6-toolchain
08:49 JimmyZ joined #perl6-toolchain
10:36 FROGGS joined #perl6-toolchain
10:38 b2gills joined #perl6-toolchain
11:31 stmuk_ joined #perl6-toolchain
12:37 tbrowder .tell ugexe See if my view of the ecosystem is correct in this gist: https://gist.github.com/tbrowder/6f36138f4f3f704ac650b06ffc4bd7b5
12:52 u65 joined #perl6-toolchain
14:20 ugexe tbrowder: you can't enforce cpan stuff in the current ecosystem
14:20 ugexe how would you authenticate that
14:20 ugexe cpan and the current ecosystem should be viewed as two entirely separate entities
14:21 ugexe so cpan can define whatever meta fields they want to use as an interface, and the current ecosystem can (and currently does) define their own interface fields
14:25 perlpilot joined #perl6-toolchain
14:57 tbrowder well, what would you do differently? it seems to me we could add whatever it takes to the meta file so transfer or upload to cpan could be automated.
14:58 ugexe if you are going to submit something to the ecosystem, why not just submit it to cpan
15:00 tbrowder well then why are we using modules.perl.org? in any event, i'm just trying to work on what we need to enhance the current system. i guess i don't understand the big picture and what the transition plan is.
15:01 ugexe because the system is meant to have multiple content storages
15:02 ugexe if you have to run a dark pan its a lot easier to setup something like the ecosystem for instance
15:05 tbrowder so what we have now is dark pan? if i just uploaded my modules to cpan i would see them on modules.perl6.org?
15:05 ugexe no
15:06 FROGGS joined #perl6-toolchain
15:06 tbrowder then i don't understand why the objection to my observations for improvement on the existing system.
15:07 ugexe because you are requiring 1) oauth to be implemented somewhere so the ecosystem can auth against cpan 2) requiring cpan to add a specific interface to conform to perl6 isntead of perl6 conforming to the existing interface 3) assuming cpan and the current ecosystem will use the same meta6.json interface fields
15:12 tbrowder nothing at the moment is required. oauth implementation should be relatively easy to implement with p6 authors required to register with cpan. cpan shouldn't have to modify anything since the ecosystem could upload updates acting as each author during the transfer.
15:14 tbrowder maybe that's a naive vision, but it seems to be a good scheme to me.
15:15 ugexe the current ecosystem serves no purpose in that scenario
15:15 tbrowder current module authors wouldn't have to change procedures much at all.
15:16 tbrowder okay, i give up.  i just don't understand the void between the current and dream systems.
17:31 domidumont joined #perl6-toolchain

| Channels | #perl6-toolchain index | Today | | Search | Google Search | Plain-Text | summary