(Created page with ' == Introduction == The Fedora Desktop Bugzilla Client is a project that aims to provide a very easy and simple interface for end users to file bug reports. We aim to built some...') |
No edit summary |
||
| Line 1: | Line 1: | ||
== Introduction == | == Introduction == | ||
| Line 17: | Line 16: | ||
The basic assumption is that the user is filing the bug report on the system having a problem and we will fallback to a simple wizard otherwise. For any bug report, collect the Fedora version by reading /etc/fedora-release and the specific component version. fetch the list of components from bugzilla based on the Fedora version and we will also deduce the source rpm name for any file in the installed system. | The basic assumption is that the user is filing the bug report on the system having a problem and we will fallback to a simple wizard otherwise. For any bug report, collect the Fedora version by reading /etc/fedora-release and the specific component version. fetch the list of components from bugzilla based on the Fedora version and we will also deduce the source rpm name for any file in the installed system. | ||
==== Specific Components ==== | ==== Specific Components ==== | ||
| Line 29: | Line 24: | ||
FIXME: Figure out what components require which information. | FIXME: Figure out what components require which information. | ||
=== Mockups === | |||
We need help with someone from the design team to draw mockups for the PyGTK application. | |||
=== Current Status === | === Current Status === | ||
We have some code written. A lot more needs to be done | We have some code written. A lot more needs to be done | ||
Revision as of 13:39, 17 August 2009
Introduction
The Fedora Desktop Bugzilla Client is a project that aims to provide a very easy and simple interface for end users to file bug reports. We aim to built some intelligence into the client. We will collect the Fedora version and component version information, hardware details, log output, SELinux status and other details depending on the component the user chooses to file a bug report against.
Name of the application
Candidates:
- bugme
Suggest your own here
What's happening
August 17, 20009: Rahul Sundaram and Kushal Das is brainstorming. Kushal Das is writing a python script based on python-bugzilla that will be provide the actual functionality. Investigating using python bindings for newt or ncurses for a command line app and intend to write a PyGTK application as well.
The basic assumption is that the user is filing the bug report on the system having a problem and we will fallback to a simple wizard otherwise. For any bug report, collect the Fedora version by reading /etc/fedora-release and the specific component version. fetch the list of components from bugzilla based on the Fedora version and we will also deduce the source rpm name for any file in the installed system.
Specific Components
For yum, get yum --version information. Based on discussions with Seth Vidal this is the most relevant information.
For Xorg, get /etc/X11/xorg.conf if it exists and /var/log/xorg.log
FIXME: Figure out what components require which information.
Mockups
We need help with someone from the design team to draw mockups for the PyGTK application.
Current Status
We have some code written. A lot more needs to be done