Advocate
This page collects statements of advocacy for
Mark Hindley <mark@hindley.org.uk>
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>
4 years ago.
This
process has been closed by noodles on
2021-03-23: no further modifications are possible.
Signed statements
Statement |
Uploaded by |
Upload date |
Actions |
I support Mark Hindley <mark@hindley.org.uk>'s request to become Debian Developer, uploading.
I have worked with Mark Hindley over the last year on several issues related to elogind and other init systems issues and strongly support Mark's application to be a Debian Developer even though I don't think he has been a DM.
Mark has experience with Debian packaging through his work in Devuan and with elogind.
My experience with Mark included working with him on #934491 and #934132, bugs related to getting elogind into bullseye.
During that process, he:
* Discovered, escalated, and coordinated with apt maintainers to resolve a dependency resolver bug
* Worked to understand release team objections to elogind, and worked through every permutation of possible solutions that I and others was able to come up with, explaining the trade offs and confirming the initial approach. This involved everything from looking at upstream ABI and API decisions, to looking at various ways of handling packaging (dependencies vs diversions). He focused on actually trying to test results where possible
* Once the politics were dealt with, the package wasn't accepted because of a britney bug. He worked with the release team, put together a proposed patch to britney. This patch wasn't quite right, but was a great first attempt for someone jumping into an unfamiliar code base. He engaged constructively and got the problem resolved.
* In recent TC discussions Mark has focused on achievable goals and has focused on providing important information about the affected packages.
* Mark has also gotten sucked into the deeper aspects of Debian policy, and while he has not (too my knowledge) contributed to the policy process he has been able to understand some of the more complex aspects of init system policy.
In all my interactions with Mark, he has been constructive, and focused on the needs of users, even when he had every right to be frustrated and disappointed with the interactions of other members of our community.
We need people like Mark who can approach difficult issues and help solve the problems of our users rather than escalating tension.
Why am I willing to advocate for DD at this stage? Mark has
demonstrated an ability to work even when concerns cross package
boundaries or even involve complex parts of our infrastructure. He
has demonstrated excellent communication skills and ability to work through complex issues. In my mind, that's when you have clearly crossed into the DD realm rather than maintaining a few packages.
I have not sponsored Mark's packages; I'd recommend that Mark get an advocate that specifically focuses on packaging tasks and skills, or that the AM spend a bit more time focusing on that than usual because as an advocate I have not done so.
Signed with key 332D 4CE3 A2FA E543 9B7E 25B2 2836 81BA 6FE7 F41D
|
hartmans |
2021-01-14 |
[view raw]
|
I fully agree with Sam's long assessment, and won't repeat it here.
I have also sponsored a number of Mark's uploads.
Because of complex work that involves cross-package relationships, and
frequent addition of additional binaries, it'd be a waste of time to
go through DM stage.
I thus support Mark Hindley <mark@hindley.org.uk>'s request for full
Debian Developer status.
Signed with key FD9C E2D8 D775 4B78 AB27 9BBD 2C3B 436F EAC6 8101
|
kilobyte |
2021-01-15 |
[view raw]
|
Log
Date |
Author |
Action |
Content |
Public |
2021-01-15 12:45 |
kilobyte |
add_statement |
Added a new statement |
yes |
2021-01-15 12:45 |
nm@debian.org |
req_approve |
New statement received, the requirement seems satisfied |
yes |
2021-01-14 18:10 |
hartmans |
add_statement |
Added a new statement |
yes |
2021-01-14 18:10 |
nm@debian.org |
req_approve |
New statement received, the requirement seems satisfied |
yes |