If a bug in code or in translations exists that comes from an "upstream" project and that was not changed in ("downstream") MeeGo it is common practice to forward this bug report to the corresponding upstream bugtracker.
This makes upstream developers / translators become aware of issues (that were found in MeeGo but affect any other downstream projects too) so they can get fixed upstream. Patches are of course also welcome to be attached in an upstream report.
Fixing issues upstream reduces the efforts of maintaining downstream patches. It is welcome to query first in the upstream bugtracker for a potentially already existing report covering the issue.
In case an upstream bug has been filed or has been found, add the URL to the field "See Also: Add Bug URLs:" in the report in bugs.meego.com, and vice versa if possible. CC yourself to the upstream bug report to keep track and update the report in bugs.meego.com once it is fixed upstream.
|Project||Bugtracker URL||Product for Translation Issues|
|Banshee, librest, libsocialweb||Gnome||https://bugzilla.gnome.org/||L10N|
|WebKit, WebCore, CoreJS||WebKit||https://bugs.webkit.org/|
If the component you're looking for isn't listed here, please add it, possible places to find further bug trackers include: