← Back to team overview

ubuntu-bugcontrol team mailing list archive

Bug Control Team Application for Christopher M. Penalver

 

As per Brian Murray's E-Mail below I am applying for Bug Control.



1. Do you promise to be polite to bug reporters even if they are rude to you
or Ubuntu? Yes. Have you signed the Ubuntu Code of Conduct? Yes.



2. Have you read Bugs/HowToTriage? Yes. Bugs/Assignment? Yes. Bugs/Status?
Yes. Bugs/Importance? Yes. Do you have any questions about that documentation?
No.



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)?



A reporter's personal information such as passwords, bank accounts, encryption
keys or other personal data that does not appear related. As well, delete
sensitive data files (ex. CoreDump.gz, Stacktrace.txt).



4. Is there a particular package or group of packages that you are interested
in helping out with? At this time, Openoffice.org and LibreOffice.



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 bugs. For all
the bugs in the list, please indicate what importance (and explain the
reasoning) you would give it after becoming a member of the Ubuntu Bug Control
team. Please use urls in your list of bugs.



1)
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/505188
Importance: Medium
Importance Rationale: A bug that has a moderate impact on a core application.
Triage Rationale: Reproducible in Natty LO, not an issue of security, data
loss, or impacting a high number of users.

2)
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/522414
Importance: Medium
Importance Rationale: A bug that has a moderate impact on a core application.
Triage Rationale: I marked as Fixed Released as it is fixed in LibreOffice
under Natty. It is not SRU eligible because it is not an issue of security,
data loss, or impacting a high number of users. It does not fit the backport
eligible criteria well because the issue is fixed via the LibreOffice PPA in
Lucid and Maverick, and reporter's release is going EoL in less than a month.



3)
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/618024
Importance: Medium
Importance Rationale: A bug that has a moderate impact on a core application.
Triage Rationale: I marked as Fixed Released for openoffice.org as it is fixed
in LibreOffice under Natty. It is not SRU eligible because it is not an issue
of security, data loss, or impacting a high number of users. It does not fit
the backport eligible criteria well because the issue was fixed as per the
reporter in OOo Maverick, and the LibreOffice PPA is available in Lucid and
Maverick.


4)
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/646157
Importance: Medium
Importance Rationale: A bug that has a moderate impact on a core application.
Triage Rationale: Reproducible in Natty LO, not an issue of security, data
loss, or impacting a high number of users.

5)
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/668079
Importance: Medium
Importance Rationale: A bug that has a moderate impact on a core application.
Triage Rationale: Reproducible in Natty LO not an issue of security, data
loss, or impacting a high number of user.

Return-Path: <bounces@xxxxxxxxxxxxx>

Received: from mail-mx1.its.albany.edu (mail-fe1.its.albany.edu [169.226.1.167])

     by mail-be1.its.albany.edu (Cyrus v2.3.12p2) with LMTPA;

     Wed, 02 Mar 2011 18:39:19 -0500

X-Sieve: CMU Sieve 2.3

Received: from adelie.canonical.com (adelie.canonical.com [91.189.90.139])

     by mail-mx1.its.albany.edu (8.14.3/8.14.3) with ESMTP id p22NdDxn025266

     for <cp9650@xxxxxxxxxx>; Wed, 2 Mar 2011 18:39:18 -0500 (EST)

Received: from palladium.canonical.com ([91.189.90.221])

     by adelie.canonical.com with esmtp (Exim 4.71 #1 (Debian))

     id 1PuvdQ-00062j-MA

     for <cp9650@xxxxxxxxxx>; Wed, 02 Mar 2011 23:39:12 +0000

Received: from palladium.canonical.com (localhost [127.0.0.1])

     by palladium.canonical.com (Postfix) with ESMTP id A1C82590070

     for <cp9650@xxxxxxxxxx>; Wed, 2 Mar 2011 23:39:12 +0000 (UTC)

Content-Type: text/plain; charset="us-ascii"

MIME-Version: 1.0

Content-Transfer-Encoding: 7bit

From: Brian Murray <brian@xxxxxxxxxx>

To: "Christopher M. Penalver" <cp9650@xxxxxxxxxx>

Subject: Your Bug Work

Message-ID: <20110302233912.11658.69167.launchpad@xxxxxxxxxxxxxxxxxxxxxxx>

X-Launchpad-Message-Rationale: ContactViaWeb user

Date: Wed, 02 Mar 2011 23:39:12 -0000

Reply-To: Brian Murray <brian@xxxxxxxxxx>

Sender: bounces@xxxxxxxxxxxxx

Errors-To: bounces@xxxxxxxxxxxxx

X-Generated-By: Launchpad (canonical.com); Revision="12509";

     Instance="launchpad-lazr.conf"

X-Launchpad-Hash: 963d8b01114a3cfbe9da58e374f67b72a6794e75

X-Scanned-By: MIMEDefang 2.65 on 169.226.1.163



------------------------------ Original Message ------------------------------

Subject: Your Bug Work

From:    "Brian Murray" <brian@xxxxxxxxxx>

Date:    Wed, March 2, 2011 6:39 pm

To:      "Christopher M. Penalver" <cp9650@xxxxxxxxxx>

------------------------------------------------------------------------------



I've noticed you've been doing a lot of great working triaging bug

reports and was wondering if you had considered joining the Ubuntu Bug

Control team.  I think you'd be a great addition!



https://wiki.ubuntu.com/UbuntuBugControl



Sincerely,



Brian Murray

-- 

This message was sent from Launchpad by

Brian Murray (https://launchpad.net/~brian-murray)

using the "Contact this user" link on your profile page

(https://launchpad.net/~penalvch).

For more information see

https://help.launchpad.net/YourAccount/ContactingPeople

-- 
Christopher M. Penalver
E-Mail: cp9650@xxxxxxxxxx
MCSE:Security, MCSA, MCDST, MCP, Security+, Network+, A+, NSSP

This E-Mail was sent via a laptop using Ubuntu, Linux for human beings.
www.ubuntu.com
https://launchpad.net/~penalvch



Follow ups