Perl 6 - the future is here, just unevenly distributed

IRC log for #pr-challenge, 2015-04-02

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

All times shown according to UTC.

Time Nick Message
03:14 frederico joined #pr-challenge
05:31 BRAD joined #pr-challenge
07:38 neilb joined #pr-challenge
07:51 neilb joined #pr-challenge
07:56 dolmen joined #pr-challenge
08:14 neilb joined #pr-challenge
10:03 frederico joined #pr-challenge
11:22 ribasushi joined #pr-challenge
11:37 kid51 joined #pr-challenge
13:27 vroom joined #pr-challenge
13:28 fredericop joined #pr-challenge
13:48 gryphon joined #pr-challenge
13:56 vroom joined #pr-challenge
14:11 kanashiro joined #pr-challenge
14:12 Ptolemarch joined #pr-challenge
14:28 tinypig joined #pr-challenge
14:42 Ptolemarch joined #pr-challenge
16:01 Ptolemarch joined #pr-challenge
16:14 kanashiro joined #pr-challenge
16:36 neilb joined #pr-challenge
16:45 gryphon Random thought question for PRC: My PR for last month has so far not been responded to. I have a suspicion my April PR will suffer the same fate. Would it be valuable to track how many PRs are responded to over time (either accepted, rejected, whatever)?
16:55 vroom1 joined #pr-challenge
17:25 vroom joined #pr-challenge
17:27 oalders gryphon: on that note, i have a little tool that helps evaluate how quickly PRs have been responded to historically for a repository: https://metacpan.org/pod/github-mergevelocity
17:28 gryphon Most excellent.
18:03 athos nice!
18:03 athos kanashiro ^
18:03 thrig alternate name: bueller... bueller... bueller...
18:10 Ptolemarch joined #pr-challenge
18:11 ambs google-protocolbuffers… gaah
18:23 fredericop joined #pr-challenge
20:30 neilb my march PR has been merged & released \o/
21:17 vroom joined #pr-challenge
21:18 Ptolemarch joined #pr-challenge
21:27 upasana Author of my March module has neither replied to my email, nor to my PRs!
21:27 Zoffix :(
21:28 neilb upasana: I’ve had dealings with him where he’s taken a while to reply, but does eventually. Patience may be the order of the day. The order of the year, in fact :-)
21:29 * Zoffix ponders including author activity history in score calculation.
21:29 upasana I've been waiting for his reply to my email from a month now, for PR's reply it's been only a week, so it's fine :)
21:30 ether Zoffix: modules where the author is inactive are the ones that are most likely in need of attention, though
21:30 upasana hehe, so true!
21:31 Zoffix Maybe pinging the inactive author first then... Yesterday, someone showed me a ticket I created 7 years ago... and module was never fixed.
21:31 vroom joined #pr-challenge
21:31 Zoffix "Hey, we'd like to assign your dist to PR challenge next month. Are you open to PRs?"
21:32 upasana Zoffix: My March PR is for a 6-7 yrs old RT ticket
21:32 Zoffix >_<
21:38 ether upasana: FWIW, you don't mention the RT# in your PR
21:40 neilb Zoffix: I need to work in oalders’s excellent merge velocity, as a indicator of likely author response
21:40 Zoffix \o/
21:41 upasana ether: oh no! Let me check!
21:43 upasana thanks ether, I updated it!
21:51 punter joined #pr-challenge
22:34 mishin joined #pr-challenge
23:06 kid51 joined #pr-challenge
23:17 kid51 joined #pr-challenge

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