ubuntu-bugcontrol team mailing list archive

[C de-Avillez <hggdh2@xxxxxxxxxx>]

On Fri, 2 Dec 2016 10:42:56 -0500
Eric Desrochers <eric.desrochers@xxxxxxxxxxxxx> wrote:

> I, Eric Desrochers, apply for membership in the ~ubuntu-bugcontrol
> team.
> 
> https://launchpad.net/~slashd <https://launchpad.net/%7Ekamalmostafa>

#########################################################^^^^^^^^^^^^^

> https://wiki.ubuntu.com/slashd <https://wiki.ubuntu.com/KamalMostafa>

#########################################################^^^^^^^^^^^^^

> IRC: slashd

Huh? Are you Eric or Kamal? :-)

Correct links:

LP:   https://launchpad.net/~slashd
Wiki: https://wiki.ubuntu.com/slashd


> 
> Thanks for considering me! _*
> 
> Application*_
> 
> ** 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, I will always be polite to bug reporters and I did sign the
> Ubuntu Code of Conduct a few years ago. *
> *** Have you read Bugs/Triage, Bugs/Assignment, Bugs/Status and
> Bugs/Importance? Do you have any questions about that documentation?*
> 
> No questions it is pretty clear and well detailed.
> *
> *** What sensitive data should you look for in a private Apport crash
> report bug before making it public? See Bugs/Triage for more
> information.*
> 
> Coredump.gz is a memory dump accessible by the program that crashed.
> Coredumps contains all sorts of private data to be mined. Never mark
> a bug containing a Coredump.gz attachment as public.
> 
> Stacktrace.txt (retraced) and ThreadStacktrace.txt (retraced)) could
> also have sensitive data passed as function arguments Examples are
> passwords, things that look like bank account numbers, CSS keys, user
> names, server names, etc. * *** Is there a particular package or
> group of packages that you are interested in helping out with?*
> 
> I'm amenable to help on all packages.
> *
> *** Please list five or more bug reports which you have triaged and
> include an explanation of your decisions. 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 bugs. For all the bugs in the list, please indicate
> what importance you would give it and explain the reasoning. Please
> use urls in your list of bugs.*
> 

<snip/>

Most of the bugs listed show you working as a developer, not as a
triager. What we are trying to determine here is if you understand the
triaging process (not the resolution process).

Nevertheless, your actions (apart from the comment above) show you
correctly changing status and priorities; additionally there is some
triaging work intermixed as well.

As such, I am +1.

Cheers,

..C..

Attachment: pgpHHPIj8PNTn.pgp
Description: OpenPGP digital signature