Thread: maemo.org Bugzilla 2008 statistics (1)
View Single Post
Jaffa's Avatar
Jaffa is offline Jaffa
2009-01-04 , 16:17
Posts: 2,535 | Thanked: 6,681 times | Joined on Mar 2008 @ UK
#8
Originally Posted by igor View Post
That is not so black and white.
Indeed, I was being (slightly) facetious. However to respond to some concrete examples:

As you can immagine, bugs are not really so easy to partition. Consider a reporter or beta tester reporting a bug on component A which is open, but further analysys showing that it belongs to component B, which is closed.
What happens to the bug? does it disappear? does it get closed till component B is published as well?
There are two possible scenarios here:
  1. Reporter is raising a bug against a publicly shipping version of Maemo. Doesn't matter if component-B is open or closed source, the bug still exists and needs to be triaged and dealt with.
  2. Beta-tester is raising bug against an unreleased software version or device. For the first part, I'd say that as long as the "applies to version" is set to a version which is not publicly available, all bugs in that version should be hidden from people without certain privileges. If it's a hardware specific item, it belongs in some internal Nokia team's issue tracker of choice.

Or, even worse, bug in component X, from a previous sw release is obsoleted by the fact that component X is going to be dropped/replaced but that is not public yet. What should we do?
Now this one's actually easy. But it requires a mindshift: Bugzilla's not just for bugs in Nokia's shipping devices, but for bugs in (all versions of) Maemo.

What if the bug is in a component which is still in use in Mer? Or a Hacker Edition? The bug still affects anyone with a 770 or N8x0 who won't (probably) have the option of upgrading to a Nokia-sponsored version of Maemo 5.

The bug should remain open. Anyone can fix it in the existing component (if it's open source) and resolve it themselves.

Especially considering the tight schedules we are already required to cope with, I am not going to ask the people working for me to take the extra effort of self censor themselves while trying to do PR with the community and simultaneously not ruining the marketing strategy.

It's not their job and I don't see why they should take this unnecessary risk upon themselves.
Then expect more griping. I fully understand your position and the limitations that it brings, and I really appreciate the involvement you (and others like Eero, Roope, Quim, timeless and many more) have in the Maemo Community. But Nokia may be successful, and the Maemo-device product line(s) may be comparitively successful; but in no way are Nokia going to be fully taking advantage of the legions of people who are working for free on improving this platform to scratch their own itches.

Once we can speak freely about everything, we'll try to do it.
You think that day'll come? Seems unlikely given what you've said above and that there'll always be hardware features which are confidential for reasons of commercial competitiveness.
__________________
Andrew Flegg -- mailto:andrew@bleb.org | http://www.bleb.org
 

The Following 4 Users Say Thank You to Jaffa For This Useful Post: