Advocate

This page collects statements of advocacy for Timothy Pearson <tpearson@raptorengineering.com> to become a Debian Developer, uploading.

You must be logged in to submit a statement of advocacy. See the Single Sign-On page for details and https://sso.debian.org/ to obtain a suitable client certificate.

See here for advocacy tips, and here for some more rationale.

Please be verbose if you can. You may want to write the advocacy in a proper text editor and paste it in the form when you are happy with it.

Note: An email with your advocacy message will be sent to the debian-newmaint public mailing list.

This requirement has been approved by Housekeeping Robot <nm@debian.org> 1 year, 7 months ago.

This process has been closed by noodles on 2023-12-16: no further modifications are possible.

Potential problems

if possible, have more than 1 advocate

Signed statements

Statement

Uploaded by

Upload date

Actions

For nm.debian.org, at 2023-10-09:
I support Timothy Pearson <tpearson@raptorengineering.com>'s request to become
a Debian Developer, uploading.
I have worked with Timothy Pearson on chromium packaging for a year and a half
and I consider them as having sufficient technical competence.

Along with what I wrote in
<https://lists.debian.org/debian-newmaint/2023/01/msg00007.html> when I
advocated for Timothy to become a Debian Maintainer, Timothy has continued
helping me maintain the Chromium package in Debian. Since becoming a DM, he has
done a number of chromium uploads to unstable. He's also helped immensely
with preparing new major versions, which involves a lot of patch refreshing,
fixing new build errors, figuring out how to deal with upstream's generally
questionable behavior around tracking & advertising, dealing with brand new
bugs, etc.

One of the major reasons I've pushed him on becoming a proper DD is because
DMs cannot upload to security-master, and chromium has weekly security updates.
I'd like him to be able to upload security updates along with the other
chromium packaging work that he does. I expect that he'd also benefit the
project as well by giving him the ability to NMU or otherwise fix ppc64
bugs that he comes across.

I have personally worked with Timothy Pearson <tpearson@raptorengineering.com>
(key 6E58CA48BEAEF11C0345205EEC3C80BC57319B7E) for 18 months, and I know
Timothy Pearson can be trusted to be a full member of Debian, and have
unsupervised, unrestricted upload rights, right now.

Signed with key 5005 24F9 7D58 8932 23B3 5F6A 645D 0247 C36E 7637

dilinger

2023-10-09

[view raw]

Log

Date	Author	Action	Content	Public
2023-10-09 02:15	dilinger	add_statement	Added a new statement	yes
2023-10-09 02:15	nm@debian.org	req_approve	New statement received, the requirement seems satisfied	yes