Hello everyone! PyCon is less than two months away (yay!) and I made a note in my calendar to send an update email this weekend. This may seem a little too early but I’ll be traveling for all the conferences in April and May and I tend to be less organized and available when I’m traveling so to make sure everything will be ready by the time PyCon gets here, I thought it would be a good idea to start prepping things now. Small update: * I reached out to the PyCon mobile guide team and asked if they could add the Open Spaces to the Guidebook app Everyone, * We talked about offering Open Spaces during the sprints and Ewa said there would be rooms available to do this. Do we still want to do this? Is there anything else we would need to do in order to make this happen? * We agreed that it would be a good idea to publish a blog post about the Open Spaces again this year. I pulled up last year’s blog post <https://docs.google.com/document/d/1ZvEyX-xH6VccLpL5TK_EcWt5me0Y6tlMP4QOwLfb...> updated it, and left some comments. If you all could take a look and comment/edit, etc., that would be fabulous. Trey, you mentioned that it would be good to have the blog post added to the Python newsletter. Do you have any ideas on how we can accomplish this? Ewa and Brandon, * We talked about adding a section about the Open Spaces and possible a blank column indicating each Open Spaces time slot to the printed schedule. Do you know yet if this will be possible? Hobson and Trey, * Hobson, could you please give us a short update on the Twitter bot? When do you think could we do a test run? * Last year we split up “Open Spaces duty” into 3 shifts for each day of the talks/Open Spaces. Open Spaces duty basically just means that each day one of us is responsible for monitoring the board every couple of hours, making sure there are no Open Spaces scheduled which would violate the CoC, putting out cards and pens in the morning, making sure there are enough cards and pens by the Open Spaces board and that everything is clean and organized, and this year also monitoring the bot. We found that the system worked well last year as each person only was “on call” for one day. Could both of you please let me know your preference regarding which day you would like to be on Open Spaces duty (May 19, 20, or 21)? * Last year we had a very short (10 minutes) briefing meeting a day before the talks/Open Spaces started. Do you think we should do this again this year or is it not necessary? If you’re pro briefing meeting, would both of you be available sometime on May 18 for 10-15 minutes? * Last year each of us tweeted about the Open Spaces from our private Twitter accounts using the hashtag #pyconopenspace to promote the Open Spaces. Some of these tweets were retweeted by the @pycon Twitter account. If we could all do this again this year (maybe 1-2 tweets a day), that would be fabulous! We’ll also have the Open Spaces bot this year, which will help with promotion as well. Thank you! I look forward to seeing you at PyCon :) Anna --------------------------------- You are appreciated. You are enough. You matter. You are not alone.