Front Desk or DAM approval

This page lists the approval statements for Christian Ehrhardt <christian.ehrhardt@canonical.com> to become Debian Developer, uploading. Only statements from FrontDesk and Debian Account Managers are valid for this requirement to be satisfied. Usually, this requirement is completed last, after the rest of the process is done.

This process being for Christian Ehrhardt <christian.ehrhardt@canonical.com> to become a Debian Developer, if the approval is made by a FrontDesk Member it won't become effective immediately. A grace period of 7 days will be observed before the process going further (RT ticket submission for the keyring changes and account creation).

This requirement has been approved by Housekeeping Robot <nm@debian.org> 4 years, 6 months ago.

This process has been closed by noodles on 2021-05-20: no further modifications are possible.

Signed statements

Statement

Uploaded by

Upload date

Actions

Hi

Please make Christian Ehrhardt (currently a Debian Maintainer) a Debian
Developer, uploading (advocated by bluca, kanashiro, paride, rbasak,
sergiodj, utkarsh, vorlon).

Key 92D618F668F22F8ED80BEEF5BA3E29338280B242 should be moved from the
'Debian Maintainer' to the 'Debian Developer, uploading' keyring.

  Key fingerprint:  92D618F668F22F8ED80BEEF5BA3E29338280B242
  uid:              paelzer
  First name:       Christian
  Middle name:      -
  Last name:        Ehrhardt
  Current status:   Debian Maintainer
  Target keyring:   Debian Developer, uploading
  Forward email:    christian.ehrhardt@canonical.com
  Details:          https://nm.debian.org/process/895/
  

Christian Ehrhardt has accepted the DMUP in a signed statement.

Details from paelzer:

  Hi,
  I would like to apply to change my status in Debian to Debian Developer,
  uploading.
  I have worked on:
  - - co-maintaining DPDK (from the initial ITP to it's today's well
  integrated form)
  - - maintained mdevctl which is a small helper in the KVM/libvirt space
  - - I've filed many bugs, helped to drive them to a conclusion and since
  the
    dawn of salsa have used that a lot as well to contribute to Debian
  packages.
  I'd like to:
  - - Be part of the voting community; After being around so long and
  working with
    so many people it feels wrong to always only wait on the outside for a
  result.
    While I'm certainly not the person that has an opinion to everything, I
  can
    easily decide which option I prefer.
  - - NMU uploads; When clearing broken packages for Ubuntu mostly I'll end
  up
    fixing it in Debian via salsa-MR or filing a bug with a fix (or if
  unknown
    at least documenting the case). In some - gladly rare - cases
  maintainers
    can't help "in time and in those cases I think I could help a bit
  better if
    able to do NMUs.
  - - Porterbox access - TBH I mostly work on Ubuntu and therefore have
  plenty of
    access to the architectures supported by Ubuntu. But sometimes and
  issue
    is only present at a Debian-arch that isn't in Ubuntu. In that case
  being
    able to use a Porterbox (and fix it myself) is better than just
  throwing
    a case to the porters.
  Kind regards,
  Christian Ehrhardt
  Submitted via nm.debian.org on 20th April 2021


- -- 
Thank you,



Pierre-Elliott Bécue (as Front Desk pp. DAM)

Signed with key 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2

peb

2021-05-03

[view raw]

Log

Date	Author	Action	Content	Public
2021-05-03 08:37	peb	add_statement	Added a new statement	yes
2021-05-03 08:37	nm@debian.org	req_approve	New statement received, the requirement seems satisfied	yes