However, I do believe in the following scenario:
- oh, there is an assertion warning, it's not my fault, let's allow one
assertion;
- wait, there are a few, let's allow several;
- oh, they are intermittent, let's make it an interval;
- [at some point, some of the warnings are fixed, but nobody real
On 09/06/2015 23:19, R Kent James wrote:
Without voting, how do you direct users to express an interest in seeing
a bug solved without adding a "me too" comment?
Maybe the answer is that we don't. We just need to be honest - it would
be very difficult to create a fair system that could be used
Regarding CC instead of voting, there is another issue. Voting is not
enabled in every component, so on these bugs I add me to the CC list.
But sometimes it happens that a bug will be marked as confidential after
I added me to the CC list. In that case I have still access to the not
public bug.
Original-Nachricht
Betreff: Voting in BMO
Von: Mark Côté
An:
Datum: 2015-06-09 23:09
To that end, I'd like to consider the voting feature. While it is
enabled on a quite a few products, anecdotally I have heard
many times that it isn't actually useful, that is, votes aren't re
On 6/9/15 11:09 PM, Mark Côté wrote:
> To that end, I'd like to consider the voting feature. While it is
> enabled on a quite a few products, anecdotally I have heard
> many times that it isn't actually useful, that is, votes aren't really
> being used to prioritize features & fixes. If your team
On Tue, Jun 9, 2015 at 11:09 PM, Mark Côté wrote:
> To that end, I'd like to consider the voting feature. While it is
> enabled on a quite a few products, anecdotally I have heard
> many times that it isn't actually useful, that is, votes aren't really
> being used to prioritize features & fixes.
On 6/10/15 1:24 PM, Dirkjan Ochtman wrote:
> Similarly, I could imagine that the very explicit CC list could be
> changed to be more like a Follow button, plus a (simplified) way to
> include others for those who have relevant privileges.
Have you seen the experimental bugzilla UI? It has a "follo
On 2015-06-10 3:55 AM, Mark Banner wrote:
Replying to this got me thinking - what about changing "vote" to "I
have this issue" similar to support.mozilla.org. However, I think the
usefulness would end up in the same way as voting.
As a suggestion though, how about adding something near the c
On 2015-06-10 3:38 AM, David Rajchenbach-Teller wrote:
However, I do believe in the following scenario:
- oh, there is an assertion warning, it's not my fault, let's allow one
assertion;
- wait, there are a few, let's allow several;
- oh, they are intermittent, let's make it an interval;
- [at so
On 2015-06-09 11:58 PM, Wayne wrote:
>> That said, there are much bigger issues with Bugzilla's UI, and removing
>> voting is probably the smallest possible improvement. But it's probably
>> easy to just disable it for a while, and see what happens?
>
> I never have seen the voting UI as being the
I'm 99% sure we've had mis-stars on intermittent assertion oranges where
the assertion changed and nobody bothered checking the logs to notice.
Various media tests are coming to mind for when that's happened.
On 6/10/2015 10:10 AM, Ehsan Akhgari wrote:
On 2015-06-10 3:38 AM, David Rajchenbach-
Philipp Kewisch schrieb:
I could live without this feature if the number of people on CC gives
some indication of how wanted a feature may be.
Well, I tend to CC myself to thing I seriously do not want to change but
really want to be informed about when they actually get done. I wouldn't
use
On 2015-06-10 7:06 AM, Philipp Kewisch wrote:
> I could live without this feature if the number of people on CC gives
> some indication of how wanted a feature may be. Can you check
> correlation between the number of votes and the number of people on CC?
A quick scan of the Core & Firefox product
Greetings,
Over in bug 968520, FallibleTArray is being merged into nsTArray.
After the bug is complete, we will be left with just nsTArray (and
nsAutoTArray). Fallible allocation will be opt-in using the
`mozilla::fallible` parameter just like with ns*String.
As a first step in this transition, i
I'd like to point Firefox and platform developers at this doc:
https://wiki.mozilla.org/Firefox/Data_Collection
Several times recently I've discovered that developers are unsure what
the rules are for collecting data. Last year, I worked with Marshall
Erwin to clarify decision-making about dat
We're using this meta-bug to track shipping Service Workers to the release
channel on desktop and Android:
https://bugzilla.mozilla.org/show_bug.cgi?id=1059784
For B2G-specific Service Worker issues we're using this meta-bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=1131322
And for "post-v1
Thanks for all the input on this feature. This was a good discussion.
Here's what I've learned:
* Almost no one makes decisions based on the number of votes
(Thunderbird and related may be an exception).
** Ergo, most users voting on bugs are probably being misled into
thinking their vote ac
On Wed, Jun 10, 2015 at 05:37:03PM -0400, Mark Côté wrote:
> Thanks for all the input on this feature. This was a good discussion.
> Here's what I've learned:
>
> * Almost no one makes decisions based on the number of votes
> (Thunderbird and related may be an exception).
> ** Ergo, most users
On Thu, Jun 11, 2015 at 9:37 AM, Mark Côté wrote:
>
> * Change bug tagging to something like "favouriting" (or a word with
> less contentious spelling ;). Rework the UI to provide an obvious
> way to both favourite a bug and to see your favourites list.
>
...
> * After those are in place, t
19 matches
Mail list logo
