maemo.org Bugzilla – Bug 3562
Reorganizing components in Bugzilla
Last modified: 2008-12-29 18:43:16 UTC
You need to
before you can comment on or make changes to this bug.
While Connectivity or Development Platform are pretty clear, products like
* System Software
* System Management or
have a bit of inconsistency in their components (and maybe even their scope).
Quoting Quim from
"This is not only poor usability for the bug reporters. It also makes life
harder for Nokia developers to track where are the reports that affect to their
work. Specially if you consider that developers work on teams, and many times
teams are mapped to certain products and components. It is easier for Team A to
know that they have to follow Product A and forget safely about the rest."
We/I'm going to compare the structures for the mentioned products in Maemo
Bugzilla and the existing structure of Nokia development teams for Sprint4.
* Desktop -> User Interaction vs UI Specification
* Documentation vs. Website -> Documentation
Quoting an email by Quim:
>Documentation is also a component under Website. All the
>developer documentation should go there under Website.
>- Help/tip texts probably go better under the product affected (i.e.
>Connectivity) where the team in charge can look at it and move
>the changes forward.
>- Problems with the User Guide...
>If we want to have these bugs in the external
>bugzilla then it would be probably better to rename
>"Documentation" to "User Guide", and have components for every
Sprint5 tasks => setting Priority to High
Please comment on the proposal at
Also, the Documentation component under maemo.org should move to Development
Platform since the bugs there refer to official developer documentation and
this falls out of the responsibility of the community.
(In reply to comment #3)
> Also, the Documentation component under maemo.org should move to Development
> Platform since the bugs there refer to official developer documentation and
> this falls out of the responsibility of the community.
Will do this today, though it's complicated and can't be easily done because of
different versioning and TM systems.
Just posted my draft now at
It also keeps the seperation between core and UI Apps and I think it should
provide us better scalibility and extensability (if that word exists) compared
to now. Some things still need some improvements (e.g. better splitting of
several Multimedia components).
Feedback very welcome.
Might want to disable sending bugmail when moving thousands of bugs.
Note to myself: /template/en/default/global/banner.html.tmpl can be used to
display a global banner announcing this in advance.
Basically done by today's reorg.
Only working on a very few flaws and corner-cases.
Will probably close this report in a few days.