From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id D9C0D158094 for ; Fri, 1 Jul 2022 18:15:03 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id EE12DE0A0B; Fri, 1 Jul 2022 18:15:02 +0000 (UTC) Received: from smtp.gentoo.org (woodpecker.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 7F795E0A0B for ; Fri, 1 Jul 2022 18:15:02 +0000 (UTC) Date: Fri, 1 Jul 2022 13:14:59 -0500 From: John Helmert III To: gentoo-project@lists.gentoo.org Subject: Re: [gentoo-project] Gentoo Council 2022-23: Questions for Candidates: how to increase contributions Message-ID: References: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Project discussion list X-BeenThere: gentoo-project@lists.gentoo.org Reply-To: gentoo-project@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="i7hPctRfl6pBnWSX" Content-Disposition: inline In-Reply-To: X-Archives-Salt: cbd02e02-05bb-4a49-a262-75267f3eff7f X-Archives-Hash: f487c1001b8f306e9ef2e85ead4fc3c7 --i7hPctRfl6pBnWSX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I'm sorry for the belatedness in my response, I've been away for much of the voting period. I agree with some of the other's sentiment that these aren't entirely useful questions for council given council only acts on what is brought to it, but further replies below. On Thu, Jun 16, 2022 at 06:06:40PM +0000, Robin H. Johnson wrote: > A question I'd like the candidates to answer. >=20 > What do you feel that Council can do to increase the contributions to > Gentoo? >=20 > - how do you feel development velocity of Gentoo should be measured? > - how do you feel technical debt of Gentoo should be measured? I think Repology provides some useful metrics related to these questions: https://repology.org/repository/gentoo Somewhat less quantitatively, technical debt should also take into account this like bugs with PATCHes that haven't been handled by the maintainer(s), pull requests that remain ignored/unreviewed by maintainer(s), and how well sets of bugs on Bugzilla (i.e. bugs assigned to a maintainer or bugs for a specific package) are maintained. It's always a bit frustrating to find a package with several years of bugs that haven't been touched by the assignee. > - how do we make it easier to get orders of magnitude more contributors? > - how do we make it easier to do QA on significantly more contributions? > - what blockers do you perceive in the contribution processes, and how > do you think they should be tackled? I'll echo tooling as one of the big barriers in contribution. In the last year or two we've made leaps forward here, maybe most notably with pkgdev and iwdevtools. Slyfox also mentioned some tooling he'd like to see in his retirement blog post: https://trofi.github.io/posts/226-farewell-gentoo-dev.html A better CI process for user contributions would allow us to process user contributions much faster. This is one of the primary goals I see in transitioning to Gitlab. The current process of users opening a PR and needing someone to manually build-test it and report back any issues is tedious and slow, and we'd do better with some automated CI here. >=20 > Many of the developers I nominated in my previous email to the -project > list were because are the very prolific contributors or have significant > impact in their contributors: how can we increase not just the prolific > contributors, but get many more contributors everywhere? We have many, many contributors who are already proxied-maintainers and we could probably do a better job of encouraging these maintainers to become developers. If we had a build CI process that automatedly reported issues with contributions, the human dependency for this would be largely eliminated and contributors wouldn't have to wait for a human to test their changes and report issues. I think this would greatly decrease the time the average PR spends open, most of which is waiting for human action. With a faster turnover for PRs, more PRs can be made more quickly. >=20 > --=20 > Robin Hugh Johnson > Gentoo Linux: Dev, Infra Lead, Foundation Treasurer > E-Mail : robbat2@gentoo.org > GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85 > GnuPG FP : 7D0B3CEB E9B85B1F 825BCECF EE05E6F6 A48F6136 --i7hPctRfl6pBnWSX Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEElFuPenBj6NvNLoABXP0dAeB+IzgFAmK/OZ4ACgkQXP0dAeB+ IzhiAA//b+EhyHaq9GJzRF3RWE4tZlg0gOKHSKhWwUW0lcugXp679pfyTPieDrPT 9xR81ez2SxdqsUfuJVMJ2yIaN08p7BYQkng2X3pKysNdce1NctZ8y39XVZzm/33y WgDc7ZtTjjvs7PMLoJx7z3b4HgWYoJ2Br9npnTcsE0RqpWURuR8C/m1uHx3XCfFu hr+3yPOBR1xBaP4brMy2BxukFE8QxjJC9kM25BWs71R1p15n9Vxdd1ONJUZjR2Fl je9PoPPpXdYfngwrHO7f2XgnEb1QKRo3jSFCzxgtnQHEN6PIQ6P38ml8xOn7AyUe fDfzjW+k4AnMAF0IKq2pSq73bTF+tOYwOJhNCua7g4wTYp8fFajjAvEcF4PFWgZW xXJ6x59sz2cXG96fHjxwwDO3yHqu61kBd7F5DdBwReXoc14p2rNThhQL/C+0jwdG YlgwAKCL4Z61Xm07LaFM/KBQgM9S5UFeDzOm43XjrecY5KdMcDAT0xduIBR3lZ7j 22TvY12fhnJiirigDKpoc5DpGRLmlrQCZOhqnHx1aIxDQ2TYwclY03pVAU0jCVCP LHSS1VeGPqCqdERO24Kuq9D1NT4sCdl5U0ob82l081izpvF34zQDnEb7un19gNCB 6PJCyuyShBF0Nle4wjCC+UhOSeqs80clARvUIAmyy5sijFjFwKw= =c2nM -----END PGP SIGNATURE----- --i7hPctRfl6pBnWSX--