Greetings Evan,I struggle to understand your message, but if you are saying that random assignment was put in place, please make that clear if that is not already the case. I for one will not volunteer in Superset if it systematically and randomly assigns tasks to me, nor in any project which does that without the consent of volunteers.
On 6/9/2026 4:39 PM, Evan Rusackas (ASF) wrote:
Chiming in from Superset PMC here. Guessing this is spam, otherwise unsure why this thread from nearly five years ago got singled out. Anyway, here we are :) This isn’t as big of a problem as it was back then. We have both human and bot processes in place. The links singled out about how GitHub measures top contributors/contributions are not our own metrics, and GitHub is far from our only forum. Just trying to put our collective/proverbial hand down, regarding the original issue raised in 2021. Thanks, Evan On Jun 5, 2026 at 5:15 PM -0700, Philippe Cloutier <[email protected]>, wrote:Greetings Erik, On 2021/07/08 21:03:39 Erik Ritter wrote:Hi all, I'm a PMC member for Apache Superset, and we've recently been struggling with the number of issues reported in our Github repo. We'recurrently at >800 open issues, and are having trouble keeping up with responding and addressing all the user issues and feedback. We were curious if any other Apache projects had a way of managing Github issues that works forthem. Wewere considering setting up a bot that assigns new issues to a randomcommitter/PMC member, but are open to other ideas too. I most strongly recommend not to do that. Less than 3 months ago, I stumbled into what could be a case study in how ticket assignment fails. https://github.com/keepassxreboot/keepassxc/issues/863 is a "high priority🚨" issue in a high priority project, and has been assigned for over 8 years, yet seems even further from completion than it seemed 8 years ago. Unfortunately, this is not an isolated case: https://github.com/keepassxreboot/keepassxc/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22high%20priority%20%3Arotating_light%3A%22 But the worst part is all these were *self-*assigned. Automatic assignment in CBPP would be a recipe for disaster (unless the assignee consented to that automation). Volunteering as a committer or PMC member does *not* mean volunteering to solve any number of issues, let alone randomly picked ones. Allocation gains are one of the greatest factors behind CBPP’s successes.
-- 🅭🄍: https://www.philippecloutier.com/Common+infrastructure+licensing#list Philippe Cloutier
OpenPGP_0x8A37FF445EA6611D.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
