it would be cool to get the list from CPAN, and try to link them with github. For example, you search all Dancer::Plugin::* on cpan, for instance Dancer::Plugin::FlashMessage. You would then try to search for dancer-plugin-flashmessage or other variants on github. Some modules also point to a repository URL in the meta files (I do that for my modules). So it would bring the cool stuff from github, like code activity, numbers of branches etc, but still make sure it's stable enough (i.e. distributed on CPAN) to be worth mentioning. On 2 February 2011 10:25, sawyer x <xsawyerx@gmail.com> wrote:

That's a good idea. Maybe we could do that on the plane! :)

On Wed, Feb 2, 2011 at 10:52 AM, Gabor Szabo <szabgab@gmail.com> wrote:

...

hi, I just saw this link http://djangopackages.com/categories/apps/ IMHO it would be nice to have a page on the Dancer web site with information about all the Dancer plugins and maybe the related modules as well. Something fetched from CPAN and MetaCPAN but displayed differently.

regards   Gabor _______________________________________________ Dancer-users mailing list Dancer-users@perldancer.org http://www.backup-manager.org/cgi-bin/listinfo/dancer-users

_______________________________________________ Dancer-users mailing list Dancer-users@perldancer.org http://www.backup-manager.org/cgi-bin/listinfo/dancer-users

We could use my brand new MetaCPAN::API! :) On Wed, Feb 2, 2011 at 11:56 AM, Gabor Szabo <szabgab@gmail.com> wrote:

I'd stick to information in META.yml for the URL of the repository and educate the plugin authors where this information is missing.

Sawyer, the plan on the plane could work.

Gabor

On Wed, Feb 2, 2011 at 11:45 AM, damien krotkine <dkrotkine@gmail.com> wrote:

...

it would be cool to get the list from CPAN, and try to link them with github. For example, you search all Dancer::Plugin::* on cpan, for instance Dancer::Plugin::FlashMessage. You would then try to search for dancer-plugin-flashmessage or other variants on github. Some modules also point to a repository URL in the meta files (I do that for my modules).

So it would bring the cool stuff from github, like code activity, numbers of branches etc, but still make sure it's stable enough (i.e. distributed on CPAN) to be worth mentioning.

On 2 February 2011 10:25, sawyer x <xsawyerx@gmail.com> wrote:

...

That's a good idea. Maybe we could do that on the plane! :)

On Wed, Feb 2, 2011 at 10:52 AM, Gabor Szabo <szabgab@gmail.com> wrote:

...

hi, I just saw this link http://djangopackages.com/categories/apps/ IMHO it would be nice to have a page on the Dancer web site with information about all the Dancer plugins and maybe the related modules as well. Something fetched from CPAN and MetaCPAN but displayed differently.

regards Gabor

On 2011-02-02, at 4:57 AM, sawyer x wrote:

We could use my brand new MetaCPAN::API! :)

Of course! If you'd like a zip of a recent version of the ElasticSearch index, I can get it to you. That way you could run your own web service locally on the plane to test it out. You just need Java and about 256MB RAM

On Wed, Feb 2, 2011 at 11:56 AM, Gabor Szabo <szabgab@gmail.com> wrote: I'd stick to information in META.yml for the URL of the repository and educate the plugin authors where this information is missing.

I'm in the process of adding more info from the META.yml to the distribution info. Repository URLs are next on the list, so you should be able to run some queries to check which Dancer plugins do or don't have the URLs available in the META.yml files. That also makes it easy to link to Github etc right from the site. You could also pull in the POD if you want to display it directly on the site. For example, the POD for Dancer::Cookbook in HTML and plain text would be: http://api.metacpan.org/pod/Dancer::Cookbook I'll also be adding pure POD to that info in the near future, in case you want to process it yourself in some special way. Olaf -- Olaf Alders olaf@wundersolutions.com http://www.wundersolutions.com http://twitter.com/wundercounter 866 503 2204 (Toll free - North America) 416 944 8306 (direct)

On 2011-02-02, at 10:55 AM, sawyer x wrote:

On Wed, Feb 2, 2011 at 5:21 PM, Olaf Alders <olaf@wundersolutions.com> wrote:

On 2011-02-02, at 4:57 AM, sawyer x wrote:

...

We could use my brand new MetaCPAN::API! :)

Of course! If you'd like a zip of a recent version of the ElasticSearch index, I can get it to you. That way you could run your own web service locally on the plane to test it out. You just need Java and about 256MB RAM

Sure!

Great. I'll get you something in the next day or two.

...

On Wed, Feb 2, 2011 at 11:56 AM, Gabor Szabo <szabgab@gmail.com> wrote: I'd stick to information in META.yml for the URL of the repository and educate the plugin authors where this information is missing.

I'm in the process of adding more info from the META.yml to the distribution info. Repository URLs are next on the list, so you should be able to run some queries to check which Dancer plugins do or don't have the URLs available in the META.yml files. That also makes it easy to link to Github etc right from the site.

Is this something that is supported in the official API?

Since this is still beta, the API is flexible, but that will be supported for sure. I had tried just stuffing entire META.yml structures into the distribution info, but ElasticSearch doesn't know how to map it well. The problem is (I think) that the files can differ so wildly from dist to dist. So, I'm going to take the parts which seem to be the most important ones and make sure they appear in the distribution info. We could still have entire META.yml files available in the API, but in some other part of the index. But really, if you feel strongly about something, just ask me to include it or open an issue and I'll do my best to get it in there. Pull requests are also gratefully accepted. :) We've got #metacpan on irc.freenode.net, so that's also a good place to make some requests.

You could also pull in the POD if you want to display it directly on the site. For example, the POD for Dancer::Cookbook in HTML and plain text would be:

http://api.metacpan.org/pod/Dancer::Cookbook

MetaCPAN::API already supports it. :)

Actually, it already supports everything that is advertised in the official API!

Excellent!!! Olaf -- Olaf Alders olaf@wundersolutions.com http://www.wundersolutions.com http://twitter.com/wundercounter 866 503 2204 (Toll free - North America) 416 944 8306 (direct)

I agree. I think we should create this list manually, after we review plugins and allow a "here are really good ones people have been using for a while and proved themselves stable and useful" list. On Wed, Feb 2, 2011 at 12:30 PM, David Precious <davidp@preshweb.co.uk>wrote:

On Wed, 2011-02-02 at 10:45 +0100, damien krotkine wrote:

...

it would be cool to get the list from CPAN, and try to link them with github. For example, you search all Dancer::Plugin::* on cpan, for instance Dancer::Plugin::FlashMessage. You would then try to search for dancer-plugin-flashmessage or other variants on github. Some modules also point to a repository URL in the meta files (I do that for my modules).

I'm not sure whether it ought to be automatically generated, or a manually-generated list, with the plugins we find to be of most interest listed first; ideally we want people to look at this page and see all the things they're most likely to want to do with Dancer listed first, and realise there's a plugin for all the stuff they need.

If we automatically generate it, they're likely to have to read further through a list to see what's of interest to them.

We can also ensure each module gets a well-written description of what it does, so it's clear.

Basically, qx(pod2html Dancer::Plugins) would be a good start, since we already have that :)

Cheers

Dave P

-- David Precious <davidp@preshweb.co.uk> ("bigpresh") http://www.preshweb.co.uk/

_______________________________________________ Dancer-users mailing list Dancer-users@perldancer.org http://www.backup-manager.org/cgi-bin/listinfo/dancer-users