Many Python conferences have "sprints" included in their conference schedule. In this talk, we will explain what is it for the newcomers, why is it important to the open-source community, and as an organizer and maintainer how can you help this "sprints" movement.
We all know the famous quote in the Python community "I came for the language, but I stayed for the community" by Brett Cannon. But I would like to borrow it and say "I came for the conference, but I stayed for the sprint". As one of the organizers of Mentored Sprint, maintainer of an open-source project and long term sprint participant, I would like to explain to the people who are new to the community, what is a "sprint"? Also, I would like to discuss the goal of sprints from different points of view. First of all, I would like to introduce the concept of sprints. In software development, we have sprints to achieve some goals, whether it's fixing a bug or adding a new feature. But what about an open-source sprint? Are we going to achieve "something" in the sprint? What is this "something"? Then I would like to talk about what is the "benefit" of participating in a sprint as a maintainer? Will you get useful help in the sprint? Is it worth the time? What is the expectation of bringing your project into the sprint? In the end, I would like to add my opinion on why sprints, especially mentored sprint is so important to the open-source community and makes the community that we all would like to "stay for".
Speakers: Cheuk Ting Ho