From Fedora Project Wiki
< Features
No edit summary |
(→Owner) |
||
| (7 intermediate revisions by 2 users not shown) | |||
| Line 14: | Line 14: | ||
<!-- Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or technical issues need to be resolved--> | <!-- Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or technical issues need to be resolved--> | ||
* Email: crash-catcher@lists.fedorahosted.org | |||
* Email: jmoskovc@redhat.com | * Email: jmoskovc@redhat.com | ||
== Current status == | == Current status == | ||
* Targeted release: [[Releases/16 | Fedora 16 ]] | * Targeted release: [[Releases/16 | Fedora 16 ]] | ||
* Last updated: 2011- | * Last updated: 2011-08-09 | ||
* Percentage of completion: | * Percentage of completion: 100% | ||
<!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. --> | <!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. --> | ||
| Line 34: | Line 35: | ||
* create a libreport package and add it to Fedora - '''DONE''' | * create a libreport package and add it to Fedora - '''DONE''' | ||
* create a python bindings for libreport - '''DONE''' | * create a python bindings for libreport - '''DONE''' | ||
* package the python bindings in Fedora - ''' | * package the python bindings in Fedora - '''DONE''' | ||
== How To Test == | == How To Test == | ||
=== 1. Install the following packages === | === 1. Install the following packages === | ||
* libreport | * libreport | ||
| Line 73: | Line 73: | ||
== Comments and Discussion == | == Comments and Discussion == | ||
* See [[Talk:Features/ | * See [[Talk:Features/Unified_Problem_Reporting_UI]] | ||
* or crash-catcher@lists.fedorahosted.org | * or crash-catcher@lists.fedorahosted.org | ||
== Release Notes == | |||
<!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ --> | |||
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release. --> | |||
[[Category: | * Fedora 16 brings the unified user interface for reporting problem from tools using ether python-meh or the python report library | ||
[[Category:FeatureAcceptedF16]] | |||
<!-- When your feature page is completed and ready for review --> | <!-- When your feature page is completed and ready for review --> | ||
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler --> | <!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler --> | ||
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete--> | <!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete--> | ||
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process --> | <!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process --> | ||
Latest revision as of 19:25, 15 August 2011
Features/Unified_Problem_Reporting_UI
Summary
Unify the UI for all problem reporting programs (mechanisms) in Fedora to improve the user experience by confronting them only one UI when reporting a problem.
Owner
- Name: Jiri Moskovcak
- Email: crash-catcher@lists.fedorahosted.org
- Email: jmoskovc@redhat.com
Current status
- Targeted release: Fedora 16
- Last updated: 2011-08-09
- Percentage of completion: 100%
Detailed Description
The new reporting library will provide the same API as did the old backend (concerns only python programs - Anaconda, setroubleshoot, python-meh) so the change should be transparent without any change in the code. The only change (not required to make it work) would be to change the spec file to require the new library instead of the old one.
Benefit to Fedora
Unified user interface makes it easier for users to use it. Unifying the reporting backend will also mean that the config data is shared and users have to setup their credentials (like bugzilla name/password) only once.
Scope
- create a bug reporting framework extensible by plugins by splitting the ABRT code - DONE
- create a libreport package and add it to Fedora - DONE
- create a python bindings for libreport - DONE
- package the python bindings in Fedora - DONE
How To Test
1. Install the following packages
- libreport
- libreport-gtk
- libreport-python (this one should obsolete the old report package)
- libreport-plugin-bugzilla (reporter plugin to create tickets in Fedora bugzilla)
2. Try to report a problem
- Anaconda crash
- SELinux AVC
- crash detected by ABRT
3. Expected results
- if the bug is new then a new ticket should be created in bz
- if the bug was reported it should let user know it found a duplice
User Experience
The bug reporting UI will change for:
- Anaconda uncaught exceptions
- setroubleshoot reports
- firstboot uncaught exceptions
Dependencies
- Anaconda
- python-meh
- firstboot
- setroubleshoot
Contingency Plan
None necessary, revert to previous release behaviour.
Documentation
- Documents describing detailed configuration can be found here
Comments and Discussion
- See Talk:Features/Unified_Problem_Reporting_UI
- or crash-catcher@lists.fedorahosted.org
Release Notes
- Fedora 16 brings the unified user interface for reporting problem from tools using ether python-meh or the python report library