Camelia, the Perl 6 bug

IRC log for #metacpan, 2013-09-05

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

All times shown according to UTC.

Time Nick Message
01:01 dolmen joined #metacpan
01:15 klapperl_ joined #metacpan
03:26 mauke_ joined #metacpan
03:29 preflex_ joined #metacpan
07:12 bouncy joined #metacpan
08:35 ether_ joined #metacpan
09:04 daxim joined #metacpan
09:52 daxim joined #metacpan
13:07 SineSwiper joined #metacpan
13:09 alh oalders: Thanks, I'll play with that a bit
14:19 mo alh: you can use wildcards at the beginning but it will be terribly slow since it has to make a full scan
14:19 mo alh: all fields, however, are available as non-analyzed fields
14:23 alh mo: Where?
14:23 dipsy mo: Where are you moving
14:23 alh mo: Where? Just in autocomplete or ... ?
14:24 mo what do you mean?
14:27 alh All fields are available as non-analyzed
14:27 alh Where are they available? Do you have an example?
14:28 mo every fields is non-analyzed
14:28 mo some are analyzed such as abstract, pod etc.
14:29 mo alh: http://api.metacpan.org/file/_mapping
14:29 mo most say "index": "not_analyzed"
14:29 alh I haven't figured out how to get that to work
14:29 alh name for example
14:30 alh The names non-analyzed also has "index_options" : "docs" - what does that mean?
14:30 mo no idea
14:30 mo something ES added to the mapping
14:30 alh Like, if you search module.name.lowercase:some::module - it works
14:31 alh If you search module.name.name:*some*, it doesn't
14:31 mo yeah you need to build a json body, the short query syntax doesn't allow leading wildcards
14:31 mo *json query
14:31 mo like the autocomplete example oalders posted
14:31 alh Hrm
14:32 mo http://www.elasticsearch.org/guide/​reference/query-dsl/wildcard-query/
14:32 dipsy [ Wildcard Query | Reference Guide | Elasticsearch ]
14:32 alh Alright, wasn't aware of that limitation. Maybe that's it. Thanks
16:50 prateeksha joined #metacpan
16:56 prateeksha is perl participating in next round of opw? the one which has application deadlines in november 20113?
16:57 prateeksha 2013
16:58 prateeksha oalders, : is perl participating in next round of opw?
18:42 oalders prateeksha: that's a very good question.  i will find out for you :)
18:44 prateeksha oalders, : oh thank you
18:45 oalders prateeksha: you're interested in contributing to MetaCPAN?
18:49 oalders i've sent an email to karen pauley at the perl foundation, so we'll see what the OPfW status is
18:49 prateeksha oalders: yes. i wud like contribute in documentation with andriod
18:49 prateeksha oalders, : oh thank you
18:50 oalders prateeksha: documentation is good. not sure how android is related?
18:51 prateeksha oalders, i read abu the project on the site. it said documention on andriod could be done.
18:51 prateeksha so i wanted to know how i could contribute.. since i m new
18:53 oalders ah, yes. there *is* an android app which uses the MetaCPAN api.  that app itself doesn't need to be documented
18:53 oalders well, maybe it does, but that's outside our scope ;)
18:53 oalders essentially what needs to be documented from the ground up is how the API works
18:53 oalders what all of the end points do
18:53 oalders and the various ways to get data out of the API
18:53 prateeksha oh. ok.. how cud i help basically in documenting
18:54 prateeksha ?
18:55 oalders well, the first problem is that our documentation is essentially one wiki page with code samples:
18:55 oalders https://github.com/CPAN-API/cpan-api/wiki/API-docs
18:55 dipsy [ API docs · CPAN-API/cpan-api Wiki · GitHub ]
18:55 oalders there is more code here https://github.com/CPAN-API/metacpan-examples
18:55 dipsy [ CPAN-API/metacpan-examples · GitHub ]
18:56 oalders there's also this set of slides: http://www.slideshare.net/o​alders/abusing-metacpan2013
18:56 dipsy [ Ab(Using) the MetaCPAN API for Fun and Profit v2013 ]
18:57 oalders but none of that is very friendly for someone getting started
18:57 oalders it needs to be in a format that is a bit friendlier (or a lot friendlier)
18:57 prateeksha oh ok.
18:58 oalders basically what happens is that people start out with those docs, then come here and ask questions
18:58 oalders the questions get answered and then not documented
18:58 oalders and then it starts over again with the next person
18:58 oalders to use the API you also need to know a bit about ElasticSearch
18:59 oalders so the key is getting in some ElasticSearch (ES) basics into the docs without it being overwhelming for someone getting started
18:59 oalders ideally, to rework the documentation, you'd spend some time just trying to get started with the API first and note your frustrations
18:59 prateeksha i m new and i donot know perl. should i have to have knowledge to do this?
19:00 oalders do you have experience with other languages?
19:01 prateeksha c and c++
19:02 prateeksha i know. i m little intimated by coding so i m choosing documentation
19:03 oalders :)
19:03 oalders it would be hard to document the API without working in Perl, but you don't have to know a lot to get started
19:07 mst oalders: that's because you aren't enforcing the standard rule for perl projects
19:07 oalders mst:?
19:08 mst oalders: if we spent half an hour answering your questions, you then supply a doc patch to buy your next supply of newbie question credits
19:08 oalders ah, that's a nice way to approach it
19:08 mst also, the review of the doc patch lets the newbie be sure they understood the answers
19:08 mst so it's win all round
19:08 oalders right
19:08 mst that's how catalyst/dbic/moose have always done it
19:09 prateeksha ok. i m not very comfortable with coding.. so could i go ahead with documentation. not just andriod
19:09 mst hence how even the modules started by people like me who're awful at documenting still have reasonable docs :)
19:09 oalders :)
19:09 oalders we can't easily do patches with the wiki, but we probably should move it to a different format anyway
19:10 oalders prateeksha: if there's anything you can do to improve the documentation as it stands, i would welcome that
19:14 prateeksha ok i will try to read the wiki. and the links u told me about. i will see if i can do anything and get back
19:14 oalders prateeksha++
21:07 bowtie_ joined #metacpan
21:09 bowtie_ joined #metacpan

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