in reply to Perl Monks += TMTOWTDI

++hacker for making an excellent point.

My suggestions:

  1. Associate keywords with the modules.
  2. Voting mechanism for module by perlmonks.
  3. Search CPAN with google like mechanism for keywords.
  4. Apply the sort orders. (Latest, Depend on, VoteRank, RefereceRank)

Notes:
Keywords will provide a very good search mechanism. Voting is not absolutely necessary. Sorting would keep latest/useful/obscure module within reach. It will also take care for the definition of better module for a given task as the time passes.

New Section - "I use this new module for":
We say that 90% code is written in terms of modules. May be we should establish a formal mechanism to introduce useful modules here. Perlmonk can say that I use such and such modules for this purpose(s) which will require lot less effort than module review section, but would be immediately helpful to us. Practical examples would serve an added value for modules to the documentation, tutorials and reviews.

artist

Replies are listed 'Best First'.
Re: Re: Perl Monks += TMTOWTDI
by Jenda (Abbot) on Apr 14, 2003 at 17:46 UTC

    I really like the 2) It would be cool if there was a section on Perlmonks were you'd see the listing of modules on CPAN and you could vote and attach notes to them. Whether the notes would be "I use this module for" or "Don't use this module, use that one" would be up to us monks. Maybe that would get more attention than the Reviews.

    I'll go on dreaming ... the module's page would be linked from search.cpan.org, it would contain some activity data (date of first version, dates of last N updates, ...), the module nodes would belong to the module authors if they are perlmonks so that they are notified of new notes, the voting on the modules look like the polls do, ...

    Jenda
    Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live.
       -- Rick Osborne

    Edit by castaway: Closed small tag in signature

[reply]
Re: Perl Monks += TMTOWTDI
by crenz (Priest) on Apr 14, 2003 at 18:24 UTC

    May be we should establish a formal mechanism to introduce useful modules here.

    I guess that is what the reviews section was meant for? I think "review" does not mean that the module has to be new, or extraordinary. A thorough review, with pros/cons, information about related modules, some code samples etc. is always useful, whether you already knew the module or not.

[reply]
      Current --->: Modules for which reviews are written:
      Of course, Module Reviews are there and helpful. That is a mechanism to fully describe the module, pros and cons in great depth. It's done by author or by the users who understand the module very well enough to explain others. We do have around 92 modules reviews currently.

      New --->:Recently Useful Modules:
      I am sure that people use much more than these 92 modules. I am proposing a section in addition to module reviews, about using the modules. So if you download a module from CPAN and found it useful in your code than you can post that information here as how it was useful to you. You may not have time to review it, but others can pickup your pointer and explore it further for the purposes similar to yours and other. This will be useful to perlmonks who want to keep up with the latest work without too much searching or analyzing.

      May be we can associate keywords with the module-node. It is to see which modules are used via perlmonks. Discussion on the same would provide valuable information for which 90% code (modules) should be used.

      Artist

[reply]

In Section Meditations