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

Bug#149425: [Popcon-developers] Bug#149425: Please, do not forget to explain why you reset the severity of a bug



Bill Allombert <allomber@math.u-bordeaux.fr> a tapoté :

> On Thu, Oct 30, 2003 at 08:03:13PM +0100, Mathieu Roy wrote:
>> severity 149425 important
>> thanks
>> 
>> No reason was provided in 
>> <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=149425&msg=4>
>> to set severity as wishlist.
>
> This is not a bug in the package but on the popcon server side,
> that we cannot fix. We are in the process of reorganizing popcon
> to be able to improve the server side.
>
>> This pop-con project is interesting only if installing it on 100
>> computers of a network does not mean sending 10 Mb by mail per week,
>> just for statistical purpose.
>
> My popularity-contest file is 23kb uncompressed and 7.5kb compressed.
> Admitting you have more package installed, that lead to 10Mb
> uncompressed, 3.3Mb compressed and 4.4Mb base64 encoded. 
>
> If you have 100 computers, I expect they all have a similar packages
> use,

Why?

> so just install popcon on some of them. You will save more bandwidth
> and avoid flooding popcon with nearly identical reports, for which
> it is not well-designed.

Is pop-con a tool designed to have statistic on packages usage of
debian installations over the word or a tool designed to have some
sample of different basic installation over the world?

If it is the first case, pop-con should definitely receive input from
many systems as possible, whatever the fact that their setup they may
be usual or not.

> Anyway, I eagerly wait for your patches.

If you only want patches to get bug fixed, maybe the BTS should be
renamed in PTS, P standing for patch.


>> In my opinion, this problem is a bug, not a wish, and it fits the
>> following severity:  
>
> I hope you understand the above give more information about you than
> about the bug.

No, I do not understand. Please be more specific.


> I prefer to fix bugs instead of discussing their severities to
> death.

Who ask you to "discuss their severities to death", can't you focus on
this mail subject?


>> If you do not agree, please argue, do not just reset the severity
>> without any meaningful explanation, this is misbehaving, as DD you
>> agreed to take care about users.
>
> You ask for a new feature that require significant work to implement
> and is basically out of our reach at this point.

I'm surprised to hear that compressing data with gzip is an hard
work. 

>> Such a bug should not remain unfixed for "1 year and 143 days old", I
>> hope more attention will be paid to that problem with this more
>> appropriate severity.
>
> I hope you understand the above sentence is accepted by most Debian
> developers as a sufficient ground to killfile you.

You are a very hopeful guy apparently. I hope that most Debian
developers give a toss about the social contract #4. 


> Read the popcon changelog. I assume you will understand why this bug
> has remained unfixed for "1 year and 143 days old".

Undertanding why a bug is or is not fixed have nothing to do with the
severity of the bug.

> In case it is still not clear to you, don't waste the time of people
> that try to fix the problem. That is unlikely to make it fixed 
> faster.

In case it is still not clear to you, if having a user input is a
"waste of time" to you, you should maybe be asking for the deletion of
section #4 of the social contract you agreed with.


Your whole mail does not address at all the obvious subject of the
mail:
    Please, do not forget to explain why you reset the severity of a
     bug    



PS: I am not interested in any reply that does not deal with that
subject.


-- 
Mathieu Roy

  +---------------------------------------------------------------------+
  | General Homepage: 		http://yeupou.coleumes.org/		|
  | Computing Homepage:		http://alberich.coleumes.org/  		|
  | Not a native english speaker:					|
  |	http://stock.coleumes.org/doc.php?i=/misc-files/flawed-english 	|
  +---------------------------------------------------------------------+




Reply to: