[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Idea for determining what users use

From: Stefan Monnier
Subject: Re: Idea for determining what users use
Date: Wed, 28 May 2003 10:33:14 -0400

>     I think such an approach is much too much "in your face" and as a user
>     I'd run screaming.
> Why?

I don't know exactly, but I generally expect a program to just
do what I ask it to, and if it comes back telling me "I noticed this
and that, do you want me to send an email for you" I instinctively
cringe.   And it could be made worse if the program is actually unable
to send the email anyway (because it's not properly configured or
because there's no access to the net, ...).

In any case, whether the warning is just the current "package foo is
obsolete" message, or whether it's extended to be more noticeable (maybe
by adding a 2s sleep) or by adding a "do you want to complain about it?"
question or whatever else, is rather secondary (to me) at this point.

My point was more about the fact that I think the basis for such a
feature should be "is it in the `obsolete' directory?" rather than
some other new annotations.  The reason for it is that otherwise we
simply add another step "first annotate it for `about-to-be-obsoleted'",
then "move it to obsolete", then "maybe remove it".  I don't see the
need for the new first step since moving a package to "obsolete" does
not make it less functional.

And the conclusion of all that was that any package for which "it seems
like it's unused, but we're not 100% sure" can be moved to the
`obsolete' directory.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]