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