I find it easier to remember which bugs I'm currently following by
simply checking my voting list.
Which works only as long as you do not follow more than 20 bugs (10 for
mail/news and 10 for the rest of Mozilla)
True. Luckily, there aren't that many bugs I've found I wanted to
Jacek Piskozub [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]...
Jason Bassford wrote:
I find it easier to remember which bugs I'm currently following by
simply checking my voting list.
Which works only as long as you do not follow more than 20 bugs (10 for
mail/news and 10
bugmail at all. I use a query based on bugs
that I've reported, where I've added a
comment, and on which I'm CC'd, that have
changed recently.
I find it easier to remember which bugs I'm currently following by
simply checking my voting list.
Jason.
I usually vote for features, and bugs that
I feel are important but getting overlooked
(like GNKSA compliance). Generally I think
that crashers are visible enough already,
so voting for them would be sort of a waste.
I vote for anything that's standing in my way of using the browser
The reason people vote mostly on enhancement bugs is that the rational
use of votes is to try to change the priorties of the engineers. If you
see that work progresses on a bug you do not need to vote for it.
Perhaps it would make more sense for Mozilla to have two different
types of
Jason Bassford [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
I usually vote for features, and bugs that
I feel are important but getting overlooked
(like GNKSA compliance). Generally I think
that crashers are visible enough already,
so voting for them
Hi Asa, thanks for the reply
Asa Dotzler wrote:
It is very underused making the wishes of a couple of people look much
more important than they probably should be. We have 15,000 active
Bugzilla accounts and the most voted for bug has like 150 votes!!!
Low voter turnout is a
David Coppit [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
Hi Asa, thanks for the reply
Asa Dotzler wrote:
What if it is a request for a feature that
would take significant enginering resources away from existing buggy
features. I never see
Asa Dotzler wrote:
snip
We try to tackle the most important bugs first. At
the top of the list are crashes, hangs and dataloss problems that affect
our users. Very few people vote for these types of bugs. Perhaps voting
would make more sense as a tool for Enhancement bugs only. It seems
JTK [EMAIL PROTECTED] wrote:
Such as performance and usablility, there's a good chance that they
could be missed. Oh wait, they've already been missed by orders of
magnitude.
Orders of magnitude being powers of ten, you're not even close.
Oh come on, indulge me just a little
If we get to the wonderful position of having no crash bugs, we do not
then land a whole slew of new features, however voted for they are. We
keep the stability and work towards shipping.
What about after shipping? I'm not necessarily only talking pre-1.0
release here. Will votes
Jerry Baker wrote:
Jason Bassford wrote:
1. Okay, if all development is forced to be only on crashers and
dataloss bugs I can see how people will not be able to work on
anything else until there are actually 0 of these. But, immediately
after that, since there is nothing else,
If we get to the wonderful position of having no crash bugs, we do not
then land a whole slew of new features, however voted for they are. We
keep the stability and work towards shipping.
What about after shipping? I'm not necessarily only talking pre-1.0
release here. Will votes matter
David Coppit wrote:
So here's my proposal: hype the bug voting some! Stick it on the main
mozilla page along side the bugzilla link. And integrate number of votes
in along with the talkback crash data, or at least keep a link to the
search page with the highest voted bugs/features.
I think
I'm not sure I completely understand this. If more work is being
done on crashers, etc. then there will end up being less (tending
towards, hopefully, 0) of them. The fewer number of crashers, the
GREATER amount of time that people will have to work on non-crash
related bugs. Some
JTK wrote:
Am I wrong in stating the
obvious fact (which I need not remind you even Mr. Hickson agrees with)
that Mozilla is nowhere near release quality? And that development has
been going on for four years?
Yes and yes. Since you love playing semantics, I'll do the same. To be strict,
Sadly, voting is going to get less relevant, rather than more. As we move
towards Mozilla 1.0, there will be fewer cycles for everyone's favourite
unimplemented cool feature as engineers concentrate on less sexy things
like crashers and dataloss bugs.
I'm not sure I completely understand
JTK wrote:
Ooof, that must have been a rough gig: Well, it's like four years now,
still nothing anywhere near ready to release. But we do have some
'liberating' commie graphics. There's coffee and cookies in the lobby,
thanks for listening.
I knew the civility and level-headedness that was
Aiy aiy aiy, was part of the discussion too. Not sure there was recording
equipment in the room, so transcripts maybe impossible.
Encouraging votes in usenet does sound like a nice idea.My votes:
35011 [DOM] window.onscroll and element.onscroll don't fire
52599 xul:srollbars should generate
jesus X wrote:
JTK wrote:
Ooof, that must have been a rough gig: Well, it's like four years now,
still nothing anywhere near ready to release. But we do have some
'liberating' commie graphics. There's coffee and cookies in the lobby,
thanks for listening.
I knew the civility and
On Wed, 1 Aug 2001, JTK wrote:
I've contributed what even *Gerv* believes to be a reasonable
performance criteria for 1.0 release
Er, well, for the record, Gerv was not quite as enthusiastic as I was. :-)
If AOL's screaming for a 1.0 release [...]
As far as I can tell (as an AOL
So during Mitchell Baker's talk on the State of the Mozilla Project at
the Open Source Convention, I asked why there are hardly any votes for
bugs. Her response was that voting seemed like a good idea, but was not
something that turned out to be useful in practice.
My followup questions was
David Coppit wrote:
So during Mitchell Baker's talk on the State of the Mozilla Project at
the Open Source Convention,
Ooof, that must have been a rough gig: Well, it's like four years now,
still nothing anywhere near ready to release. But we do have some
'liberating' commie graphics.
JTK [EMAIL PROTECTED] wrote in [EMAIL PROTECTED]">news:[EMAIL PROTECTED],
on 31 Jul 2001:
1. Play your violin while AOL HQ burns. This is probably the most
productive choice in terms of results gotten vs. effort expended,
since regardless of what anybody outside (and many inside) of AOL
JTK wrote:
David Coppit wrote:
So during Mitchell Baker's talk on the State of the Mozilla Project at
the Open Source Convention,
Ooof, that must have been a rough gig: Well, it's like four years now,
still nothing anywhere near ready to release. But we do have some
'liberating' commie
25 matches
Mail list logo
