3 ms·
I think you have fundamentally misunderstood my argument. "28 people on payroll" is not at all important to my point. The financial report says how much money
by zahlman 2y ago
I think you have fundamentally misunderstood my argument.
"28 people on payroll" is not at all important to my point. The financial report says how much money is spent on salary. The important part is that most of it doesn't go to developers.
I don't see bloat because of how many staffers there are. I think funding is misallocated because developers don't get it (rather, they aren't hiring more people that can actually work on Python full time - my understanding is that most core devs have a day job) and because international events apparently run on a shoestring compared to PyCon, which in turn doesn't seem remotely important enough to justify its expenditures.
This results, among other things, in an ecosystem where basic PyPI support requests (see e.g. https://github.com/pypi/support/issues/2771 https://github.com/pypi/support/issues/2771) go unanswered for months, and Pip has embarrassing flaws (asking it to download a package without installing it can cause it to run arbitrary code from setup.py - https://github.com/pypa/pip/issues/1884 https://github.com/pypa/pip/issues/1884 and many others) that have persisted for almost the entire history of Pip.
That said, I do see "bloat" in the social overhead of Python governance, given the proliferation of (volunteer) Work Groups that don't seem to be accomplishing very much.
And just to emphasize, I did already describe the PSF as "woefully underfunded", because it is - just like most other open source orgs.