This page collects statements of advocacy for
Richard Laager <firstname.lastname@example.org>
to become 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
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
public mailing list
requirement has been approved by Housekeeping Robot <email@example.com>
4 months, 4 weeks ago.
process has been closed by johns on
2020-05-02: no further modifications are possible.
- if possible, have more than 1 advocate
Dear Debian Front Desk/nm.debian.org,
I support Richard Laager <firstname.lastname@example.org>'s request to become Debian
Richard and I have worked together on the gbonds package since March of
2007, the up-imapproxy package since December of 2016, and most recently
(and more intensively) on the ntpsec package since February of 2018.
For these packages, Richard has handled basically 100% of the packaging
and BTS/triage work, while I have acted as sponsor and we have conferred
on questions and approaches to maintaining software. I am confident in
Richard's capabilities, skills as a developer, and commitment to Debian
and Free Software.
I have collaborated with Richard Laager <email@example.com> (key
D4EB7D94E78E4EE8ECE07F94F8796199C04586CE) for almost 13 years, and I
know Richard Laager can be trusted to be a full member of Debian, and
have unsupervised, unrestricted upload rights, right now.
Note that the text above is quite similar to my advocacy statement for
Richard's DM application last year . Nothing has changed in my
estimation of Richard's capabilities since that time. I am glad to see
this application move forward. Please feel free to reach out to me if I
can help further with the process.
tony mancill <firstname.lastname@example.org>
Signed with key E50A FD55 ADD2 7AAB 9716 3A8B 21D2 0589 974B 3E96
||New statement received, the requirement seems satisfied
||Added a new statement