Front Desk or DAM approval

This page lists the approval statements for HAYASHI Kentaro <hayashi@clear-code.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 HAYASHI Kentaro <hayashi@clear-code.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, 7 months ago.

This process has been closed by noodles on 2020-09-24: no further modifications are possible.

Signed statements

Statement

Uploaded by

Upload date

Actions

Hi

Please make HAYASHI Kentaro (currently a Debian Maintainer, with guest
account) a Debian Developer, uploading (advocated by dai, knok).

Key D92025640886D27D14A9EE02D22C1A883455D448 should be moved from the
'Debian Maintainer, with guest account' to the 'Debian Developer,
uploading' keyring.

Note that HAYASHI Kentaro already has an account in LDAP.

  Key fingerprint:  D92025640886D27D14A9EE02D22C1A883455D448
  uid:              kenhys
  First name:       HAYASHI
  Middle name:      -
  Last name:        Kentaro
  Current status:   Debian Maintainer, with guest account
  Target keyring:   Debian Developer, uploading
  Forward email:    hayashi@clear-code.com
  Details:          https://nm.debian.org/process/750/
  

HAYASHI Kentaro has accepted the DMUP in a signed statement.

Details from kenhys:

  For nm.debian.org, at 2020-05-17:
  I would like to apply to change my status in Debian to Debian Developer,
  uploading.
  I'm a user of Debian/Ubuntu since 2012.
  and I maintain some packages on Debian. [1]
  I become Debian Maintainer since August, 2018. [2]
  I worked on keeping the package in good shape, and
  fixed bugs, sent ITP/RFS for introducing new packages.
  I also helped for packaging linux sound subsystem
  maintainer who want to make available libhinawa/hinawa-utils on Debian.
  [3]
  As a DM role, I become to feel that it is important to
  cooperative work to maintain package quality.
  (not only fixing bugs on Debian, but also feedback to upstream)
  It may be OK to stay as a DM, but becoming a DD is a efficiant
  way to fix some architecture specific bugs by using porterbox,
  or to upload packages without bothering other DDs for sponsorship.
  I would like to more get involved debian community,
  especially exploring to improve find/fix bug mechanism as a daily task
  efficiantly.
  So, I want to become DD.
  [1] https://qa.debian.org/developer.php?login=kenhys
  [2] https://bits.debian.org/2018/09/new-developers-2018-08.html
  [3] https://www.alsa-project.org/pipermail/alsa-
  devel/2018-August/139448.html


- -- 
Thank you,

Joerg Jaspert (as DAM)

Signed with key FBFA BDB5 41B5 DC95 5BD9 BA6E DB16 CF5B B125 25C4

joerg

2020-09-20

[view raw]

Log

Date	Author	Action	Content	Public
2020-09-20 18:59	joerg	add_statement	Added a new statement	yes
2020-09-20 18:59	nm@debian.org	req_approve	New statement received, the requirement seems satisfied	yes
2020-09-20 18:58	joerg	req_unapprove	Requirement unapproved	yes
2020-09-20 18:58	joerg	req_approve	Requirement approved	yes