maemo.org - Talk - View Single Post - maemo.org Bugzilla 2008 statistics (1)

	qgil	2009-01-09 , 17:22
	Posts: 3,105 \| Thanked: 11,088 times \| Joined on Jul 2007 @ Mountain View (CA, USA)	#19

Looking at these stats (thanks Andre!) I can only say that they are way better than anybody could have imagined exactly a year ago (thanks Bugsquad Team and many others for kicking the snowball!).

... and continuing. The long Fremantle release process will hopefully give us time to clean the bug database of dormant legacy. The current bugs will be tested against Fremantle and those relevant still not FIXED will be filed in the internal bugzilla against the Fremantle program, while still being in the development and bugfixing phases. Something that never had happened before.

Originally Posted by igor

Recently we have recieved permission to publish kernel code at a level that was not even imaginable before

I also call this progress. More steps without any precedent in Maemo (and Nokia?) will be done before any device is launched. It's not easy to set these precedents but I think they are solid ones. This is why Harmattan still will get more unprecedented steps, probably.

but there are still certain areas - which i cannot mention for obvious reasons - that are still considered to be a marketing advantage and therefore cannot be published.

(...)

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?

Untill Harmattan the platform layers are getting many changes that contain new signals about hardware, technology selections and consumer features. This creates many frictions between open development and marketing/product management.

I wish (and I have moderate reasons to think) that once Harmattan is released the pace for open development will be simpler since the platform will be more consolidated and we hopefully will be able to disclose/launch new software features without the pressure of not unveiling features of the Device XXX to be launched. Like Symbian/S60 do nowadays, and I expect them to do even more going open source. Or like Qt did in the times of Trolltech and keeps doing in the times of Nokia.

From my point of view it would be much simpler if there was _one_ bugzilla system, open to everybody, where i could debate anything regardless of who might be seeing it.

The next stop of that train is open development for open source components, and this is the one where we need to focus now. I don't know if that train will ever lead to that single bugzilla but it's clear that without open development it doesn't even make sense.

But, coming to reality, I have already stated this several times internally, and the problem is that the people who enforce certain closedness are the same ones who also support the external bugzilla and ask developers for more partecipation.

Being in the product management team I know perfectly what you mean. Again, moving to open development is the best remedy for this, although not an automatic solution. The Fremanle pre-alpha release is a concrete step in the good direction and hopefully during the Fremantle release we can do a lot more progress solving those inconsistencies.

Once we can speak freely about everything, we'll try to do it.

This is a quest that needs to be done team by team, area by area. Platform+OSS goes first. Applications+Closed perhaps never gets there.

__________________
http://maemo.org/profile/view/qgil/ + http://qt-project.org

Quote & Reply |

The Following 2 Users Say Thank You to qgil For This Useful Post:
Stskeeps, timsamoff