ubuntu-bugcontrol team mailing list archive
-
ubuntu-bugcontrol team
-
Mailing list archive
-
Message #01140
BugControl Application
Ubuntu Bug Control Team,
Below is my application for inclusion in the Bug Control Team. Hopefully it
will meet your criterion. However, if it does not, then please let me know
how I can improve my triaging skills.
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?
Response: Yes I do, Bug #517777 is evidence to this pledge. Yes, I have
signed the CoC.
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?
Response: Yes, I have read over each page several times and have become very
familiar with their contents. I do not have any questions.
3. What sensitive data should you look for in a private Apport crash report
bug before making it public?
Response: Coredump.gz files should be removed (if they are not needed) from
reports before they are made public. If there is no Stacktrace.txt file,
then the Coredump.gz file should remain on the report, the report should
remain private, and Martin Pitt should be contacted via IRC. The
Stacktrace.txt file (if there is one) should also be examined for personal
information, such as account numbers, passwords, usernames, etc. before a
report is made public. If the Stacktrace.txt file is complete and does not
contain any personal information, then the Coredump.gz file can be removed
and the report can be made public.
4. Is there a particular package or group of packages that you are
interested in helping out with?
Response: For now, I am interested in helping out with Firefox reports.
Micah Gersten is currently helping me learn how to approach these reports.
Once I have a firm understanding of how the Mozilla Team works, I would like
to spread to working on reports for all Mozilla applications.
5. Examples of triaging skill. Below are six examples of my ability to
handle bug reports. The importance of each report was requested by myself on
#ubuntu-bugs, and a Bug Control member changed the report for me.
Bug #485352
Bug #523236
Bug #517777
Bug #515725
Bug #516154
Bug #514782
These bugs are in no particular order, and I have selected these six in
order to show my experience with different aspects of triaging (i.e., filing
upstream, translation bugs, testing on development release, dealing with a
rude reporter, etc.)
My mentor is Pedro (pedro_), however I have had difficulty in keeping in
contact with him, so I am not sure how much he has been following me. Others
who have helped me most on #ubuntu-bugs include hggdh, persia, and micahg.
I really enjoy working with Bug Squad and Bug Control members, and I look
forward to becoming a more integral part of the team!
Thank you for taking the time to review this application,
Draycen DeCator (ddecator)
Follow ups