On Apr 5, 2008, at 6:02 AM, Shlomi Fish wrote:
Hi all!
In regards to the previous discussion about trimming down CPAN and
finding
better ways to find quality modules, I got an idea of making CPAN
"category"
reviews. The idea was originally derived from Freshmeat.net where
they often
have category reviews of the various software hosted there:
This is something I sort of started doing on perl101.org. "How do I
parse XML?" "Use this module" etc Your idea is a bigger & better
expansion of that.
However, my concern is that discussion has turned down the road of
where the reviews will live, what formats they'll be kept in, etc etc
etc. These are all technical issues and are the least of your concerns.
Like most projects of any size, the technical aspect is at most half
of the problem. The rest is the human side.
Who is going to write these reviews? Where do you expect them to come
from? Will they be posted by whoever wants to post them? Will there
be some sort of editorial oversight?
What are the categories? Who decides what the categories are? Do the
modules get starred reviews? How will differences of opinion be
handled?
Whenever I'm faced with this sort of requirements gathering, I find it
useful to come up with a mockup of what a screen might look like.
Your list of OOP modules is a good start, but there's room for
expansion. A full-blown HTML page mockup of what
cpanreviews.shlomi.com could be will help others visualize what you're
discussing. $picture == @words[0..999].
I think it's far more useful to talk about these human issues first.
The technical answers will fall out of the requirements that get
created.
xoxo,
Andy
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
