"Eric Wilhelm" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> >FORBID any module without a meaningful readme with all its (possibly
> >recursive) dependencies, its pod and any other relevant information
> >inside.

> I don't think it is in the spirit of CPAN to "FORBID" anything.

OK. but a module without a readme with meaning ful content, a minimum of
documentation is not "anything" it's "nothing" so I'd say it's OK to not
allow "nothing" to get into CPAN. We, of course, want to avoid waisting our
time but I think all want to help the module author to get the a chance to
be used.

I would also forbid (yes that's forbid this time) modules without makefile
to make it into CPAN.

There is unfortunately no system to check if "meaningful documentation"
exists in the distribution or not (some AI guru may want to look at this :-)

The spirit of CPAN is quite straighforwardly described when it come to
documentation but unfortunately a dummy (dumb) readme is generated instead
for "forcing" the user to write one.

The access to CPAN is not moderated in any way (my anarchist side likes
that) but maybe a minimum of control wouldn't hurt (my fascite side like
that)

Cheers, Nadim

PS: I wouldn't  like to find commercial modules on CPAN either


Reply via email to