Łukasz is a fantastic person (although I have to copy and paste his name every time ) and he makes a darn good candidate for the steering council. However he is also the release manager for Python 3.8. The combination is bugging me. In my opinion it would be more beneficial to have the RM independent from the SC, so she/he can act independently from decisions of the SC without a conflict of interest – a bit like checks and balances in modern democracy.
I don’t recall a formal definition of powers of a release manager. Except for PEP 8011, no governance PEP even mentions RM. Personally I see the RM a bit like a product manager: the SC decides what major changes land in the next Python version. Traditionally the RM has acted as a gate keeper to ensure, that last minute changes do not break the release or give exceptions to changes during beta freeze. And here lies the potential conflict: the SC may want to land a feature while the RM considers the feature as non-ready yet.
What do you think? Should the RM always be independent of the SC?
PS: Łukasz, I’m sorry that I’m speaking up against your nomination.
PPS: I really should look into compose key combination for the polish L with a stroke.