@tomhohenstein To be a site in the global sprint, you need to have a room booked where people can come and work together for the two days. The room should have accessible wifi and toilets - those are the basics. If you can supply other things like tea/coffee, cake, lunch - well, that is icing on the cake but it is not necessary. People should come because they want to contribute to the lesson development as part of a team effort (and have some fun). People don't have to come for the whole sprint either - a half day or even a couple of hours would help. To know what to do - well, we are about to have a call to discuss the python lesson and we will use that call to decide on the projects to be worked on during the sprint. We will then assemble a list of tasks for the lessons we want to work on - these will be the SQL and Python lessons as far as I know, along with some badging of an existing web scraping lesson as Library Carpentry. @ostephens might also look at nutting out an XSLT lesson. People (especially non-coders) can also use the sprint to review lessons and raise GitHub issues on them - these might be areas not covered or areas that should be included, or material that should be removed. Issues help people who will be fixing the lessons understand what needs work, and what the needs of the community are. Happy to chat further.