← Back to team overview

ubuntu-bugcontrol team mailing list archive

Application to join ubuntu-bugcontrol

 

Hi,

I would like to apply for access to ubuntu-bugcontrol on Launchpad.

I am a Debian Developer, and I also work at MSFT, so often I have to
prepare fixes that go through the SRU process, and this requires
setting the per-release bug subtasks as per the required process. I
have to ask an Ubuntu dev to do this for me, which wastes their time
and leads to delays. Having ubuntu-bugcontrol access means I can do
this directly without having to rely on Canonical's time (mostly
cpaelzer's!).

My Launchpad: https://launchpad.net/~bluca

- 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

- Have you read Bugs/Triage, Bugs/Assignment, Bugs/Status and
Bugs/Importance? Do you have any questions about that documentation?

I have read it, no question at this stage.

- What sensitive data should you look for in a private Apport crash
report bug before making it public? See Bugs/Triage for more
information.

Things such as PII (Personal Identifiable Information), passwords,
keys, addresses, and anything else that belongs to a specific user or
service and can be sensitive, valuable, private, privileged or any
combination thereof.

- Is there a particular package or group of packages that you are
interested in helping out with?

Packages that I maintain in Debian and that are synced automatically
(ie: don't have a "permanent" Ubuntu fork that is looked at by a
specific team):
https://qa.debian.org/developer.php?login=bluca&comaint=yes

- 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.

CVEs reported, with patches, as upstream maintainer:

https://bugs.launchpad.net/debian/+source/zeromq3/+bug/1811531
https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1835213

Bug that I solved upstream, backported to debian and reported to
Ubuntu: 
https://bugs.launchpad.net/debian/+source/evolution-ews/+bug/1838463

Bugs that resulted in SRUs for Focal:
https://bugs.launchpad.net/debian/+source/azure-cli/+bug/1897586
https://bugs.launchpad.net/ubuntu/+source/azure-cli/+bug/1866612

Bugs that I triaged as MSFT employee and provided the fixes for,
currently waiting in the SRU queue for approval:

https://bugs.launchpad.net/ubuntu/+source/tpm2-openssl/+bug/1970999
https://bugs.launchpad.net/ubuntu/+source/tpm2-openssl/+bug/1971000
https://bugs.launchpad.net/ubuntu/+source/tpm2-openssl/+bug/1996498

Feature requests, wishlist, backport requests and such:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961771
https://bugs.launchpad.net/ubuntu/+bug/1959901
https://bugs.launchpad.net/ubuntu/+source/tpm2-tss-engine/+bug/1951314
https://bugs.launchpad.net/ubuntu/+source/sdbus-cpp/+bug/1916068
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1961610

Thanks!

-- 
Kind regards,
Luca Boccassi

Attachment: signature.asc
Description: This is a digitally signed message part


Follow ups