ubuntu-bugcontrol team mailing list archive
Mailing list archive
Re: Fwd: Application
On 03/07/2011 03:08 PM, RedSingularity wrote:
> On 03/07/2011 08:54 AM, C de-Avillez wrote:
>> On 03/07/2011 07:31 AM, C de-Avillez wrote:
>>> Forwarding for RedSingularity, he could not email BugControl.
>>> -------- Original Message --------
>>> Subject: Application
>>> Date: Mon, 07 Mar 2011 00:12:11 -0500
>>> From: RedSingularity<RedSingularity@xxxxxxx>
>>> To: hggdh2@xxxxxxxxxx
>>> RedSingularity's (Tim's) Application,
>>> 1) Do you promise to be polite to bug reporters even if they are
>>> rude to you or Ubuntu? Have you signed the Ubuntu Code of Conduct?
>>> -YES / YES
>>> 2) Have you read Bugs/HowToTriage
>>> <https://wiki.ubuntu.com/Bugs/HowToTriage>, Bugs/Assignment
>>> <https://wiki.ubuntu.com/Bugs/Assignment>, Bugs/Status
>>> <https://wiki.ubuntu.com/Bugs/Status> and Bugs/Importance
>>> <https://wiki.ubuntu.com/Bugs/Importance>? Do you have any
>>> questions about that documentation?
>>> -YES / NO
>>> 3) What sensitive data should you look for in a private Apport
>>> crash report bug before making it public?
>>> -Sensitive data to look for in a apport crash would be found in
>>> stacktrace.txt files. Things such as passwords, bank account
>>> numbers, CSS keys, user names, server names, etc may be located in
>> And, please do not forget, coredumps, configuration files, etc.
>>> 4) Is there a particular package or group of packages that you are
>>> interested in helping out with?
>>> -I work on any package I feel comfortable with. Most of my time
>>> goes to the update-manager package though. I have been working with
>>> that for many months.
>>> 5) Please list five or more bugs which you have triaged and include
>>> an explanation of your Triage. Please note that these bugs should be
>>> representative of your very best work and they should demonstrate
>>> your understanding of the triage process and how to properly handle
>>> Importance for each one has been discussed with -control
>>> members before being assigned.
>> Unfortunately, any other bug-control member not involved in these
>> discussions will have no idea of *how* you reached the conclusion.
>> Please resend with your rationale for the importances.
> Importance: "Medium", This bug affected all FRESH natty installs and it
> was a core-app. The workaround was simple enough though therefore not
> Importance: "Low", It only effected people with the mentioned intel VGA
> chipset WITH compiz enabled as the window manager. Workaround was as
> simple as using the default manager Metacity.
> Importance: "Low", It only effected the group of people using a dual
> monitor set up. The issue did not effect the usage of thunderbird in
> any way. It was more of a "cosmetic" issue.
> Importance: "Low", The problem with the restart button was a nuisance
> but nothing more. Did not effect the proper working of the
> update-manager. And in order to reproduce you need to start
> update-manager as root which is not done normally anyway.
> Importance: "Wishlist", obviously this was a usability improvement idea
> for update-manager so it got the wishlist stamp.
> Importance: "Wishlist", another usability improvement idea that was
> EASY to implement. Bitesize. (I looked at the source code of
> update-manager for this one to be sure)
> Importance: "Wishlist", And finally another idea to improve the users
> experience with ubuntu. Implimintation requires, again, a few lines of
Very nice work, RedSingularity. I'm happy to endorse your application.