Advocate

This page collects statements of advocacy for NoisyCoil <noisycoil@tutanota.com> to become a Debian Maintainer.

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 details about advocating someone to be a Debian Maintainer. You should be familiar with their existing work within Debian and believe it to be of a sufficient standard that they can be trusted with upload rights to the packages they maintain.

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> 5 months, 3 weeks ago.

This process has been closed by johns on 2025-01-17: no further modifications are possible.

Signed statements

Statement

Uploaded by

Upload date

Actions

For nm.debian.org, at 2024-09-08:
I support NoisyCoil <noisycoil@tutanota.com>'s request to become a Debian Maintainer.
I have worked with NoisyCoil on multiple rust packages for more than two months now
and I consider them as having sufficient technical competence.

They picked up dysk and packaged all remained rust deps for this application while quickly picking
up the not-so-straightforward packing process of the Debian Rust team. 
Furthermore, they packaged tiny-dfr, also working down the deps one by one.

They have been very nice to interact and work with.

I have personally worked with NoisyCoil <noisycoil@tutanota.com>
(key 50CFC9D5E5BDE1CBCA57FD7B6DF008E70F28CBF7) for [T time], and I know NoisyCoil
can be trusted to have upload rights for their own packages, right now.

Signed with key 1459 3BFF 4A5E BF6F E0E9 716E ECBE DBB6 07B9 B2BE

werdahias

2024-09-08

[view raw]

For nm.debian.org, at 2024-12-20:
I support NoisyCoil <noisycoil@tutanota.com>'s request to become a Debian
Maintainer. I have worked with NoisyCoil on debian-bananas team and debian-rust
team for several months and I consider them as having sufficient technical
competence.

We share a common interest in the Asahi Linux efforts and want to bring
Debian up to speed with the parts needed to run on Apple Silicon (M1/M2).
NoisyCoil is very interested in putting in effort to make this happen and
brings us just-in-time notifications of what is now unblocked by something
that happened. I want to empower NoisyCoil to be able to improve Debian
without relying on constantly prodding other people that are too busy
to act on often trivial tasks that needs someone with permissions to do.
While NoisyCoil have alot of technical knowledge, there might be
Debian-specific (non-technical) knowledge that can still be improved. I would
however prefer NoisyCoil work towards DD instead of DM, because I assume DM
will also very soon come with too many restrictions that means back to prodding
people to hand out permissions or do tasks on NoisyCoils behalf. I'm sure
Debian will benefit from allowing NoisyCoil to work inside debian, rather than
doing a separate third party effort and putting their work outside the official
Debian archive.

I have personally worked with NoisyCoil <noisycoil@tutanota.com>
(key 50CFC9D5E5BDE1CBCA57FD7B6DF008E70F28CBF7) for several months, and I know
NoisyCoil can be trusted to have upload rights for their own packages, right
now.

Signed with key FAE1 E5B6 4652 BE79 8E27 8CC2 0BC4 7DC6 4D13 5306

2024-12-20

[view raw]

Log

Date	Author	Action	Content	Public
2024-12-20 10:01	ah	add_statement	Added a new statement	yes
2024-12-20 10:01	nm@debian.org	req_approve	New statement received, the requirement seems satisfied	yes
2024-09-08 19:22	werdahias	add_statement	Added a new statement	yes
2024-09-08 19:22	nm@debian.org	req_approve	New statement received, the requirement seems satisfied	yes