-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 For nm.debian.org, at 2023-01-13: I support Timothy Pearson <tpear...@raptorengineering.com>'s request to become a Debian Maintainer. I have worked with Timothy Pearson on chromium packaging for 8 months and I consider them as having sufficient technical competence.
Timothy's company focuses on POWER9 systems due to its openness, and presentations he's given along with interviews make it clear that he's passionate about free software and open hardware (examples: https://www.opensourcevoices.org/24 , https://www.youtube.com/watch?v=Tvey2Nsc3oY , and https://peter.czanik.hu/posts/power-timothy-pearson-raptorcs/ ). Timothy filed a bug 11 months ago on the chromium package asking me to incorporate a set of ppc64el patches into it. At the time I wasn't in a position to do that, but a few months later I began working with him on getting some of those patches upstream. When it became clear that upstream wasn't willing to accept most of the patches, we came to an agreement that we'd include the ppc64el patches in debian's chromium as long as he kept them updated for every new release. For the past 3 months, he's been doing just that. In addition, he's been very helpfully preparing and testing some of the chromium security updates. He clearly has the technical and social ability to maintain packages and work within the debian project and with our upstreams; as a very recent example, the last chromium upload built for amd64 but the v8 javascript engine would crash during the build on ppc64. He did a bunch of debugging and discovered that the register stack had an off-by-one error. He committed the fix to chromium's git repo on salsa, and then submitted the fix to upstream v8 (which upstream chromium will then pull in at some point): https://chromium-review.googlesource.com/c/v8/v8/+/4163419 . He then tested it and found ANOTHER crash at runtime in libdav1d, which was fixed in upstream libdav1d's git but not yet fixed in chromium. So both of those fixes are now in debian's chromium packaging. He's been reliable and responsive in my communication with him. I think he'd be a huge asset to the debian project. I have personally worked with Timothy Pearson <tpear...@raptorengineering.com> (key 6E58CA48BEAEF11C0345205EEC3C80BC57319B7E) for 8 months, and I know Timothy Pearson can be trusted to have upload rights for their own packages, right now. -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEUAUk+X1YiTIjs19qZF0CR8NudjcFAmPBEikACgkQZF0CR8Nu djejiRAAr6GmtHTHn8gc7vX8gxXfC05jC8DA1DOeH0Z7Krq5SfF5D358FeH3SdO2 do0AH33mtjsRMxhorNMZApYD65AXB8sZRyyx3p+bZM4JzFMKrt7mgz/VIeiuJFHh QHF2sun/Ub6whDgyFSnDQMVm+ZMWg87k6jkVgsyc9B7TrYEwbOsuWVSlwgpDkZu0 4ZwiltaCAObgPIgRd/wCk5Yp5D6RKX2+ILErTquOjocfGZ4hH+b4q84lnTBJZVnQ oVnxxAy+/Z7FQjqslGD3aZ0Qw68cGF1G6MxJwHtI9k6yY9Beibx4bLMifsEliyt7 ACdkSxV8owF6K03XCEZuzo1mxefjWrBdcc0uSJ28EM4zLYYrhkyqXeEyZypWwJii OWQ20Vo9d4vG5U49gqCs0oG+0KQgZGDrnHIb+hTREWqb9EXurdadO7Yb05UA+0LF VNzPKW3mMwqdqX0ekT1h9nNzJpYgFdCUTWzfzTRrzyAzcHjDYZBOetJjPxlTZ4tb nwqeVwoDnkGAZXppcTrO31C/Zw0hwkkPe+Fj4yUJr2zK+e/2E6pf4/oOraR2S+tB 6718ucqLrxYtBHFxBvl34OAich/8RwIZ89RJ9qhLDaUGNNduLlS9eL02TIhZ0NGl PVYqrkv1nxvUgEjEVxI0qLmEVbQvOIp6bmFaOdwXVizpukaj/xY= =EcVx -----END PGP SIGNATURE----- Andres Salomon (via nm.debian.org) For details and to comment, visit https://nm.debian.org/process/1154/ -- https://nm.debian.org/process/1154/
