ubuntu-bugcontrol team mailing list archive

[Philip Muskovac <yofel@xxxxxxx>]

On 08/30/2010 11:45 PM, Mohammed Amine IL Idrissi wrote:
> 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?
> I signed the Ubuntu Code of Conduct, thus requiring me to be polite
> and respectful to any person.
> 
> 2. Have you read Bugs/HowToTriage, Bugs/Assignment, Bugs/Status and
> Bugs/Importance? Do you have any questions about that documentation?
> I read all of these pages, and understood them well without any
> questions pending.
> 
> 3. What sensitive data should you look for in a private Apport crash
> report bug before making it public? See Bugs/HowToTriage for more
> information.
> I should look for login passwords, confidential photos...
> I'm not sure I understood that question well, since only
> ubuntu-bugcontrol has access to private bugs ; newcomers can't "test"
> if they are capable of looking into private reports. But maybe I
> didn't understand this question, so could you reformulate?

Also make sure that there is no coredump attached anymore and if yes
check why.
see https://wiki.ubuntu.com/Bugs/HowToTriage#Apport%20crash%20reports

> 
> 4. Is there a particular package or group of packages that you are
> interested in helping out with?
> Not really, I can triage everything without much trouble ; however,
> I'm inclined toward handling desktop bugs.
> 
> 5. Please list five or more bugs which you have triaged. These bugs
> should demonstrate your understanding of the triage process and how to
> properly handle bugs. If there is a bug in your list that does not
> have an importance indicate what importance (and explain the
> reasoning) you would give it after becoming a member of Ubuntu Bug
> Control. Please use urls in your list of bugs.
>  * https://bugs.edge.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/503041
> : This was an old bug not assigned to any package ; howerver, I
> confirmed it under Maverick, provided the required information via
> apport-collect, and reported it upstream.
>  * https://bugs.edge.launchpad.net/ubuntu/+source/vifm/+bug/615563 :
> This bug was caused because Debian had modified the binary name
> because of conflicts with another package, but forgot to update it in
> one location. The patch supplied was forwarded to Debian, and a
> debdiff was attached. (I realize I should had subscribed
> ubuntu-sponsors, but I wasn't aware of this at the time. Sorry for
> that)
>  * https://bugs.edge.launchpad.net/ubuntu/+source/adduser/+bug/613204
> : Again, patch was forwarded to upstream (which is Debian in this
> case). No response from upstream was heard until now.
>  * https://bugs.edge.launchpad.net/ubuntu/+source/rox/+bug/615490 :
> The attached patch was forwarded upstream, and accepted there.
>  * https://bugs.edge.launchpad.net/ubuntu/+source/update-manager/+bug/387247:
> Not much to say here.

Good work in general, and considering your daily work in #ubuntu-bugs +1
from me.