vnparker

"to contract a developer to help CPython determine what needs to take priority through analytical metrics as well as helping CPython understand how backlog can be addressed. The role will also be responsible for surveying maintainers to paint a better landscape of CPython, which will be used to ensure future funding and volunteer hours are used efficiently and effectively."

This will turn into a bureaucratic nightmare that increases the power of the existing cabal, most of whom already do not provide any meaningful code contributions.

And these caused a lot of disagreement in the core team. Many thought that they were introducing too much churn.

Coupled with the fact that they get paid for the alleged churn and others have to catch up on unpaid time, this can ruin a project.

The Python dev community has certainly gotten far less vibrant (and productive) in the last decade due to stifling corporate influence.