Talk:Task:3rd party bug tracking in

[edit] "Community" instead of "Garage" + Website

Now there is a "Garage" item in the Classification at Proposing to rename it to "Community" and adding there the Website product. Or have "" as a separate entry in the classification, since it has and will have less and less to do with the official software offering by Nokia.--qgil 11:11, 19 July 2008 (UTC)

In fact, after going throough the bugs in Website it is clear that we need to make an own product for Documentation (the official, maintained by Nokia) and put it inside "Maemo Software". The rest of Website can go then under "Community".--qgil 14:58, 19 July 2008 (UTC)
Yes, timeless and I were discussing this, we were thinking something along the lines of Maemo Software, Nokia, Garage, Website. Part of the problem with lumping Website in with Community is that it will be increasingly difficult to get to the Website products in the Community classification as the number of Garage projects tracking bugs in Bugzilla increases. Personally, I think it's a good idea to separate the relatively-less-important Garage projects from the more important Website stuff. —GeneralAntilles 20:20, 19 July 2008 (UTC)

[edit] Bug tracking future plan

Moved from 2010 Agenda

  • It's unclear where to report problems about packages found in the application catalog. A single bug tracker is needed, or at least a catalog that would redirect the user to the appropriate tracker from a common start page. Or we could set up a "maemo" distribution on, which would let us integrate with the bug trackers of individual packages.
Nokia is open to discuss any possibility of integration of with third parties i.e. ITt and also using any external service i.e. We can commit to overall plans for the 100 Days exercise but not on execution. Having a better and common understabnding of how this steps would fall in the 2010 Agenda would definitely help to see what are the right first steps.--qgil 07:45, 2 June 2008 (UTC)