Perl 6 - the future is here, just unevenly distributed

IRC log for #pr-challenge, 2015-01-19

| Channels | #pr-challenge index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:29 thrig joined #pr-challenge
01:12 boreas_ joined #pr-challenge
02:20 sue_ joined #pr-challenge
02:24 BRAD_ joined #pr-challenge
02:53 Su-Shee_ joined #pr-challenge
03:08 boreas joined #pr-challenge
03:59 kentnl joined #pr-challenge
04:44 daveh joined #pr-challenge
04:57 boreas joined #pr-challenge
04:58 daveh joined #pr-challenge
05:07 reneeb joined #pr-challenge
05:19 nbezzala joined #pr-challenge
06:06 daveh joined #pr-challenge
06:13 panshin joined #pr-challenge
06:46 boreas joined #pr-challenge
06:56 StylusEater joined #pr-challenge
07:09 boreas joined #pr-challenge
07:14 daveh joined #pr-challenge
07:37 reneeb joined #pr-challenge
08:09 reneeb joined #pr-challenge
08:48 sue joined #pr-challenge
08:53 neilb joined #pr-challenge
08:59 shorty_mu joined #pr-challenge
09:30 mvuets joined #pr-challenge
09:34 neilb joined #pr-challenge
09:55 Su-Shee good morning everyone
10:09 absolut_todd joined #pr-challenge
10:11 veryrusty joined #pr-challenge
10:17 sue_ joined #pr-challenge
10:24 Mike__B joined #pr-challenge
10:39 haarg morning
10:47 veryrusty joined #pr-challenge
11:12 cakirke joined #pr-challenge
11:27 sue joined #pr-challenge
11:50 sue joined #pr-challenge
11:56 LLamaRider joined #pr-challenge
13:24 boreas joined #pr-challenge
13:25 Mike__B joined #pr-challenge
13:38 punter joined #pr-challenge
13:40 neilb yesterday was the first day without a sign-up since, er, sometime in December. Had one today, so currently 359 people have an assignment
13:42 Su-Shee nice :)
13:58 tinypig joined #pr-challenge
13:59 neilb don’t think we’re gonna hit a YAPC::Asia :-)
14:03 StylusEater joined #pr-challenge
14:20 gryphon joined #pr-challenge
14:55 vroom joined #pr-challenge
15:01 tinypig joined #pr-challenge
15:07 manito joined #pr-challenge
15:15 boreas joined #pr-challenge
15:21 daveh joined #pr-challenge
15:47 itcharlie joined #pr-challenge
16:18 Ptolemarch joined #pr-challenge
16:27 manito joined #pr-challenge
16:35 dolmen neilb, do you think you hit the Japanese community? How many participants from Japan?
16:36 neilb perhaps not, but Ishigaki-san was going to mention it at a meeting on Friday last week. Which reminds me, I need to email him!
16:37 * dolmen just tweeted him (and miyagawa)
16:43 * neilb must remember to check his spam box more regularly
16:46 itcharlie rjbs:  I did my pr as you recommended  thanks for the help.  https://github.com/arcanez/poe-component-dirwatch/pull/3
16:47 rjbs cool :)
16:56 Ptolemarch joined #pr-challenge
17:03 manito joined #pr-challenge
17:03 itcharlie1 joined #pr-challenge
17:04 boreas joined #pr-challenge
17:07 itcharlie joined #pr-challenge
17:21 manchicken_ joined #pr-challenge
17:21 Ptolemarch joined #pr-challenge
17:28 boreas joined #pr-challenge
17:30 panshin joined #pr-challenge
17:54 jluis_ joined #pr-challenge
17:59 neilb_ joined #pr-challenge
18:10 panshin joined #pr-challenge
18:33 manito joined #pr-challenge
18:36 mje_ joined #pr-challenge
18:49 mvuets joined #pr-challenge
20:29 manito joined #pr-challenge
20:38 manito joined #pr-challenge
20:43 punter joined #pr-challenge
21:28 sue joined #pr-challenge
21:56 sue_ joined #pr-challenge
22:20 veryrusty joined #pr-challenge
22:30 manito what's the license you people use nowadays? (of course besides the perl license for your perl code) - gpl? v2? v2 only? v3? or am i sweating the small stuff again?
22:30 Su-Shee "depends" I choose my licences very carefully.
22:31 pink_mist I tend to go with MIT by default
22:31 pink_mist unless I have reasons not to
22:31 manito good one. :) depends on what?
22:31 manito i am somehow set on some form of gpl. just because i do it for fun, not to help somebody make money with it.
22:31 pink_mist gpl doesn't stop anyone from making money with it
22:32 Su-Shee that's irrevelant for the GPL
22:32 manito at least they have a hard time hiding it where the code came from
22:33 manito i was more thinking about that whole "take my code and close-source it" which i don't wanna see happening
22:33 Su-Shee that's also not what the GPL says :)
22:46 neilb_ Here’s a table of the candidate dists (have a github repo listed in metadata, and repo exists): http://rawgit.com/CPAN-PRC/resources/master/prc-scores.html
23:09 ether neilb_: \o/
23:09 neilb_ thought you’d like it. You’ll like v2 even more, I’m sure
23:10 ether "click on score" --?
23:10 ether there is nothing to click
23:10 neilb_ first I’m writing a blog post describing how it works, to solicit input
23:10 neilb_ ether: read more carefully, especially the word at the start of that paragraph
23:11 ether heh ok :)
23:11 * ether is definitely interested in all the inputs to the score algorithm :)
23:11 ether looks like "has "deprecated" in abstract" is a bit contributor, judging by the placement of my dists in that list
23:11 ether all my top dists are "oh god, not THAT old thing!" :)
23:12 ether clearly I'm going to have to do some releases to add x_deprecated soon :)
23:13 neilb_ no, not *you*. Or rather when someone sends you a PR, *then* you can do a release
23:13 neilb_ basically if it appears to be marked as deprecated, but doesn’t have x_deprecated in the metadata, it gets a +1
23:14 neilb_ dists which have x_deprecated => 1 are excluded :-)
23:14 ether "there are more dists with the repo, but these are ones where the repo actually exists" --> seems easyish to have someone script up something that files tickets for all the others: "hey, your repo doesn't exist!"
23:16 ether another potential input for the scoring algo: has at least one pass report for 5.20.x, but only failures for 5.21.x
23:20 pink_mist one of my modules has that on purpose :> I just wish I could coax Dist::Zilla to bail out already at the perl Makefile.PL stage rather than failing the make test stage :/
23:20 vroom joined #pr-challenge
23:20 pink_mist but I can't seem to find a neat way to put some custom code in the Makefile.PL from Dist::Zilla :/
23:25 haarg https://metacpan.org/pod/Dist::Zilla::Plugin::MakeMaker::Awesome
23:33 haarg the author of the module i got for the challenge isn't doing perl anymore, so i suggested he find someone to take over the module.  he asked someone else who had contributed if they were interested.  now that person is getting a pause id to get comaint.
23:35 haarg so the prc resulted in someone who didn't sign up contributing as well
23:39 pink_mist haarg++
23:39 pink_mist thanks for that
23:39 pink_mist ether++
23:39 pink_mist suppose you deserve thanks too :P
23:43 neilb_ haarg++
23:43 haarg there's also https://metacpan.org/pod/Dist::Zilla::Plugin::DynamicPrereqs if you want to do dynamic prereqs easier, although that didn't sound like what you were looking for
23:46 pink_mist no, it's not a prereq =) I just don't want to support dev versions of perl
23:47 neilb_ http://neilb.org/2015/01/19/prc-scoring.html
23:48 haarg pink_mist: what module?
23:49 pink_mist Warnings::Version
23:50 haarg is there a reason it needs to have explicit support for dev versions?
23:51 neilb_ night all
23:51 pink_mist dev versions can change which warnings they have willy nilly
23:51 pink_mist so it's not something that's feasible to support imo
23:52 haarg but you already don't support odd versions as a tag
23:52 haarg seems like use Warnings::Version '5.10'; should work fine on a dev perl without any work
23:53 haarg another thought is that for $last_stable+1, you could just assume the category list from warnings.pm is accurate.  although i guess that requires poking into its internals.
23:53 pink_mist but '5.8' wouldn't
23:54 haarg why wouldn't it?
23:54 pink_mist there's no y2k warning since 5.8
23:55 pink_mist and when features stop being experimental, things will change even more
23:57 haarg wouldn't that mean '5.8' wouldn't work on any newer perl?  how is dev perl any different?
23:58 pink_mist I keep a list for each major version of perl which warning categoires it has
23:58 pink_mist *categories
23:58 haarg not supporting use Warnings::Version '5.21'; makes sense, i get that
23:59 haarg i'm just not sure why a 5.21 perl shouldn't be able to do use Warnings::Version '5.14';

| Channels | #pr-challenge index | Today | | Search | Google Search | Plain-Text | summary