This seems to be solving a problem that most of us would like to have, so it indeed comes out as arrogant. However look at it from another point of view. Imagin

This seems to be solving a problem that most of us would like to have, so it indeed comes out as arrogant. However look at it from another point of view. Imagine you are working on your job and a manager comes every 30-60 min to your desk to ask you a question about your project, often silly and already answered, breaking all your workflow (guesstimate about the email frequency for popular projects). Wouldn't you basically device some way to avoid this as much as possible? This seems to be a similar case to popular, single-maintainer OSS. The largest open issues I've had I think was under 10 in 1 day after launching a mid-popular project of mine and luckily it was _after_ launching (so no middle-of-workflow). I cannot even start to imagine the load for a popular dev, and this indeed seems like a good way for a saturated person to offload some of the work to contributors while raising up the entry bar. Cmon, this is even a basic economy rule: supply and demand. An alternative I've thought is, for purely one-on-one support that only benefits OP, redirect them to some support platform where it can be handled as the developer prefers. In that way it makes it even more viable for the developer to keep working on the project. I just don't love the perverse incentives it generates, but seems better than other alternatives.