[neilv]

I appreciate that an open source developer is likely to be burned out on some people's expectations or unthinking requests, but that page was too long for me to even skim.

Usability-wise, one could lead with a terse bulleted list of "use cases" for which people should contact you, and how.

Then state you can't handle all the other usual reasons people want to interact with an open source developer, maybe giving examples. Then follow it with explanation of why.