Python Creator Guido van Rossum Blames His Resignation Partly On Social Media

'Swapnil Bhartiya, the founder of TFIR, sat down with Guido van Rossum, the creator of Python, to talk about the origin of the language and why he stepped down from the leadership of the very project he created,' writes sfcrazy.

In the interview, van Rossum emphasizes that he still remains one of the core developers, and provides this update:
'We're going to set up a new form of governance. We haven't decided yet what that will be. There is actually an interesting time ahead where we currently have about five of six different proposals for new governance systems, and in November there's going to be a vote among the core developers about that. And then there will be another vote that will actually determine specifically who is going to form the leadership. So we're starting out by choosing a constitution, and then using the rules set out in the selected constitution, we're going to vote for a leadership...'

He talks more about his resignation when asked if there's ever been an after-the-fact debate about decisions he's made:
'Well, that certainly happens too. What led to my resignation was a form of that, where on social media -- and I've got a feeling that social media are sort of getting out of hand... But for me personally, social media definitely sort of caused additional stress. And I did not enjoy it when core developers were sort of sending tweets where they were questioning my authority or the wisdom of my decisions, rather than saying it to my face and having an honest debate about things...

'It might just have to do with the fact that I've had this role for 28 years... And all that time, I've been sort of the final decider, the final arbiter. I'm getting older, I'm not always available... I just want to spend less time feeling stressed about what is the community -- I have this attitude where everything that was being said on some of the mailing lists, python-ideas, python-dev, touched me. I felt involved in everything, because ultimately every idea would end on my desk for deciding. And I just thought that that should be a responsibiity that should either be shared or transferred... Given that I've been on the project for such a long time, and some of the currently active core developers are good personal friends that I've known for 20 years or more, I am completely confident that the more experienced core developers that we currently have, plus the newer core developers that we have, together will be able to weather any kind of storm that might come Python's way. Yes I resigned from the title suddenly, but there were a lot of responsibilities that I had already completely delegated. I mean, I barely touch the code base, I barely reviewed submissions.

At one point van Rossum compares the future of Python to that of a grown-up child, in that 'You're supposed to raise your child for independence...'

So what's he doing now? ' I was and still am a principal engineer at Dropbox, which is actually where I spend most of my time.'

Read more of this story at Slashdot.