Re: Jerome Charaoui: Declaration of intent

[Gunnar Wolf]

Sean Whitton dijo [Tue, Aug 29, 2017 at 02:08:37PM -0700]:
> Packaging mistakes can be rectified, but rectifying them sucks volunteer
> time.  The reason why we expect highly trusted contributors to have a
> longer track record of packaging updates is to reduce the chance they'll
> make mistakes which cause work for other people.
> 
> Becoming someone who doesn't make common packaging mistakes just takes
> time and lots of uploads.  Not having that ability doesn't reflect on
> someone's general technical ability.

Umh... /methinks that this volunteer time sucking will happen
regardless of whether the person in question is a DM or a DD. The
number of botched uploads a DD can make is _usually_ n+1 the botched
uploads the same person would do being a DM (that is, a package gets
reviewed and access is granted to do unsupervised uploads).

Of course, a DD will be able to NMU. However, how often will a newbie
DD NMU something they are not familiar with? Or, uploading to
NEW... NEW gets reviewed no-matter-what, so that's not _so_ different.

People tend to get confident over time. I guess that's one of the
reasons I have made some of my mistakes: Because of not
triple-checking some stuff I would be checking otherwise. Say, I have
uploaded to backports something that was lacking quite a bit of
dependencies. Silly me. Or, as keyring-maint, I have often made
formatting errors in the git log (which we consume for some automated
tasks) requiring me to rewrite history. Both are things that Should
Not Happen™, but happen nevertheless. I guess that if I were a new DD,
I would be more careful.

I understand your point and won't argue more about it — But what I am
stating is... There is no clear point as to where a person has "done
enough" to be trusted to be careful not to botch too much. I can
assert the level of care I have observed in this person's interactions
is high enough that I trust he won't be a serial upload botcher ;-)


signature.asc
Description: PGP signature

Ming-ting Yao Wei: Advocate

[Hector Oron]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

For nm.debian.org, at :
I support Ming-ting Yao Wei 's request to become Debian 
Developer, uploading.
I have meet Ming-ting Yao Wei, several years ago, 2009, when we had MiniDebConf 
in Taiwan, since
then I have been sharing DebConf experiences with him in Heidelberg and 
Montreal. I have not
directly worked with 'mwei' in technical matters, besides he worked on upstream 
patch to add
Chinese input method to libinput (which I happen to co-maintain). I am 
confident he is quite able to
move around Debian infrastructure in proper way. On the other hand, I have been 
working with
'mwei' preparing DebConf 18 in Taiwan and he has proved to be a great asset for 
DebConf
organization team taking core tasks in the critical path for DebConf to happen. 
In the same
way I believe 'mwei' will be a great asset for Debian development.

I have personally known Ming-ting Yao Wei  (key 
FED5434845287DF262931489CFBBFCE0B74F1B14) for 9 years time,
and I know Ming-ting Yao Wei can be trusted to be a full member of Debian, and 
have unsupervised, unrestricted upload rights, right now.
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE6Q8IiVReeMgqnedOryKDqnbirHsFAlmmqEIACgkQryKDqnbi
rHvV9Q/+K9xjzP7dP4MswrbEjLeTzTxmA9SyDMV//YmQ1K8PTvAis8jKoIzLNaAr
Ber0TFouOalM0MHcspFXzm7KXMS//Rwd28ZUxvYpQ+t3CZ+0bfy+NYrXDSzWFPI8
g2LL+ctBIgs5yNPV7dkLsLNLMy/OgsiT+jikc2C67wYDoVXHc0lWjkM1roTqkMyo
4KPoMLIr54Fj1O+DRVz3JZV1VxFwxk2ItGHXYQMBREp5t3VYJpTCPciA7RfY2Fc5
o0g+sIurf2u7Ueh+uZMBK0Lll6D1jPAW7Vl4GKn4tmfgugYEJrlvATPzDkiHdJEh
6SRL7DnBeXcb8tRqYj1ddDVXeyQGiIW9DgeNjHShcdOSLqx636RFrmlQjITiBJHN
4pxzZRSZwEIO2xPJFdNJaFFoIWrUVFoRn45XCkyCeDeO0olkxJtQk3YVBprc2P2S
Y8bD2b00a4VaRcxhB17ECqCDch6paprmO/X0EXNlA6O08LIxoi8AeU6rnCOaHjv/
LFqhT4aRpTNh4S2eqf0WSwzNovf19CGBh92zoR/6YjXWyrt42py9AtrXxJtTaH3B
VvxYzGT7YFtPI1AZvzV+WhgCeih5+/SBpv0oqnKBqKReW4mwT/Tj+EiAwONS5ZTc
nM6JSo7bQSF/gOyNDu2G8XxqADJakyGcQbjpAENjiOn/8Pn7Tg4=
=Gjdi
-END PGP SIGNATURE-

Hector Oron (via nm.debian.org)

For details and to comment, visit https://nm.debian.org/process/279
-- 
https://nm.debian.org/process/279