ubuntu-bugcontrol team mailing list archive

[Jeremy Foshee <jeremyfoshee@xxxxxxxxx>]

responses inline :)

On Mon, Oct 5, 2009 at 12:41 PM, Brian Murray <brian@xxxxxxxxxx> wrote:
> Thanks for your interest in joining the Ubuntu Bug Control team.  As
> part of the application process we need to ensure that the following
> criteria are met.
>
> 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 do indeed. Having the Support Engineering background that I do, I
have dealt with many bug /issue reporters and have run the gamut from
polite to downright nasty in their responses. I have no problem being
polite to those types of people. I have signed the CoC.
>
> 2) Have you read Bugs/HowToTriage[0], Bugs/Assignment[1] and
> Bugs/Importance[2] at wiki.ubuntu.com?  Do you have any questions about
> that documentation?

I have read them and, as usually is the case, I have flagged them for
future reference. I don't have any questions currently, but I also
have no problem asking those questions as they arise.

>
> 3) What sensitive data should you look for in a private Apport crash
> report bug before making it public?  See Bugs/HowToTriage[1] for more
> information.

Well, there could be any kind of potentially sensitive data passed in
as function call arguments. Most of the time this is password
information or static IP and in some cases internal hostname. I've not
yet had to deal with this, but I have the information should I ever
need it.
>
> 4) Is there a particular package or group of packages that you are
> interested in helping out with?

Lately I have been dealing exclusively with kernel bugs. I am still
fresh in the process of understanding all aspects of kernel bug
triage, but I am lucky in that I have a great resource in Leann O.,
Steve Conklin and occasionally Pete Graner to ask questions of.
>
> 5) We also need to see a list of 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 you would give
> it after becoming a member of Ubuntu Bug Control.  Please use urls in
> your list of bugs so we can more easily find them.

https://bugs.launchpad.net/bugs/430694 I didn't do much to this due to
it being a high importance case. I simply brought it to the attention
of PGraner and he set the priority, etc.
https://bugs.launchpad.net/bugs/27287  This case was very confusing as
there seemed to be irrelevant information in the bug. I asked for some
clarification and I believe we have the issue back on track.
https://bugs.launchpad.net/bugs/441162 This bug was answered based on
information I got again from PGraner. I have a request in for
information on the feasability/necessity of a bug for detecting
encrypted home and reacting appropriately.
https://bugs.launchpad.net/bugs/441485 The request in this bug was due
to information from the kernel team. It appears we already get the
information we requested, but I have not heard yet if that is in fact
the case.
https://bugs.launchpad.net/bugs/308820 This is an old bug that needed
an information refresh

I'm absolutely certain that I can find you a ton more of these. The
biggest issue I have is not having the ability to set priority or some
of the other statuses. I'm hoping that membership in this team will
enable me to help with the tremendous backlog of kernel bugs in the
wild today.

>
> [0] https://wiki.ubuntu.com/Bugs/HowToTriage
> [1] https://wiki.ubuntu.com/Bugs/Assignment
> [2] https://wiki.ubuntu.com/Bugs/Importance
>
> Thanks again for your interest in joining the team and we look forward
> to hearing from you.

Thank you for your consideration of me for inclusion in this team. :)

-JFo

>
> Sincerely,
> --
> Brian Murray                                                 @ubuntu.com
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
>
> iEYEARECAAYFAkrKIcQACgkQDTAwc5ER+zVYbACgjPECQsbMjStG/vP6tCTojlmp
> l20AoJnka8AO4BjLoJT2fHD66ssGj4uU
> =2BlO
> -----END PGP SIGNATURE-----
>
>