On Wed, Aug 06, 2003 at 09:43:13AM -0500, Mark Stosberg wrote:
I don't mind that there are a lot of rarely modules that are still
accessible. I mind when they show up in search results and I have to
wade through them to get to the juicy modules. There is not an easy way
to distinguish the
On Tue, Aug 05, 2003 at 09:47:09AM -0500, Ken Williams wrote:
I agree. There are plenty of modules on CPAN that people still find
useful even though they haven't had recent development on them. It's
much better to inform people of known/serious bugs in modules, than to
try to guess at
On Aug-04, James E Keenan wrote:
Searching via All:
1st distro appearing is Test::More as part of Palm-Progect-2.0.1 by Michael
Graham. Schwern's Test::More appears 4th on list. Note: In recent weeks
1st distro appearing under this search was Test::More as part of
parrot-0.0.010 by Steve A
On Tue, Aug 05, 2003 at 01:27:47AM -0400, Christopher Hicks wrote:
Maybe the e-mail should do something informative like list how many years,
months and days it's been since a given module has been updated. Some
weak souls might be guilted into pushing out bug fixes sooner.
If there are no
* Steve Fink ([EMAIL PROTECTED]) [05 Aug 2003 19:12]:
[...]
He also said there's no way to suppress the indexer.
At the time, yes.
A format using the META.yml file has sprung up.
Check out your local cpan mirror at the file:
Sorry for beating the dead horse a little more, but here goes...
On Tue, 5 Aug 2003, Nicholas Clark wrote:
On Tue, Aug 05, 2003 at 01:27:47AM -0400, Christopher Hicks wrote:
Maybe the e-mail should do something informative like list how many years,
months and days it's been since a given
Christopher Hicks [EMAIL PROTECTED] writes:
On Mon, 4 Aug 2003, Nicholas Clark wrote:
How much do you hate mailman for all those here is a reminder of your
mailing list memberships messages?
They're only slightly irritating and I get a dozen of them every month.
If they wouldn't show
On Mon, 4 Aug 2003, James E Keenan wrote:
May I begin a separate thread for a line of discussion coming up under
the dead camels?
Sure.
I'm going to present empirical observations only; it would be premature
to make suggestions for changes until we heard from more contributors.
It's never
elaine wrote:
I also used to run analog on the search logs but, again, I
doubt that they would be accurate in any way for measuring module
downloads and interest.
They're not, as I can readily attest. According to those stats, CSS::SAC is one
*really* popular module. Ego boost apart, I know
On Wed, Aug 06, 2003 at 04:06:34AM -0500, elaine wrote:
On Tue, Aug 05, 2003 at 01:09:52AM -0400, Christopher Hicks wrote:
(A) Do we have any idea what tha algorithm it's using is?
Soundex for everything but Authors and Docs which then uses CPAN::WAIT.
I suppose that explains why
On Tue, Aug 05, 2003 at 11:17:36AM +0100, Nicholas Clark wrote:
On Tue, Aug 05, 2003 at 01:27:47AM -0400, Christopher Hicks wrote:
Maybe the e-mail should do something informative like list how many years,
months and days it's been since a given module has been updated. Some
weak souls
On Mon, Aug 04, 2003 at 11:43:40AM +0100, Sam Vilain wrote:
It turns out that in June there were 4000+ hits on modules in
Andy, why don't you talk with acme about getting such information
added to the CPANTS metrics... clearly it is something that authors
want to know.
If it matters, CPAN
* Gabor Szabo ([EMAIL PROTECTED]) [03 Aug 2003 18:31]:
[...]
If I encounter such a module what should I suggest to the author ?
Ask the author to update or delete. Or offer to take over maintenance.
Your problems begin when you can't *find* the author.
Some of the older dists that bundle in
Iain 'Spoon' Truskett [EMAIL PROTECTED] writes:
Ask the author to update or delete. Or offer to take over maintenance.
Your problems begin when you can't *find* the author.
Maybe a periodic 'ping' to module maintainers (e.g., once every two or
three months) and mark maintainers (and their
On Mon, 4 Aug 2003, Johan Vromans wrote:
Maybe a periodic 'ping' to module maintainers (e.g., once every two or
three months) and mark maintainers (and their modules) that miss a
couple of pings. Modules marked as such could be returned last by the
search engines, and be clearly marked as
On Sunday 03 August 2003 17:45, Andy Lester wrote:
There's a distro on CPAN now called lcwa that I would love to see
disappear. It's from 1997 and it's one of those distros that
included all its necessary parts rather than rely on depencies.
Unfortunately, those parts are 6 years out of date,
It turns out that in June there were 4000+ hits on modules in the
could you please teach me how do you look such statistic?
Is it available for public?
Andy, why don't you talk with acme about getting such information
added to the CPANTS metrics... clearly it is something that
At 10:34 AM +0400 8/4/03, Konovalov, Vadim wrote:
I wouldn't mind there being something in PAUSE that says you have to
touch the module once a year. I don't mean worthless updates, like
but how do you distinguish cases when module does not need updates, just
because it does not needs to be
Andy, why don't you talk with acme about getting such information
added to the CPANTS metrics... clearly it is something that authors
want to know.
Oh, I have. It was talking with Leon that this project first came
into being. My goal isn't to have an ongoing stats collection
process like he's
Try Test::More, it's true home is Test::Simple but that's 5th on the list.
Understood. HTTP::Response was just an example, and one that was
annoying me because of the skewing of the stats I was collecting...
--
Andy Lester = [EMAIL PROTECTED] = www.petdance.com = AIM:petdance
Hello,
As long as we are discussing ways to improve the quality of CPAN, this
seems like a good time to mention CPANTS. While addresses Dead Camels
does patch a hole in CPAN, Schwern's CPANTS proposal provides
a complete solution for quality control for CPAN.
Here's a link to more information
On Mon, Aug 04, 2003 at 10:24:29PM +0200, Elizabeth Mattijsen wrote:
This could be as simple as sending an email once a month to the CPAN
id's mail address and set a flag when it has bounced. Maybe once a
year you would like the author to actually reply to make sure the
mail isn't going
May I begin a separate thread for a line of discussion coming up under the
dead camels? The discussion suggests we should also look at (1) what
search.cpan.org comes up with in searching for modules; and (2) what links
PAUSE builds when it extracts POD from an uploaded module. I'm going to
There are a few modules on CPAN that seem to be dead.
Without pointing fingers (to myself :-), let's say there is a
module called Dead::Camel someone started to develop, uploaded to
CPAN but it never reached any form of usable version or for some
other reason it is unusable today.
Eliminating
24 matches
Mail list logo
