Perl 6 - the future is here, just unevenly distributed

IRC log for #metacpan, 2016-04-04

| Channels | #metacpan index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
03:24 punter joined #metacpan
06:04 melo joined #metacpan
06:11 oiami joined #metacpan
07:31 neilb joined #metacpan
07:54 khisanth_ joined #metacpan
07:58 melo joined #metacpan
08:10 Relequestual joined #metacpan
08:11 neilb joined #metacpan
08:44 punter joined #metacpan
09:16 oiami joined #metacpan
11:43 ribasushi joined #metacpan
13:56 Tempesta joined #metacpan
14:38 melo joined #metacpan
16:22 neilb joined #metacpan
19:57 krebbit joined #metacpan
20:16 mattp_ kentnl: I tried looking at what metacpan was using for its search query
20:20 mattp_ looks like its a straight lucene q query on /modules/_search ?
20:22 mattp_ oops thats not true nevermind. API::Module::search_collapsed
20:25 mattp_ what i was trying to see if results are boosted based on inputs (reviews ++s etc), i cant tell
20:30 ranguard the ++'s arn't taken into account at the moment
20:33 ranguard mattp_: https://github.com/CPAN-API/cpan-api/issues/253 is sort of related, though I think https://github.com/CPAN-API/metacpan-web/issues/1231 is probably the main point
22:03 vroom joined #metacpan
22:05 vroom joined #metacpan
22:07 ether I suspect the 'keywords' field in metadata isn't used either
22:18 vroom joined #metacpan
22:38 neilb_ joined #metacpan
23:09 castaway joined #metacpan
23:17 vroom joined #metacpan

| Channels | #metacpan index | Today | | Search | Google Search | Plain-Text | summary