Python is a huge open source software project, and ensuring it evolves and get better and at the same time not too complex is a massive undertaking from contributors around the world. This talk will try to tell you about how that process works. You may find it interesting if you want to get involved, have ideas to propose, or are just curious about how this system that you use actually gets built. The talks will not focus much on the formal process to submit code or a language change proposal (which are thoroughly documented elsewhere), but more on the team dynamics, answering questions like "is there people getting paid to work on Python?", "how are decisions made and who takes them?", "what kinds of changes are there?", "when should I write a proposal vs file a bug vs write an email at python-ideas vs talk to Guido at a conference?", "what kinds of ideas are more or less likely to be accepted?" "what are common causes of rejected ideas?". I'm hoping that by the end of the talk the audience should have demystified a lot of what happens behind the scenes and help them get curious about getting involved and contribute.