 So, just a second, I just need to start this as well. Okay, so hello, good morning. This is the final day of the conference, the sprint days. So, what we're going to do today is going to give a few short announcements, and then maybe some teams will want to maybe update us on what they're going to do today. Maybe introduce new things that they want to do. So, I'm going to give everyone who wants to say something a chance as well. Please raise your hand as the attendee, then I can make a panelist, and then you can have a few words. Right, so, morning announcements for Sunday. I published the conference videos yesterday to Discord. I put the links into the, I put the links into a separate channel, a new channel that we have on Discord, conference videos as called. You can access the links there. We're going to keep the links exclusive to the conference attendees for two weeks. And after that, we're going to publish them to the general public. We are going to then, you know, in parallel to that, we are going to start talking to the video editing company. They're going to start and then take those videos, cut them and then produce edited videos. And over the next, you know, maybe two months, we're going to put them on YouTube. The YouTube streams from yesterday's intros, the stream links from yesterday, they are now turned into archives. So you can still access them. I'm also going to put the Zoom videos up online, like I did yesterday for all the other videos. The YouTube link for today's stream for the Microsoft track has changed. It changes every day. So, you know, you need to use a new link there. The link is in the announcement. And the final announcement that we have is we want to do a session today on organizing EP 2021. So next year, the hopefully in-person one. If you are interested in joining the organization, you have questions, then we're going to do it and ask me anything session in the open space at 1600 CST. And there's also a chat that you can see in the conference tracks called open space one. So if you want to, you know, raise questions by text, then you can write into that chat. We'll monitor that chat as well. Right. So if you're interested in maybe, you know, you saw what's going on at the conference, if you are interested in helping out maybe next year, then please join us and we can give an introduction there. Right. So let's see who's on. I saw a Christian wanted to say something. So Christian, please go ahead start sharing your screen. Let me just let me, I need to enable the screen sharing for panelists and also the webcam just a second. I think that I am able to do it. Yeah, you should be able to do it now. You can also enable the webcam if you like. Yes. Perfect. Good. So good morning everyone. Yeah. So the most active is print group as far as I heard. Yes. We are here again for a second day. So it's really cool to see that we had a lot of action yesterday and many contributions from even from people that the Spanish is not the second or the first thing. Well, yeah, not the first language. So just a little bit of background. This was kind of like motivated by the tutorial that was translated by the Argentinian community. Later on, besides doing it by hand, they decided to use these PO files, which is kind of like easier to translate and synchronize with the documentation from Python. And just to give you some dates, this initiative started in May this year and it took us, I think, one month to be accepted officially in the documentation. So now, of course, every time that you go to the docs, you can go there and select the Spanish option. So just maybe an update of yesterday's summary. Even during night, I woke up with many messages and written messages and we managed to even have less open issues, less issues without anyone assigned to it. And still the number of PRs that we are closing is really, really amazing. So thanks for everyone interested. We even got one extra person to the telegram. Yeah, so we have a guide here. I know it's a long link, but you can share the slides afterwards or just join the channel and check it out. In a nutshell, it's mainly forking, checking for issues and then submitting your power request. So everything is kind of easy. But of course, as you saw at the beginning, there are many countries involved. So usually we have questions of which word we use. What do we use here? Is it active or passive voice? We have some memory on it. So also, if you have some questions, you can go there and check it out. If not, we are really open to discuss any word or meaning in both channels. So a little bit of configuration is nothing else but a normal Python environment. And then install a couple of tools that you can see here related to working with PO files. And that will be it. So usually what everyone does is like you go to an issue with an assignment, you assign it, you create a local branch, you translate and you create a pull request. It's really easy, of course, this process. But it's really probable that you will find these messages of Travis complaining about something. So I just want you to be calm. It's totally normal because there are many common issues. So first of all is that we apply some wrapping to the file because sometimes we have long lines. This is one of the errors that could happen. The second is that maybe a word was not recognized. So this is really easy. We have some dictionaries in place where you can just add the word if it doesn't exist. Sometimes there are some mistakes or spelling. And the last one is that maybe you don't have the latest changes from the master bunch, sort of the 3-8 upstream branch. Still, if there are some questions, there is some frequently asked questions there, Link. And we are quite open. Here you can visit on the SprintPytonDoc channel or if not, we have an official telegram group. That would be it. Okay, thank you very much. Thanks, Raekel, for the audience. So next is Cuk. Right, right, right. Okay, so let me share the forever. I really love this slide deck. I'm using it again and again. So yeah, Terminus DB client Sprint. Yeah, so we have fun. Yesterday we also have fun. So these are all the reasons why you need to join. And yeah, maybe I will repeat again because maybe there will be newcomers. So we are open source graph database that actually work like Git. So we can do revision control. We're using this as a state data structured. So it's very lightweight. And the Python client is made for Pythonista, obviously. And for the Sprint, we have some documentation that is still, the tickets are still open. You can do it. And then you're always welcome to write more tests for us and also do some testing. We have people that say that they're interested in testing today. They have set up yesterday. So I hope that you found it fun today when you can really try out something and help us test something. I also created a new ticket yesterday that you could help us to implement a new feature that's actually a very straightforward feature and it will be fun if you want to contribute a new feature to us. And so yesterday, we have merged free pull request and we have someone found a new issue. That's great. And then we have free soft issues and a very promising PR on the way. And that's a really good PR. It kind of really pumped the test percentage really high up. And swags. And yesterday I mentioned, you know, you can contact my colleague Luke Finney. He's also in this, in this channel, you know, in this, this course server. So you can basically just give him a direct message and so we'll like arrange how to send you all the swags that we could send you. So yeah, so that's it. Thank you so much. Great. Thanks, Chuck. So you did make a lot of progress yesterday. That's good. Right. So who is next? Olive, Olive, I think it's next. Yes. Yes. So, so I represent the, the scikit-lan project. So I hope you can see the screen. So this is the machine learning library for Python, open source library machine learning for Python. So we started this print yesterday and we already had a bunch of very interesting pull request merged. So if you are new to, to this print, if you didn't have done yesterday, we prepared a small document to get started with setting up your dev environment and how to use the build tools, how to run the test, how to build the documentation and things like that. So there is a video tutorial and a text, written text tutorial also. So feel free to join us. So just a quick summary of some of the progress that we made yesterday. So there, there are a bunch of pull requests that have already been merged and we are reviewing the new set of active pull request. Actually, I just connected so I haven't had time to, to have a look at the details, but this is the things that I need to review this morning and just to show you one example of some, one pull request that was merged yesterday. So this was an old pull request that was started, started months ago that added some, some past reviews, but they were not fully addressed and the original contributor did not reply to the last comments since end of June. So one of the contributor of the, of the sprint, Amanda, started to, to, to reuse the old commit from the first contributor and addressed the, the remaining comments basically by adding a test. We had a discussion with Roman and other core developer and then Roman gave us approval. I did a review, I gave my approval and then went to bed and during the night Amanda fixed the remaining comments and another core developer of Cykit-learn in Australia merged the pull request tonight basically. So this is basically the workflow. So it's going smoothly and we, I'm very glad that we are going to go on today and hopefully with new contributors. Thank you very much. Excellent. So this is around the world development, right? So this is really working well. By the way, just a comment there. We are going to, you know, leave the discord server open, of course, so you're free to use the whole day until late, late at night, even, you know, Monday morning. If you're like, we're not going to shut it down anytime soon. We may want to put it into read only mode and at some point in the future, we're going to have to, we're going to have to see how, how that works and also want to archive the server in some way. Right. So there is one more candidate here. Zach, Zach, you want to go ahead? All right. Hello. I'm leading a sprint for hypothesis, which is a library for testing. And I thought that I would show you what kind of tool, what tests with hypothesis look like. They look pretty much like this. You have some imports. Then you say given, you know, some arguments and some what we call strategies. In this case, text and just the number zero. If we take those arguments and we try calling a function on them, we shouldn't get an exception. Except if you actually run this, you see that we don't just get one test failure. We get three separate different ways to get an exception by trying to compile a string as a regular expression. When you have more complicated data, you get even more complicated failure modes. And so for this sprint, I'm doing a combination of helping other projects write tests with hypothesis and working on hypothesis issues. So we have still eight open issues, seven of them waiting for people to come along and help us out. We have some documentation, some features and some internal bug fixes. And yesterday, we already have one new release thanks to this sprint. So if you're using hypothesis 5.22, the new feature was released late last night thanks to these sprints. So I hope you'll come along and keep working with us today. Okay, that's impressive. Thank you very much. So I think those are all the presentations. So maybe I can just finish up the intros. We're taking a bit longer here than scheduled, but that's perfectly fine. Let me share my screen. We already had the announcement. So just to show you the schedule for today, we had the morning announcements. We have the usual coffee break, lunchtime and so on. Then at 1500, we're going to have repeated announcements by Jason. So he's just going to take my slides and then repeat them. And you can join there as well if you'd like to again present your sprint. This is mainly meant for the America's time zones. Then at 17.05, we have the first sprint end-of-day presentations. And then at 22.20, we have the second one. And after that, it's really the end-of-day for us. We're going to basically then close down the webinar. But you can, of course, like I said, still continue working on Discord and continue using it. If you have a need, but so far we haven't heard any requests for that, for a larger room to show your show slides, show demos, whatever. Then you can get a Zoom room. You just have to call the organizers for help. And we can make that happen very quickly. Right. So final word, Code of Conduct. You all know so far we have not had any Code of Conduct issues. We'd like to keep it that way. It's actually very simple. Be nice to each other. Be professional and don't spam. Of course, there's a longer version available as well on the website. But this is essentially it. If you have any issues, you can contact one of these people here. They are on Discord, on Telegram, some on Twitter as well. Or you just reach out to ads.coc. And that's it. Happy sprinting. Right now, we're getting started here in a minute for our second afternoon announcements for those of you who are in Europe morning announcements, for those waking up and joining us from the Americas. And of course, for all the brave souls who are staying up overnight over in Asia, et cetera. This would probably be the late show. So hang tight for that. Hello, EuroPython 2020. Here we are on day four of the conference. Last day of the conference. It's been fun though. I do look forward to getting back to our normal sleep schedule though. But this has been absolutely awesome. This is also the second day of sprints. So it's our opportunity to build some really cool stuff with all of the knowledge we've gained so far. So yeah, it's the coffee break hour. So if you've already heard the announcements while I'm blathering through those again, you can grab a fresh cup of coffee or Yerba Matei if you've been listening to Niko's presentation. And we're going to go ahead and go through this here. Bruno, do you know if we're going to be having anyone represent their pitches or did Mark not do that this morning? I did not catch up. I don't know. He did. Okay, so anybody who wants, we mean to announce this in the hall, but any project who wants to represent, please do that. And then we'll probably just replay after the fresh presentations. At the tail end of this, we'll replay the video from this morning or the presentations from this morning so that anyone who is not able to represent can still get people who just did their project. So, right. So morning announcements for those of you in the Americas. Here, good morning. So, as you might know from yesterday, we had a big conference, more than a thousand tickets registered which is amazing. Attendees from over 69 countries, you know, we were expecting a smaller conference because it was online, but this has been awesome. This has been a lot of fun. So, Mark has published the conference videos, the raw conference videos to Discord. Those are actually published, published them to YouTube and he listed them on Discord. So, there is a, there's a dedicated room for that. I believe it's conference videos on the top of my head. Anyway, you'll see it up in the, it's one of the top rooms. The YouTube links have changed those to see the announcements. YouTube streams from yesterday's intros are also going to be added to the list as well. Also, later on today, a little bit of news. 1600 CEST, which if I subtract nine, that would be, I have it written down here in an hour. Thank you. I can't do these perversions. In an hour, we're going to have an ask me anything on organizing EuroPython 2021. So, if you're watching this conference and want, wow, how did they do that? Great time to come and find out and find out how you can get involved too because you can. This conference is run by volunteers. So, we are looking for more volunteers to help us with EuroPython 2021 which will hopefully be in Dublin. So, come find out more about how that works at the ask me anything session in an hour. That'll be in open space one. So, the schedule today, we are currently sitting right here at 1500 CEST, which is the Coffee Break and the Repeated Announcements. We're going to go for a little while longer for anyone who started earlier in the day and then we'll have an, what's called an end of day presentation. You can kind of think of it as a check-in. It's end of day for people in Europe who aren't going to be staying up super, super, super late. And then we're going to keep going from there for a couple more sessions and then we're going to have a second end of day presentation and this will actually be the end of, the real end of conference type of presentations. This is the last chance to present what you've done in the sprints. And that'll be at 2220. So, come to one or both of those. If your team is working and keeps working, just, you know, show up what, show what's happened and then you can show again later on. Just a quick reminder about the code of conduct as far as I know, we're still at zero offenses on the COC, which is great. Love the Python community for that. So, just a reminder though, in short, be nice to each other, be professional, don't spam. Pretty easy to follow. And this is for the whole event, including all the social channels. Well, we don't have a safe insult zone. Just be nice, period. It's, and it's not hard to do as evidenced by the fact that over a thousand attendees and issues would. If there is a problem at any point, we do want to know about it. You can contact us a few different ways. You can tag at COC and that's going to work the code of conduct team on Discord. You can also email COC at EuroPython.eu or you can direct message any of the members of the COC, which would be Valeria, Sylvia, Anders and Mark. Their names are highlighted in red under organizers so you can message them directly if you need their help. Their, their Twitter's are there. Contact information and the full text at the COC can be found at EP2020.EuroPython.eu slash COC. And that is all I've got for me. So do enjoy the rest of the sprints. Stick around for a moment because we're going to give a, if you're wondering what some of some of the projects are because we're going to give everyone a chance to pitch what's going on and what they're, you know, what the maybe not what they're whatever. So if you want an update, stick around and there's this contact slide here. So if you need to contact EuroPython, you want to find out more about the EuroPython Society that makes this whole thing possible go to EuroPython-society.org and you can also email board at EuroPython.eu or write to them at their address, go to BookSuite. Anyway, so thank you very much and let me stop my screen share here. Excellent. So who do we have up first? Great if I could see our total list. I send you the list on the Microsoft command. Okay. Yeah. All right. Let me, let me get out of that then. So I can actually see my discord. All right. Here we go. So perfect. Okay. So hopefully we got people from each of these here, but I'll just go through each of these and then anybody who wants to present from that team just, you know, raise your hand, Bruno will promote you and then you can do your pitch. So anyone here from SiteKit learn from SiteKit? Okay. EuroPython website. I know Mark was working on that, but he isn't. That's right. That's right. He did the other thing. Anyone from the website project? Okay. Well, I know we have someone here for this one, which would be the Python Spanish documentation. I want to hear what's going on with this because this one's cool. I think I can present, but I need Christian to share screen because I don't have the slides in my computer. I know Christian. Yes. Amazing. So in a second. Yeah. I think we can just say, what's our progress so far? So we are down to 132 issues. That number is probably not, it's not linear because we are also creating some. We are investigating some ways to have a bot to ping users with a pull request that is not up to date because we have a lot of that and maybe there is a review and we are waiting for some changes. So we are, it was really nice that we found a person that maintains the bot. It was participating in the conference. So we are working on that. Also working with some bot in Telegram to do some noise in the social networks every time and to send some greetings every time a person merge a pull request. Yeah. And now we are all down to 53 pull requests from 78, 79 that was yesterday. We have three new persons in the telegram. Yeah. And we are going to keep working. I would say it's going to be more activity now we're starting now because these people from the medical training. So from Latin America in particular. So yeah. Thank you. If you, everyone has a question plus contact us. Excellent. Thank you, Nicholas. So yeah, if anyone wants to help out with that if you speak Spanish and any, to any meaningful degree and you want to help out translating that or you want to help build those bots. Definitely check out. We'll check that one out. That's python-doc.es on discord. Okay. I actually don't see anyone else with their hands raised, but I'll just go through this. We got scan API. I call out your project. You want to present just raise your hand. Seaborn API. Python packaging. Strawberry graph QL. Diamond Quest is mine. So I'm not going to bring up my slides but Diamond Quest is a game project where we are building an accessibility first math game. So it's a game that is designed specifically for people with disabilities who would have to use the computer with something like a head pointer to be able to have a game they can actually enjoy. Accessibility first means that instead of building a game that the average computer user can play and then adding some accessibility features on top of it, we're building the game to be accessible first and foremost. That permeates all of our design decisions and then from there making it fun for everyone else as well. So we're working on that and if you want to help with that it's a side-scroller platformer style game. So we're doing it in Pygame if anyone wants to help out with that. So Jason, what kind of skills you need to have for participating there? You know, I think it's one of those things where we have a bunch of different sort of tasks. So there are some things, you know, if you know Pygame, that's a huge advantage of course but you don't really have to know Pygame to figure it out. If I'm totally honest, I'm building this Pygame because if it's suitability for the project, I don't know Pygame. I'm learning it from the docs as I go. But there's some trickier issues dealing with like timing and key presses and game tick rate but then there's some easier things too. There's some stuff with layout. We need someone to finish the code for generating the math problems. So there's variety of things. So even if you don't know Pygame or not super familiar with game development, there's still stuff there. So it's a very, very good project if you have some proficiency with Python but otherwise don't, you know, may not know a ton about everything else. It's a good place for like early intermediate, you know, late beginner, early intermediate. Okay, fine, it's really different. Yeah. Okay, do we have anyone here from Commitizen? That one's, that one's, I watched his presentation on, I think that was on Friday. That is a full set of tools. If I didn't have my own sprint, I'd be over there. So, but I don't see anyone for that. Terminus DB. Chutes not here. Kedro, Borg backup, Epic and Hypothesis. I think Hypothesis is out of the time, so I don't know what time is now in Australia, so. Okay. All right. So basically, you know, these are, we'll just replay the videos from earlier, honestly. So we can use those pitches to find out more. But yeah, cool. So I think we're good for now. So again, everyone remember that we have that meeting in 40, now it's 45 minutes from now and open space one, ask me anything to learn more about the Euro Python 2021 planning process and how you can get involved. And then we have our end of date, our first end of day presentation and our second day, end of, second end of day presentations coming up later on. So yeah, let's get back to, let's get back to sprinting. If you got your projects already, dive on in. If you're still wondering, stick around. We'll replay the pitch videos from earlier. So thank you very much. I can share my screen. Do this. So next, next one is Strawberry GraphQL and then is the Diamond Quest and Commit 10. So please be ready. Okay. Does this work? Yes. Yes. Yeah. Okay. Cool. So we're doing Python packaging and we are a group called PyPA, Python Packaging Authorities, which are, we make decisions on packaging stuff like for PIP and other packaging like pypi.org. And we, if you look at our Discord, there are some links in the description and you can follow to get some ideas. And especially if you take a look at a wiki page on python.org, there, sorry, there's a list of people that should be available during the sprint. I believe most of them are in North America. So they should be joining much later. And there are a list of projects that you can work on. And then there's a Disgust of Python.org link that has the, like you can use the discussion to link to which one, which person is responsible for which projects. And for myself, I am Suping. I work on PIP and PIPM. So if you want to work on those projects, feel free to ping me on Discord for review. Yeah. I guess that's it. Thank you. Okay. Thank you. Thank you. So next one is a story. Is anyone in the room? Yes. Do you see my browser? Yes. Actually, I'm not the coordinator for this sprint. Patrick would be available soon. However, just to show you what this project is, what the project is about. It's a GraphQL server that instead of using the scriptors as in most of the software that is dealing with schema. Here we are using type annotations. So our way of defining schema is, is coordinated with type annotations and static checks of the types. And this is a quite young project. There was a big refactor lately. And what do we expect? There is a number of issues here, which require your work. And also there is missing documentation. So if you want to learn more about GraphQL, more about how can you use type annotations in various ways, then please join the stream. Thank you. Okay. Thank you. Thank you very much. So next spring, I think, took your way to present. Yes. Yes. So diamond quest is not my project is actually Jason's project, but he's actually in the American time zone. So it's, so it's not. So yeah, he's not available right now. So I'm trying to go to the screen. So yeah, I hope you can see the slides. If you can maybe like Nicholas can tell me. Yes. Yeah. So this is diamond quest. So can I, okay. So I have to use. Okay. So this is like a PDF. So yeah. So this is an accessibility first performance is a game that actually like designed for people who got like disabilities and it's a bit. So if you like that as a static, then that's great. And also it's a math game is reward driven. And of course it's open source. So it's Jason told me that it's actually inspired by a friend that got a celebrity parsley. So basically the like his friend can only move the heart. So we tried to make a game that is actually, you know, so he's like, people like his friend can play and also it's, you know, it's also fun for everybody. It's not just for, you know, people with that disability. And so there's all these features that is actually going to be implemented in the game. And also it's a math game. So it's a self driven and also it's rewarding. So it's like, it's going to be fun rather than like very, you know, frustrated for people who like, you know, try to get the math right. And, you know, so it kind of help people who maybe like also a scale of math, like get math anxiety can also enjoy learning math. So it's a bit. So you see that like a lot of games is actually cute having a bit and also got a keyboard interface. And also there are some like animations as well. The most important thing is open source and it got, you know, a DS, a BSD free license. And it's also, you know, free for everyone. And they will be always this force. So yeah, that's it for them. And yeah, so now like this is the sprint. And then, you know, so I think the sprint details actually in the, in the, in the, in the channel, in the channel. So you can join the text channel to kind of seal the details, what you have to do to get started. And Jason will be online, you know, when he wake up in his time soon. So, you know, please don't hesitate to go there to leave, you know, any questions or comments there and Jason will be getting, getting back to you later today, but you can get started. There are some instructions there posted already. So yeah. Awesome. Thank you very much. So Santiago from committed send is the next one. Hello, can you hear me? Yes. I will share my screen. Can you see my screen? We can. I use in the documentation. This one. Hello. Good morning. So, in this spring we're going to work on committees and which is a tool to automate the, the generation of the version of your project and the change law. And it has a lot of features. You can read them in the documentation. Some of the comments are BAM, for example, you just type BAM and it will bump your version and it can generate as well. We have a selected many issues. They are labeled as a Euro Python in the repository. And I'll share in the, in the discord chat a link explaining about the, how, how it's the code made or set. Basically we, inside the committees and folder, we have the commands where each command has its own file. And then in the root, there are like different files specifically for, for each part as well. Then there are some recommendations, the highlights and the workflow. And the, then we have a two branches, one for breaking changes and a call next and normal changes called master and then a lot of resources. And that's it. The channel, I think it's called the spring committees and tools. And I'm going to be with the Liwi, who is the other a maintainer, but he's in Taiwan. So he's not connected yet, but you can already join and start the coding. That's it. Thank you. Thank you, Sandy. Yeah, it's me again. Cause this is, this time is my own project. Okay. So let me share my screen again. And yeah, so Terminus DB clients sprint. So I, I hope you have seen my talk yesterday and well, Terminus DB got a Q mass cut as well. I forgot to show it in my slide that yesterday. So the first thing that I want to show you is that, please meet the team. So you can see that this is actually similar to what's happening yesterday in the show show. And that means that we all love parties. So we are cool people. You want to, you know, one of the selling point here. And also we are, you know, in case you don't know Terminus DB, then we are open source forever. This is the most important thing. I put it at the beginning on, well, we are graph database. So if you're interested in database or anything like, you know, data related and this may be a project for you. We are a lightweight database, you know, we use sustained data structure to store all your data. So it's very lightweight. And also we can do revision control. So basically if you don't understand what that means, it means that like you can do what it does. So for the, for the Python clients, obviously this is made for Python sisters. And the sprint today, it will be super beginners friendly. I'm trying to also run a beginner's workshop. I think I would coordinate with the organizers whether I would run it in this room or maybe in other rooms. So stay tuned for the announcements. And so for the sprint for, for Terminus DB clients, and it will mainly about documentation. So if you are scared of doing too much coding, then that's easy. And also writing some tests if you want to, you know, challenge yourself a little bit more. Or even like if you don't want to contribute to anything, well, you can just download it and play around. Like that will be user testing for me. I actually have tickets for that. So and the most important thing is swag. And we got actually very, very nice swag. My colleague Luke actually say on the channel about like if you how, you know, if you successfully create some contribution, then we can send you swag if you contact him and let him know that like where about you are and we can send you, maybe not the cup is too difficult to ship and it may be broken, but like the socks, the t-shirt, the stickers, it's easy to melt it to you. So please consider joining us. It will be fun. Awesome. Thank you. So nice. Yeah. Hello. Hello. Good morning. Yeah. Perfect. So hello, everyone. Good morning. Welcome to Python sprints. My name is Lais. You might have seen me around or be hosted by me around. One of the, one of the talks. I hope you're having fun. And well, so I'm, I'm a developer advocate and I will be running this print in our room today with my credit, my credit manager, manager called Yetunde. So basically what Kedro is. So Kedro is a Python development framework. That helps you view data pipelines. So we have a template that is based on the cookie, cookie cutter data science and it implements software engineering best practices for data science and machine learning models. So it's basically, it has a very modular kind of style to it. So it, some people actually say that it kind of looks like the reactor, the jungle of data science. So what we're trying to do with Kedro is basically make sure that data engineers and data scientists collaborate in a very peaceful and effective in effective way. Making production ready code from the gecko. So we have a few issues here for you already. We are going to be there's issues from, for every type of difficulty. If you're a newbie, I would more than happy to help you learning how to make your first full request. And yeah, so please we're waiting for you with this list of questions and just join us. And we also have flags for you. So, yeah. Thank you guys. Thank you. So next project is the ball backup. I think Thomas is with you. Yeah, good morning. Let me share my screen. Where are you streaming from? I'm from Germany. So, okay, is my screen visible? Yes. Okay. So this is about a board backup sprint. My name is Thomas Waldmann and I'm the project maintainer. And so what's boring about it's basically a backup software. So you can back up your all your files with it. And the special thing it's a deduplicating backup tool. So you can save lots of space. And it also does compression and encryption. And it even authenticates all your data so you can make sure the data is still as it was when you back up did. So some of the features. Yeah, space efficiency. I already mentioned you can back up to untrusted storage servers because you can always verify your stuff is okay. There's a wide range of compression levels. We support lots of platforms except the windows. Windows support is still work in progress. There's a command line interface and also there's a separately available graphical interface named Walter. And as a backup storage you can either use your own server or your own USB disk or you can also rely on some commercial offers. The code is mostly in Python three. It's completely in Python three. And the Python code is most of our code. And a little bit of code is also in Python. Some of it is in C some own hash table implementation. So we need less memory. And we also use some third party libraries like message pack open SSL and some compression libraries. These are the tools and services we use. We use git. We use pie test. We use things. The continuous integration runs on Travis and we use way grand virtual box for platform testing. We do bounties using bounty source and the documentation is hosted on read the docs.org. Some of the sprint topics is if you are completely new to the project you can get an introduction to the code base. We want to debug analyze and fix some issues. If you like you can also work on the documentation. And what would be especially useful if you use some unusual platform like DSD unusual for us or mega s or open Indiana. You could help us improving the compatibility to that. Or you can work on whatever you want. Just join our channel. And we have a GitHub issue about this print. It's issue 52 51. And if that sounds interesting just join us for the board backup sprint. My name is Thomas Waldmann and you can find me in the board backup sprint room. Okay, that's it. Okay, thank you very much. Good luck. So Epica true or Epica is the next project but I think no one is here. And also there is no information in the channel. So I have the feeling that there is someone from a different time zone. So I'm going to skip that one. And that means the hypothesis is the last project. And I think it's over here. I am. You'll be able to hear me. Yes, perfect. Excellent. Well, hello from sunny Australia. You might be thinking, what is an Australian doing at Europe? But I figure if we're European enough for your vision, we're European enough for Europe. So I'll be running a sprint this morning while I'm still awake. Thanks to time zones on hypothesis, we have a tool for what we call property based testing, which is a style of testing where instead of saying that this specific input leads to a specific output, you declare what kinds of inputs should be allowed. And hypothesis tries to generate an output which makes your test plan. This might be easier to explain with a little demo, which is also going to be a sneaky preview of a thing. I haven't a pull request. So you should be able to see my terminal now. And I can actually ask hypothesis to write me a test. Let's try testing the read.compile function, which compiles a regular expression. And hypothesis will duly spit out this test code for me. So if I pipe that into a file, I can then run PyTest on it. And PyTest tells me that this is just unsatisfiable. And that's because I haven't actually told hypothesis what to generate. Because the remodule is in the standard library, it doesn't have typekits, so we don't actually know what the pattern should be. So let's substitute in something for the pattern. If we instead tell it that the pattern should be text, that is any unicode string, and then we run PyTest again, we discover that there are actually a whole bunch of different exceptions we can get if we just try to compile arbitrary strings as regular expressions. And personally, I wouldn't have guessed that there are so many different ways to have an invalid regular expression pattern. Specifically, what would you do if you want to join in with our sprint? We've got a couple of things. There's a hypothesis tutorial. If you just want to learn how to use it, you can work through that and ping me with questions. And I'll help you out as you go through it. If you want to contribute to our documentation, add some new features, fix some internal issues and so on, we've got about 10 of those open, listed in our meta issue that you can see. And I would particularly love it if someone with Django experience wants to look at that. Because we have a cool feature where we can take an arbitrary form or a model and generate instances of it. And it would be great if we could leverage the validators as well to make that better. Or finally, if you're sprinting on any other project, if it's open source, I would also love to help you write hypothesis tests for those other projects as well. So if you want to do two sprints at the same time, we can totally do that too. Thanks very much. Thank you, Zach. Thank you. Thank you for a hypothesis. So I think that was the last project. If I were missing someone, please raise your hand. Otherwise, I think we are done. Sorry. So it's just a comment I want to say. Mark already mentioned it, but we are planning to use this score for the sprints. It should be more easy to manage for everyone because you just can keep the score open and the channel will open. But if you have more people or you need something that this score is not providing, please contact me or contact our organizers and we can give you a Zoom room for the sprints. Nicolas, I just wanted to jump in because I think I just want to give you a very quick intro in how to actually make the video work on Discord because that may not be obvious. You should see my screen. Can you see my screen? Yes, OK, excellent. So what you see here, this is the sprints category. These are all the sprints text channels. And then down here you see the hashtag. This is for text. And then you see these speakers here for the audio channels. To enter these, let me just exit again. OK, to enter the audio channels, it's very easy to just click on it. It works like this. And then you're a member of this audio channel. You can only be a member of one audio channel on Discord. So if you click somewhere else, then you just switch like this. You can also drag and drop yourself into some other channel networks as well. Now that's audio. Audio is easy. If you want to set up your audio devices, you go here to the user settings. You go here to voice and video. And then you can set your input-output device for audio. Down here you can set your video. I chose this virtual webcam here because you can only have one webcam on at a time. But you can configure others that you have here as well. OBS also works if you want to use that for presentations. Now if you want to enable your video, you go here to the... you can click on the audio channel. You get a window that looks a bit like the zoom window. And then you see down here the controls. You have video and screen. So you can do screen sharing in here, which works a lot like Zoom does. And you can also enable the video here. Click here and then the video goes on. There's something strange in Discord. It seems to mirror your webcam automatically. So that's something to be aware of when you're showing text. For example, here you see everything mirrored. It's a bit weird. I don't know how to switch it off in Discord. Maybe there is no way to switch it off. So just something to be aware. That's all I wanted to say. And this is the famous disconnect button that's not very intuitive. So you can click on this one to leave this or you can right-click on your name and then... Actually, it doesn't. That's interesting. Okay, so you always have to use this button down here if you want to leave like this. And you can also share a screen. I think you already mentioned that. Yes, yes. There's a button there for sharing a screen as well. Okay, so we want to try to have you use Discord for most of the things because it's very easy to use for you. You don't have to ask us. You can just set up everything yourself. If you have a need for something bigger, we have I think around 15 or so Zoom licenses available so we can set up additional rooms on Zoom and Zoom can handle 300 participants if you like. So this is for scaling up. Right, that's all I wanted to say. Thanks. So I miss, in the least, Oliver is here for the SkiTea Learn project. So sorry, Oliver. I'm sorry to hear you. Yes, can you hear me? Yes. Okay. So here I'm... Hello, everyone. I'm here to present the Scikit-learn Sprint. So Scikit-learn is a machine learning library in Python. So we use NumPy, SciPy, and SciTen a bit and also Python programming. So we prepared for the Sprint, a small Getting Started sheet that we linked in our channel. So with the repository, the main documentation for the developer version and some Getting Started instructions. So basically those are instructions from past online Sprints that we had recently and there is one that is mainly like some kind of video tutorial to get started contributing with Scikit-learn and one, actually, I don't have the link, it's there, which is... No, I made a mistake. Okay, I need to fix the link, which is about a text version if you don't like videos and if you want to contribute to the Scikit-learn project, so ideally if you're already a user and you found a bug or want to improve something, then feel free to open an issue and we can discuss how to fix it. And otherwise, we have labeled in the issue tracker some issues that are either required some help and some of them are good first issues for first-time contributors. They could be documentation or some simple code change and things like this. There are also some old pull requests that are stalled, so if you're a specialist of one of Scikit-learn cluster ring or something like that, our user and you want to help move those pull requests forward, you can feel free to take over those if they have not been updated in the last couple of months, for instance. All right, so let's discuss on the channel directly if you need it. Thank you. Okay, thank you very much. I think we are done. Mark, anything else? Yes, I think so too. I think we can now start. Can we have a beginners workshop here if people want to, you know, haven't made any contribution, haven't been to any sprints, they could stay here and give a shot. Good idea, sprint intro, yes. So let me just play the applause because I like playing the applause. Thank you. Okay, so Tuk, do you have anything to show? I have slides, just a quick slide deck and I have some hands-on exercise for the beginners and I also created a text channel it's called beginners help desk in the sprint category, so if you have any, you know, questions about Git or pull requests you can ask me there and so, yeah, if you have an experience in sprint, you know what you're doing, you can basically start work on the project that you want to work on and someone asked what time will people show their work? So there's an end of, you know, end of day sessions there. I think maybe we can coordinate that but basically it will be quite improvised so stay tuned to the channels. I think we would make some announcement there. So, yeah, so I would just share my screen now and here. Okay, so, yeah, so this is actually a reuse some slides that I've done before. I've run some open source beginners bootcamps so people found this helpful so I hope that if you're new to open source if you're new to, you know, so what, you know, contributing to open source or even you're new to GitHub that like I am here to help you and so I'm check, you know, I don't want to spend too much time because like I think you have seen enough of me today so yeah, I organized a lot of things and I have a channel for beginners. I actually do have a Git tutorial that I've done on Twitch before. It may still be there, it may not but I can share the link of the YouTube copy there if anybody wants to get more information about Git I'll share in the beginners channel. So if you wonder like, okay, I just come here for your Python and I try to stay as long as I could because what is this sprint open source thing about like maybe you have no idea what this is you just like use Python for work or you just started to use Python so you may have like no idea about like so okay, what is open source, you know so I think open source software and I won't be as good as, you know, explaining as this video so I'm just like playing this. I think I hope it's okay to play this video I don't know whether we're streaming or not but this is actually a YouTube video from Intel so if that's okay I'll just play it. Open source software is sorry I start again Most people understand that open source software is software copied for free What's less understood is how the potential chaos of all these copies can be transformed into a collaborative whole Let's break down how open source works using a family cookie recipe as a metaphor we can all relate to Just like code, all recipes start by somebody writing the original version In this case, Grandma May has developed a delicious cookie recipe She shares it with her family telling them they can use her recipe as long as they follow her rules In Grandma May's case anyone who bakes cookies with her recipe has to credit her as the author and if they make changes to her recipe she has to be allowed to use those changes in future versions of the recipe The same thing happens when someone writes and publishes an original version of open source software They put rules called licenses in place so that others can use and change the code they've written as long as they follow the author's license Grandma May's recipe provides her family the place to start that they can customize to their own liking Aunt Maria decided to add chocolate chips to her batch of cookies In software, this departure from the original code is called a branch Aunt Maria's change was such a great success with everyone who tasted the cookies that she asked Grandma May to add chocolate chips to her original recipe At this point, Grandma May needs to begin acting as a maintainer after the integrity of the original recipe and deciding which changes she will incorporate In this case, Grandma May agreed that the chocolate chips were a good addition and so from then on Grandma May's recipe included chocolate chips Aunt Maria is now a contributor because she has contributed something to the recipe In open source software development this process of incorporating a change or patch into the original code is called up-streaming because it's flowing back to the original source If the original brand of chocolate chips becomes unavailable Grandma May is responsible for updating the up-streamed chocolate chip patch with a new brand because she accepted the patch The benefits of incorporating your changes into the original recipe are pretty amazing leading to the popular open source motto up-stream early and often The sooner you up-stream the sooner the community can back you up not only by maintaining the recipe but also by testing it in as many configurations as there are community members using it Uncle Miles went out on a limb and added peanut butter and nuts to his batch of cookies His wife and friends all love peanut butter so they thought his additions greatly improved the original recipe But when Uncle Miles tried to up-stream his nutty changes Grandma May, who detests peanut butter used to add peanut butter and nuts to her recipe Uncle Miles resolved to move on with his version of the recipe with no plans of merging the two again at any point In open source software development a permanent split like this is called a fork Grandma May's recipe is getting better all the time as people continue to contribute Her family gets to learn from and enjoy the latest and newest cookie recipes as they are created As Grandma May's family grows and her recipe is shared outside the family more and more people will become contributors As you can imagine things could get pretty complicated for Grandma May as the maintainer of the original recipe with more contributors The same is true for open source software More contributors and more versions of code make it essential that we have a way of collaborating on changes This is why we need the structure common language and roles we just talked about with our recipe example Now let's recap really quickly Someone writes an original version of the open source software They set rules around how it can be used and changed called licenses This gives contributors a starting point to then branch out from and make changes or patches Some request their changes to be upstreamed to merge their new version with the original version If the maintainer decides to incorporate the change it becomes part of the main branch and will be maintained by the community even if the contributor stops being involved in the project Sometimes software is taken in a direction that we know will not be incorporated back into the original version This kind of permanent split is called a fork Open source has the potential to be complicated because it's created by communities of people But these ways of working manage those communities making it possible to benefit from new versions from an authoritative source, the maintainer Actual products based on open source can be made up of dozens even hundreds of recipes like Gram-a-Maze Which is why having a disciplined way of managing change is so important In open source the possibilities are endless but we need the rules and roles to keep things organized That's a very good video I love it, I play it all the time every time I give this presentation I also take up a little bit of history when did open source started According to Wikipedia it started with a person, Richard Stortman and then in 1980s he actually wanted to access some code for his printer but the source code is not open source So there's no open source at that time and then he can't access the code So actually he started to started this open source thing because maybe we think that it's a good idea that some of the code should be accessible for everybody So I started this GNU project and you may have heard of GNU a lot because they are licensed GNU licensed that it's basically one of the open source license, one of the first open source license, a general public license So I think now there's other versions as well because it's involved, I think there's a version free now I'm not so sure, but you'll see that everywhere So why do we like open source? Well we like open source The reason is that it's free It's also part of why I love it as well but as you know it's more than that it's not just means that it's free it also enables some small companies startups and even if you're a one-man company or one-man project team that you could easily access to a lot of tools that could make your work easier Also you can use that knowledge Actually one thing I love about the Sprint is you learn so much by contributing to a project You can see other projects code to see people do things differently and you can learn from them I copy a lot of for example the testing setup or the packaging setup that some other project user I learn so much from them Also encourage collaboration I hope that you all love collaborating because you're here, you love coding with people We can actually use this course You can do lots of peer programming today I do that a lot within my company so I hope that it also works fine today Also now I think there's a mental exercise You don't have to tell me if you want to type in the chat, that's okay Do you use any open source software every day to your work? Can you name them? Now try to think about what you're using day to day is actually open source Who is involved in open source who make this all happen? Actually everybody can participate in open source including you and me It's not just someone as smart as some of the maintainers As long as you follow the rules because in the video I also mentioned there are rules at the end that try to maintain the whole system The license of course I follow the license Sometimes some license is like you can use whatever is free but some of them may be restricted to non-commercial use so make sure you check that Also there are code of conducts most of the time for projects just to make sure that everybody is nice to everybody and they can be online or making for requests or commenting So you can help actually sometimes by just being the user like today I have some tickets for my project that is user testing basically you don't have to write any code for me or write any documentation for me you can just test it and let me know if something breaks But one step further you can be a contributor you can be like writing code you can contribute to the project by upstreaming this in the video and eventually you may actually what happens to some people is that they become a very they contribute a lot they contribute consistently and then maybe people invite them to be one of the maintainers in the team or you go for another path you have managed the community you help to promote that project you help to make sure that everybody's the users are happy everybody's nice to each other so yeah there's a lot of roles you can play in open source and everybody can do something if they want to you can decide for yourself how much time you want to involve in the projects so where can I contribute to open source well actually anywhere you like we are now doing it online that's fine but normally we will have to sprint after the conference so people can still stay rushing back home they can still stay and work together but also there's other places like Mark has already showed us at the beginning that there are hackathons there's events that are organized by people I actually organized the London sprints I didn't start it actually someone actually Mark Lausier the maintainer of Pandas I started it but I just like helped to keep on working on it but you can start your own actually you can start your own meetups to organize sprints so conferences like your python we have this tradition of having the sprints after the conference so if you go to a conference try to see if they have a sprint see if you can stay maybe one or two days behind to just do work in the sprint on private sprints you can actually share your friends and just contribute if you want to and we make friends in this conference so I hope that you can find friends that also love doing this together with you so how can I contribute and I have actually a slide deck that I think my friend Lays also shared before you can actually this slide is all yours you can just go there if you want to do your work if not you can find it on slides.com and put my name there I will share it again in the beginners channel as well let's test if the link is still working okay that's good it's still working so it's actually a step by step guy that you can make your first pull request if you have never done that before or if you have never you know I know lots of people they have already like already used to get in their work but the steps may be a little bit different in open source projects so this slide actually all the steps are quite standard for a lot of projects of course there's some minor differences so please if you have doubts ask the maintainer of the project that you are working on but as an exercise you can follow all these steps to make your pull request to a dummy wrap hole I don't own I just like hijacked once the wrap hole but they welcome people to use it as an exercise to create a PR so I hope you found this useful oh by the way this like arrow bracket thing it means that just use whatever name you see fit so replace this whole thing with your own name not your name but like the name that you make up for your thing you know and all these you know all these things are linked you know if it's blue and sometimes you can click on it and find more information so I think that's it there is a text channel that's for beginners I would post all the resources like including the git tutorial that I had and also this make a first pull request hands-on exercise I'll put everything there you can access it and if you have questions ask me there I think it's sometimes like I don't mind people you know ask me like individually I'll give you a really really shine but I encourage people to ask you in the channel because then everybody can learn from everybody so I think that's it and I'll be staying around you know not all the time in the sprint but I would be you know most of them I will be online and keeping an eye on the chat I may be you know sometimes going out to do a little bit of my own personal stuff but I would be staying online flow this two days as much as I can so that's it for me and I think there's one Q&A and oh yes sure the slides would be all on the text channel of beginners workshop so you can find it in the all the sprint channel you'll find one that school beginners help us I'll put all the materials there so that's it for me you're muted are you saying something so hello this is going to be the end of the day session it's not the last one we're going to have one more later please people that's going to present about the world they did in sprints raise your hand so we can promote you to the panelist I really like your background Elise I knew I was honoring you I was like well you made it it's the closing session I'm going to log out for today after this so I thought it would be nothing more more suitable echo where's your python island logo disgraceful disgraceful what's this that's true I did the flag that lice is using so maybe I participated yeah he made it he made it the first time that we did it up together I said I wanted to do like a background to integrate everyone and he's like yeah sure give me two minutes so he did it I was saying that I wanted to do it for like a week and he was like yeah give me two minutes so he didn't need two minutes okay so everyone to be a panelist people is going to be presenting here so please raise your hand Jason um I'm missing now everybody's drinking mata yeah that's oh please not okay I have a few I know drinking okay welcome this is going to be the end of the day for the European time zone so people can why they were working on so I think there was a lot of things down and next to this one is at 10 p.m. Europe time is going to be the last one so for for the Americas and Latin America etc so I'm going to check my list here so the first team in the list is so first automation something happened with the seaborn api but no one was working there so yeah it was a shame because I wanted to see who it was scikit learn is the first one in the list yes yeah thank you so you're ready to go let me just show for the pull request that we emerged during the script print so I really appreciated this sprint so thank you very much to all the organizers and the people who contributed so we merged like many pull request around 10 I would say around half of them would be a good first time contributors pull request like fixing the documentation a little more deeper pull request in the source code that involved understanding issues and existing pull request and taking over the code fixing addressing all the comments by the reviewers adding new tests upgrading the documentation and sometimes the examples and also it was a good opportunity to do some per developer programming sessions and per debugging sessions using discord so it was very productive I would say so overall for the scikit learn project we improved some clustering algorithms fixed incorrect results improved the performance of for instance this calibrated classifier tool to be able to run in parallel fix issues on specific operating systems like errors that only happen on windows for instance and things like this so I think it's very useful both for the future users of scikit-learn so the future release of scikit-learn and also for the contributors and the community dynamics of the project so thank you very much again to everyone involved and to this opportunity to get this print online thank you Bravo so next one is a autopython website I know Mark if you are going for Stefan I think Mark was working for autopython I was working on videos yesterday and basically I uploaded all the videos to YouTube made them available today I worked mostly on the feedback form together with Reiko so did not really work a lot on the website but there are some people who have been working there I saw that didn't really participate much in that sprint and they did you know work on tickets and put in pull requests and did reviews and discussed things so there was a lot going on and it's moving forward which is nice so I see Daniel Reyes here for example who did a lot of work I see Juho Wiegmann who else Reiko is there Stefan worked on a couple of things yeah so Stefan is not here because he is doing other things Anders was commenting there as well yeah that's it for the thank you I hope I am nice for sure we are going to see more features next year and then is the Python Spanish translation of the docs Nari hi hello can you share my screen where are you streaming from Nari where where are you streaming from I'm from Colombia nice yeah well I'm going to show you a summary of our sprint we have different people from different time zones from South America to Europe and I'm going to show you the metrics right now well before the air python we had 149 open issues and right now the last two days were some productive we have 131 open issues right now 79 PR open before the air python and right now we have 54 request open that's like 25 in two days that's awesome and before the air python we had communication channel on telegram and we were 93 people on telegram and right now we are 96 people after all this air python sprint we had this channel like the first communication channel and we invite you to join us if you want it if you're interested to join us in the translation and lastly the most important we had an idea from this sprint to improve our telegram bot to automate reminders from github so thank you very much thank you she's the best reviewer that we have next team is sorry I miss Pascanapi I've not seen Camilla here so I would expect Camilla to be in the next session probably so next one C1 is not here python packaging anyone here I think that's enough so we'll move to the next one Strawberry GraphQL also so Jason, diamond quest yes sir I want to share my screen here I've been working on some stuff here so we have the beginnings of a menu none of these are interactive yet but this actually took a lot to get this much so because you know we're dealing with pie game so we have that we have the beginnings of the menu and then so you saw last time probably if you're watching our wrap up last time is that we have this white square that was zipping across the screen no more zipping it is now moving at a much saner pace when I'm holding down the key there are a couple of bugs with this and there is a pull request we haven't landed that will add gravity so it'll do that but we don't have yet half that so that'll be coming soon but that is actually a good beginning because once this is in place it's a matter of adding the artwork largely and then start adding the player block so that is that is actually some pretty good progress for today's sprint thank you to everyone who helped out with that congratulations congrats so comitted san tiao is going to percent I think yeah hello I'll share my screen share can you say it well yes so we closed a lot of issues it was mostly really and me the maintainers closed 10 issues which is 33% of the total issues now we have only 20 left and we released a lot of versions everything automatically it's really nice and 2.0 is ready it's finishing a few details but it will be released probably or tomorrow I have a quick demo because now it's a super smooth process basically we install a comitted san this is an example folder and a git init so the repo is initialized we create the comitted san file specifying the current version and here I create a commit again a new feature another commit for employees and we create the changelog just a single command now we see we have a changelog file and this is how it looks and now we are compliant with conventional commits 1.0 so here I'm making a breaking change so we bump and we have a major release and this is how it looks it says there is a feature and this is the information about the breaking change and the explanation about how to do it and that's it, thank you thank you cool, thank you wow so took with the terminus db client right so let me share my screen and so this is the statistic so far this is not a very accurate statistic because sometimes I lose track I just try to count everything so we have nine merged PL three new issues five solved issues and then some of these promising PLs already merged so this is not accurate like I said it's not accurate really good progress today and thank you so much for everybody who has contributed and as promised we can send you slacks please contact Luke I'm slowly closing down myself I would still reply to message but not as fast as before but also Kevin is also online so if you have questions just ask and I will come back to you eventually or just ask Kevin so also we have our discord community if you want to join after the sprint you can also join I can send a link in chat yeah awesome cool so I think lies with Kedro is the next one you are mute lies yes yeah perfect so we got so yeah for Kedro sorry so we got 10 issues done kind of so we had some late contributors some late joiners and we still have some PRs in progress some stuff in review for engineering tomorrow because I'm going to be very happy but we also got 5 issues done so in Kedro we had 10 of them that were actually like started and were super happy because that's like a third of all the issues we had and it was awesome it was really really cool to be part of it was my first sprint it was the first time that I'm running a sprint I participated in a few before but this was super cool so I wanted to end this out with the sentence that is on the front of the Python website saying that great software supported by great people in Python is no exception for user bases enthusiastic and dedicated to spreading use of the language far and wide and our community can help support beginner to expert and that's the ever increasing open source knowledge base so I want to say thank you to everyone that contributed to open source and contributed to the community this is me logging off pretty much I'm going to keep replying messages as well but maybe more like tomorrow morning so I wanted to say thank you and I wanted to say it was an honor to serve the community and to host the sprint and for everything else that everyone has been doing it was a pleasure it was an honor and thank you thank you guys thank you very much so next one is I'm not sure if we have Thomas Thomas can you raise your hand if you are here I will skip and maybe he's joining later Oliver from Epica also I think we have other Oliver okay and the last project is hypothesis but I would expect hypothesis to be later because just in case I'm checking if anyone from hypothesis no okay so I think he's still sleeping maybe it was someone else who was working okay so next end of the day session for the people sleeping is at 10 pm europe time jayton is going to be hosting that one yeah it was really nice to see all the projects everyone was working on thank you very much for the organizers and for the european society for hosting this awesome conference really quick and that is for anyone who might not have thought of it a lot of these projects it's great to have help for two days but there's always stuff to do so if you're enjoying it if you found a project you like working on stay in touch with them get plugged into their development platform you're already basically on board you've done some coding so stay plugged in if you like the group if you like the project I know all the project maintainers would appreciate the ongoing help with the code or whatever you have and the discards are going to stay for a while as well so whoever wants to like keep discussing things there or maybe I don't know get the contacts or keep doing some more contribution open source contribution I think we're going to be continue to reply messages I know that Jason and Chuck use to talk a lot as well by the way I rarely use it for being a parent discord expert I rarely use it actually yeah you are the owner by the way the easiest way to get in contact with Chuck is call her in discord don't call me that's only for you Lace otherwise my phone will keep ringing no I'm joking yeah you can send me a message I will try to reply to you if there's something I could help but yeah raining is mostly for Lace because we work in a lot of things together so yeah it was a joke sorry don't call her okay so I don't mind you are going to say something or you are just not working now it's only me not working let's get this down can you hear me now you know I put this up when I want to drink something so no just a small correction I wanted to say that the next meeting is actually according to the schedule is 20 past 10 so you have 20 minutes more to sprint which is ice of course right thank you do we have the open space show show for people who want to wind down it's running so you can go there if you want we can make no guarantees as to what might happen in that room other than it will be we won't violate the code of conduct but we may be relatively random yeah we won't violate the code of conduct but yeah bye bye thank you are we going yeah we going wow last one surreal thought Bruno do we have anyone lined up to present anything I'm muted so I can't sorry my background was I was saying that we don't have anyone who raise their hands now until now we can wait a few more minutes okay yeah I know I know we probably want to grab Camilla and I've got something I've actually got something new do you want me to maybe ask around Jason yeah might as well just find out who wants to present yeah I just send a reminder and I send you the list of Springtime coordinators although if I don't see them in the participants I'll just skip it out right just to make it easier do you want applause oh yes please yeah I don't have my sound board of course one more minute and then it started alright so anyone who's in here who wants to present what they've done please do raise your hands in the participants list this is the end of day for the Sprint day 2 of EuroPython so welcome actually it's also our last end of day for EuroPython 2020 so this is it this is the final the final presentation it's been an amazing ride so anyone actually ready to go here does anyone is there anybody from because I recognize a few names in the list here is there anybody from Python Spanish documentation that just wants to just one last status update because I know you guys have been working even still you're welcome to go ahead hi Jason and let me share my screen I think I can show you the last things we had done today we had very first of day today and this one was the last presentation a few hours ago we had 132 open issues now we had 130 to list to list so it was very cool and we had 55 who requested open now we had 57 so it increased two requests since the CRs ago now we had 97% 97 persons on our channel and we will invite you to join us if you want to keep with us in the official translation to Spanish to keep growing there is a lot of work to do and thank you very much for the opportunity for this screen and that's it fantastic okay so just going through my list here I don't see any other hands raised at the moment are you going to show off your screen yeah I think I'm going to show off mine so I'm not going to go through the whole list this time because I think most people are most of the sprints have wrapped up but I'm going to show mine and I have to give a huge thanks to of course Simon here as well as Ajay Steven Gallagher and we got the name here I will find the name here and so thanks to all of them we do have some neat stuff so I'm going to minimize this and I'm going to start this up and I'll start my screen share and go desktop 2 hopefully this can be seen get everyone see that yeah well we have the menu I think I showed this before but we have some further adjustments from Stanislav with highlighting so that is pretty cool we get that out of the way we have the early rendering of the little character which is great so we have infinite map scrolling now and that is cool and then we also have no clip built in so that we can more easily navigate through the map and then we can use that to jump in we will eventually have free climbing here on the stone walls part of our design but still the fact that we can use that free climb for that no clip to be able to navigate is really helpful and you can see that this goes infinitely in either direction so that's cool so that's huge progress on our end and it's really exciting so thank you very much for helping with the demo quest sprint do we have anyone else who wanted to present did scanAPI present earlier? Camilla no she's not here but I worked on that sprint so I can probably tell some stuff what happened there oh why not sure why not so scanAPI went from let me find it let me actually screen share it as well I guess which is kind of fun because I don't know if she presented and if there's not that many pre-input presenting then I'll present as well so we'll go here let's find scanAPI so scanAPI had a lot of stuff happen if we look at the closed pool requests as well if they will actually load on github hope my internet doesn't die so they added a chat for all the new sprint participants they invited a lot of people to their organization fix some bugs I did the let me see I did added the faff icon we renamed everything the textual review so it's pretty much starting from here it's all merged during our sprint which is I think quite a bit looks good to me also I'll just present the project it's a thing where you can write a specification file for an API and then it generates a report like this for your entire API which is also quite cool that's all I have to say about scanAPI thank you good to have you last introduce yourself you know, thank any of you would have been in the pre-discord channel. I think there might be one more presenter coming in from Python packaging. Okay, that would be great. Yeah, but you could, yeah, okay, I can sort of see him. Okay, so Python packaging. It's very pit. Yeah, just just have him raise his hand. Oh yeah, there we go, there we go. You got him fully baked. Cool, and hello. Right, hey. Hey, hello everybody. Good evening, good morning, good night. I don't know where all of you are. Good evening from me. Good afternoon here. It's 5 p.m. here in Brazil. So I'm here to talk a little bit about the Python packaging spring from today, right? Yeah. Actually, today I finished some work in the warehouse repository. There was some API redirects that aren't really working. And then I went on to try and tackle some issues at Pip. I am actually still trying to write a failing case for a very interesting proposal about Pip Check detecting broken installs. But, well, I just started working with Pip today. And so I'm having a little bit of a hard time around. There are other colleagues in this spring working with the new dependencies over testing with very large and complex requirements.txt files. And we did find some interesting behaviors over there. And I think that's what we've done for today. Excellent. Thanks, Felipe. Thank you. Okay, so I've gone through the attendees list. I have gone through the, we just have someone else join the attendees though. That looks like it. So one last check, raise your hand in Zoom if you want to present. Otherwise, we will wrap this up so that some of us can go to bed, some of us can go get supper, and some of us can go clean the fog out of our heads. So Zoom fatigue is real, y'all. So thank you once again to everybody who came, all the sprint managers, all the sprinters, the attendees, of course, my fellow organizers. It was all of our sponsors. This was a lot of fun. Speaking personally, I enjoyed this. This was definitely the highlight of my summer. And I've met a lot of awesome people, had a really great time. I hope you have too. So, Mark, do you have anything you want to add before we wrap this up? No, not really. Just thank you very much for joining the sprints and hope you enjoyed yourself. And of course, you can continue until later at night if you like. We won't take the Discord server down anytime soon. And I hope to see you all at the sprints in Dublin next year. So see you then. Bye-bye. Like Mark said, we hope to see you next year. And thanks for joining us. Have a fantastic day or afternoon or evening.