 So this is a new feature we're just inventing. Person of the month, the basic idea is to highlight personalities of the Python community, international or local, so that when you start being a member of this community, you see names thrown around. And this guy is the author of this, and this person is this organizer. And with these five minutes highlights, I'd like to introduce names of the community to you so that you can relate and know who they are and maybe in conferences you can connect with them because you know something. So any feedback is very welcome after, because it's the first time we're doing this. So if you want to do it, you can. If you have any feedback, it will be welcome. All right. For this first segment, I chose Quido and Russell. So Quido is the inventor of the Python language. I have a few dates. So in 1989, he started Python. And 14 months later, there was the first release. So it was December and then February. So you can see our favorite language has 20 years. You can see along the history of Python things from the community which have like Quido's participation, like with the creation of a mailing list, actually a newsnet discussion group. The process became more open and more focused around the community, not just one person. The same thing with the PEP process. It's a balance between heavy standardization and just an actual discussion in mailing lists where you get an actual chaos and you don't make progress. So with the PEPs, that's how the community defines a big change we want to do and people can have objections and counter-proposals. And big syntax changes or big module additions are discussed with PEPs. I don't know if everybody familiar with PEPs. And this process was invented by Python and it's been taken in a lot of other communities. So it's a very good legacy from Quido van Russell and other people for free software in general. This is also the year of Python 2.0, which is mostly a big license change from the previous generation. It's not like Python 3. A good date, Python Software Foundation was founded in 2001. So it's like a nonprofit organization which holds the moral rights. So you see, Quido is still leading the language evolution but not coding as much. And in these big steps, you can see how he's making sure that the community does not depend on him only, which I think is a really good attitude. In 2005, he was hired by Google and he left in the end of last December, so seven years. You may know this logo, Google App Engine here, which is Google's platform so that you can run your applications on a hosted platform without renting your own server. It's a modified Django. Now he's working for Dropbox, that was the other logo. A big contribution from Quido is also ReadVeld, which is a code review tool. You can use it for free at codereview.appspot.com. And of course, that was the year of the Python 3 release. And another big change, like more recent, using Macriol as version control system instead of subversion. Some reasons were like ease of use for the developers, but mostly the change was done to ease contributions by other people because it's much more easy to maintain your fork and your patches with a DVCS than with subversion. And it took a year to be implemented. A few interesting links. That's Quido's core plate. It's in Virginia. It's Python. That's his website, his homepage on the Python.org site. This is his current web blog when he talks about Python or tech or many things. And this is a really interesting blog about the history of Python. You can learn why he used indentation to name it blocks or meta classes. How did they come to invent that? It's really interesting to understand more about how things were implementing. And the big surprise is that the first version of classes is just like how we know them today. It's really fun to understand the history. This one is an article about the history of Python, which you don't find from the docs at Python.org or his web page. So I put the link. It's an interesting one. I'd like to leave with a quote from Quido. The joy of coding Python should be in seeing short, concise, readable classes that express a lot of action in a small amount of clear code, not in realms of trivial code that bores the reader to death. Thank you.