-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 I believe a candidate to become Debian Maintainer should be judged by the work he has actually done for Debian and by his social behavior. When he initially started to contribute to Debian in 2016 and asked for help and sponsorship on debian-mentors he clearly did not know all the procedures many of us take for granted. It is true that he should improve to learn more about copyright and how that should be properly documented in Debian but I was always under the impression there was merely a language barrier and a lack of knowledge. His latest introduction to Debian, pekka-kana-2, also lacked a DFSG-free license (although the license intent was clear), so I simply suggested to contact the original author and ask him for a clarification and because of Carlos' determination we can distribute the game in main now.
When I started to package my first application in 2012 there were no autopkgtests, no Rules-Requires-Root and hundreds of Lintian warnings contributors are expected to take care of nowadays. We raise the bar higher and higher and strive for technical excellence, which is great. However in my opinion new contributors are bombarded with too many technical terms and Debian conventions, they all should speak English fluently and being a computer science student or even better a professor would be appreciated. Some friendly Debian developer should have explained to Carlos that one should apply for Debian maintainer first in January 2019. He is doing that now. A Debian maintainer is responsible for their own packages after a DD has granted upload permissions. In no event is there any great risk of copyright violations that puts Debian in danger because a Debian developer is still responsible for making sure a package complies with the DFSG when uploading the package for the first time. I agree we should be rigorous when someone applies for DD but the limited role of DM is really an entry point and different from that. I still uphold my view that Carlos is capable to maintain some of his packages himself, especially those he is already upstream for. -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAl1sNplfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQACgkQ2a0UuVE7 UeQDHg/8Cf54yHBb+gosQ8iJSViK01Ti7Wa3UBmk6fICq2tF42DjXpHYS9QHDfwq L0qJL7s+7lUHLydzJqR9HZg9jH52ApUW8WOi1sAshrgEARA9oduxy64lPiDeg8j9 cx80S53Olacoijs/JB8IqFkeGEb3nzx0R4OAuXtPUmLq9B6fpDygg5+GFhgMhKf3 XJ70iGDDGPHB/lbK+cAwhj5TlhiNZ6N1hDGvuY6jPCLH8p9CvEnXS7vUE7wZ0f28 NEsInjZlwRGgse/UWdOhba/l98toSYu6Zl9F6vQqtA5ILCzLL5OjeixU2t+MeVa3 no0pU50uTYbghq4Z7ONezBburdiTHw4+Qw5WTCusM9vxGiA8JZbV/Ev7TzOZj+ll M6ZPzCeRFGoGxhoBfNyIFVZbuKwYHNk2ytgh8HJiCnuAtPgBbfleZfyV3PmqVvzT /JWMyZ8N0vjUoDWdFzgBg0qAcgKrZie2l1RIinaDQt0O++5J0vpis/JfxezFzRvu SqMYrYIPNKHfyUHOSjnAb76cswDOy+f1Rd2Z8ol945xQyMCbIvEAPrImw0Lyg65o GqmFSxrkmqkOMkXZcyDLt4jdCb//+5KdylWxsM6H2zvq241sg2xVcWrCT0qnl9Vp 6Q49rvKHWApJ1nDrmxz+aePso5JomUanxC/VI0EzR1Lj4K9ytw8= =ZdEd -----END PGP SIGNATURE----- Markus Koschany (via nm.debian.org) For details and to comment, visit https://nm.debian.org/process/676 -- https://nm.debian.org/process/676
