On Wed, 2011-06-08 at 17:04 -0400, [email protected] wrote:
> The 691 open SpamAssassin bugs are kind of overwhelming to tackle.
>
> I'd like a way to tell bugzilla "I've looked at this bug and decided I'm
> not going to do anything with it until further notice, please never show it
> to me again." And then have all searches default to not listing anything
> with that flag set.
If you are ever *searching* again later after you glimpsed through all
of them, you are likely to have a different view on what would matter to
you. Otherwise, you could just have a look at the new ones (advanced
search, limit by date).
I suggest you invert that logic. Anything that stands out to you, and
you feel important to watch -- add yourself to the Cc list. And
obviously, keep a separate bugzilla mail folder for them. There are
really handy X-Bugzilla headers for advanced filtering, including
Reason.
> I'm wondering if you folks have better ideas on how to implement it,
> before I ask the bugzilla people for it.
And then have ASF Infra team backport the patch, apply manually for us,
and maintain the custom patch. Rather unlikely, at the very least not a
good idea.
> A possibility that occurred to me was including functionality similar to
> launchpad.net's "Does this affect you?" So you can sort bugs by the number
> of people who have said a bug affects them.
That feature is called Voting -- basically a +1, without leaving a
noisy /me too comment. We just don't have it enabled, and I strongly
believe we should keep it that way.
> And I could see doing more than just a yes/no/maybe value, and having a
> personal priority for each bug. But I suspect that's getting out of hand.
Labels in your bugzilla mail folder.
> Might be important to separate "Are you interested in this being fixed?"
> and "Is there any chance you might fix it?"
Voting is the first one, leaving a real comment the latter. "Might" is
just useless, adds to the noise, and prone to counter-productively
prevent another volunteer from working on it. Feel free to leave a
comment that you are actually working on a fix, or just attach a
patch. :)
> I think I'd probably just do it as "Do you care about this bug?" with
> yes/no/maybe values, defaulting to maybe.
Bugzilla is bug tracking tool. While it has some functionality for
voting, I'd rather not make it a public voting forum. The community
(limited to people administrating mail servers, not their users) and the
number of bugs is sufficiently small, that adding meaningful comments
expressing why a feature might be especially desirable, is manageable.
> There really are an amazing number of bugs in there that I'm just never
> going to care enough about to work on. And I bet the rest of you feel the
> same, which is why there are 691 open. Might be nice to close more of them
> WONTFIX. Maybe vote on some that nobody is ever likely to care enough to
> fix?
Someone cared enough to outline the issue or feature request, and with
first time users even to dip his toe into the community tools. Almost by
definition, the reporter *is* likely to care enough, to maybe fix it
himself.
Itch. Scratch.
> Like the (exactly) 100 that are over 6 years old. Maybe add another
> resolution "DONTCARE" in case anybody ever feels chronically motivated
> enough to go dig this stuff up after fixing everything else. (603 bugs
> have been closed WONTFIX.)
Just go through the list of WONTFIX'ed bugs?
--
char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
