Skip to main content

28 November 2020, 9:19 pm

Python's Steering Council Assesses the After-Guido Era

Python's Steering Council Assesses the After-Guido Era

47 of Python's core developers participated in this year's Core Development Sprint, according to this report — "but what's more important is the very real and necessary community building that seemed to have taken place..." It's an especially critical time for Python, which switched to a steering council model in February of 2019, after Guido van Rossum had stepped down as the language's "benevolent dictator for life...." [During the Python Steering Council and Core Developer Q&A] core developer Ned Deily asked a question which had probably been on everyone's minds: how is the steering council experience working, now that van Rossum is no longer serving as the language's benevolent overseer? And core developer/councilmember Carol Willing was the first to respond. "I've been involved in a lot of governance organizations, and I would say the Steering Council has been towards the top in terms of sticking to the agenda and being thoughtful and collaborative in how things are working." They meet every week for an hour — with a pre-set agenda — and "in general, I think it's working quite well. If there's anything I take away from it, it's I'm amazed that Guido was able to do this function as a single person for as long as he had been. Because it's a lot of work, even amongst five people...." Core developer/councilmember Barry Warsaw agreed. "A couple of us have been on the Steering Council since its inception. And there was a lot of things that the governance PEPs didn't really cover. So we really had to figure out the process for a number of things. I couldn't be more happy to work with both the first year of Steering Council members, and this year of Steering Council members. I think everybody is doing this for the right reasons — because we love Python, and we love the Python community..." Deily agreed with their assessments. "My impression is things are going really well, better than might be expected. I was very proud how we as a community met the challenge of coming up with a governance, kind of from scratch. And I think — I don't know for sure all of Guido's motivation for doing it, but I think in a lot of ways he did it the right way, just kind of forced the community to come up with things. And I think all in all that worked out really well...." About 48 minutes in, there was a question from van Rossum himself about the issue tracker at (affectionately known as "BPO"). "So I'm desperately curious about the status of the BPO to GitHub migration." He paused, then asked delicately, "Uh, how much is the Steering Council willing to share of what they know, and how much do you actually know?" Cannon responded, talking about the group hired to run it, and thanking the groups whose donations had funded it. And then Deily suggested van Rossum volunteer for the working group, "because it's going to affect all of us." van Rossum asked if it would be appropriate if he volunteered, everyone agreed, and he responded, "Okay, I'm game."

Read more of this story at Slashdot.