Hi all, (hoping to break the thousands of emails currently being written...) we're having our first sprint at WikiToLearn!!! It's an exciting news since most of the participants are absolutely newcomers to FOSS development (let alone to KDE), and to various degrees to WikiToLearn too. The contribution areas are very diverse (content, code, infrastructure...), so there are some discussions which can't be held together. To complicate the matter, the sprint is happening this weekend (it was organized just two weeks ago), it will have 8 participants, and I will have (as WTL maintainer and sprint organizer) to guide it.
It is my greatest objective to make this sprint productive and especially community building, to give every participant the sense of how beautiful and inclusive our community is. Since it's been a few years since my last KDE sprint, I am admittedly quite rusty on how to make a sprint work best. I have checked online and I found no guidance on how to make a good sprint that can perform well. I want to take the opportunity to ask the help of the community! I need help in guidance, tips and tricks to help make the sprint as good as possible (hey, why don't we have a KDE knowledge base on these community matters?). Could you share some of the things that you found the most helpful in your past sprints? What did you like, what did you find productive? Did scrum work for you? How would you organize it? How would you structure the day? What infrastructure would you bring? Thanks a lot for your input. :-) -Riccardo _______________________________________________ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community