Please read the reply to your post carefully. It does answer your question. In particular the third paragraph.
By all means go ahead and write a CPAN Testers search engine. But I get the feeling from all these posts recently, everyone wants someone else (usually me) to do the work.
]]>My point was actually that my original query about not being able to search for the obscure XS errors quite possibly did not make a very convincing case for allowing search of the CPAN tester's site, and that perhaps a better example of the utility of search was needed.
By all means go ahead and write a CPAN Testers search engine.
You already have access to the text based reports, and the structured data is also described (see CPAN::Testers::Report, CPAN::Testers::Fact::LegacyReport and CPAN::Testers::Fact::TestSummary). Using test examples you can create a demo search site.
If you plan to host this yourself, David Golden can provide you with keys to access the metabase, from which you can obtain the structured reports. However, as the db is now so large, it will be better to run this on one of the CPAN Testers servers. Probably the metabase server. There is ongoing work to move the current setup to a new server, using MongoDB for storage, so that would be an ideal place to have the kind of search engine you want.
]]>A submission's score is simply the number of upvotes minus the number of downvotes. If five users like the submission and three users don't it will have a score of 2. Please note that the vote numbers are not "real" numbers, they have been "fuzzed" to prevent spam bots etc. So taking the above example, if five users upvoted the submission, and three users downvote it, the upvote/downvote numbers may say 23 upvotes and 21 downvotes, or 12 upvotes, and 10 downvotes. The points score is correct, but the vote totals are "fuzzed".]]>
http://blog.jacius.info/2012/05/29/a-personal-lisp-crisis/?
I'm thinking it's nice that in Perl we have people like Gabor who take an active role in caring about the perception of Perl from the outside world.
The last time I tried that, someone removed *all* the implementation links claiming "Wikipedia is not a code repository". I get the point, but sometimes having a link to some actual working code is useful. It's a very inconsistent standard.
Oh, and thank you very much for doing this. I have an edit queued up for after work.
]]>Since outbound Wikipedia links employ rel="nofollow", it's not going to help with SEO in this case, but it does expose people to another way to find Perl modules and that's a good thing. Once the number of links to MetaCPAN increases across other sites, the SEO situation should improve.
]]>@Dana Jacobsen, for a long time I tried to avoid editing Wikipedia after one of my articles was deleted without warning in a very stupid way, but I am sure some other people can handle Wikipedia better than I do.
So I can totally see the situation you were in, but as I see from the list of pages I linked to, there are also plenty of pages with links to the implementations. Indeed very inconsistent standard.
I'll do my best. Although fix all the Wikipedia will be difficult, according to the Spanish Wikipedia Perl doesn't have switch sentence... :(
]]>
Nevertheless, these are all good practices
I'm not a C/C++ programmer and don't know the pains here, but it seems with a tool like this one we can detect and solve them. Obviously the work is a pain in the ass to deal with but I guess that's the result of using an open standard like C
]]>Jeffrey: Nah, I read it as a regex-like thing and got the right answer immediately - a *multiple* of two would obviously require "aa"A/"aa" or similar, no? I think perhaps it might be an interesting exercise for you to show a few more "intuition defying" examples to a few perl hackers some time and see whether it truly defies intuition in general or merely *an* intuition, and we have a different one.
-- mst
]]>