> My preference would be for these projects to enroll individually, and for those maintainers that wish to direct the project’s compensation to the PSF or another entity should do so, and those that wish to distribute the compensation to contributors or co-maintainers should do so. For example, in the CherryPy projects, I share compensation with a co-maintainer and on Setuptools, I’ve offered equal shares to those aiding substantially with the maintenance.
The issue is that with the exception of setuptools (more than $800/mo) we haven't done this already and currently have a total of nearly $1,000/mo that we're just leaving on the table, which we could be using to pay for infrastructure / have bug bounties / hire contractors / pay maintainers at the PyPA's discretion.
I'm personally fine with you continuing to accept all the Tidelift funding on behalf of the setuptools project, as long as the other maintainers are in agreement and we have a plan to disperse that funding in the event of another more active maintainer joining or you deciding to wind down down your maintainership. I think that's one of the advantages of the PyPA accepting funding for the projects under its umbrella instead, though.