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.
Hi Anna, Thank you for the update. We're doing internal testing of an MVP for the twitter bot this weekend and it's going well. We'll send you the test @address and instructions on how to test it by next Saturday, April 1. --Hobson (503) 974-6274 On Sun, Mar 26, 2017 at 4:59 AM, Anna Ossowski <ossanna16@gmx.de> wrote:
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.
_______________________________________________ Pycon-openspaces mailing list Pycon-openspaces@python.org https://mail.python.org/mailman/listinfo/pycon-openspaces
Thank you, Hobson! :) And no hurry, this is not urgent. I was just curious where you were at in the development process. Have a great Sunday! Anna --------------------------------- You are appreciated. You are enough. You matter. You are not alone.
On Mar 26, 2017, at 7:40 PM, Hobson Lane <hobsonlane@gmail.com> wrote:
Hi Anna,
Thank you for the update. We're doing internal testing of an MVP for the twitter bot this weekend and it's going well. We'll send you the test @address and instructions on how to test it by next Saturday, April 1.
--Hobson (503) 974-6274
On Sun, Mar 26, 2017 at 4:59 AM, Anna Ossowski <ossanna16@gmx.de <mailto:ossanna16@gmx.de>> wrote: 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.
_______________________________________________ Pycon-openspaces mailing list Pycon-openspaces@python.org <mailto:Pycon-openspaces@python.org> https://mail.python.org/mailman/listinfo/pycon-openspaces <https://mail.python.org/mailman/listinfo/pycon-openspaces>
Hi Anna, Thank you for putting together such a comprehensive update email. I have cropped out the points I am not addressing, but feel free to ask me anything I miss :) On Sun, Mar 26, 2017 at 6:59 AM, Anna Ossowski <ossanna16@gmx.de> wrote:
* 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?
Unfortunately, we do not have the same space as we did in 2016 for Sprints. This year the Sprints will be on the lower level and in the rooms where our tutorials/open space rooms will be prior to the Sprints (section A & B). See map: [image: Inline image 1] We have less space than we did in 2016 so we cannot commit any spaces to Open Spaces at this time. However, from my experience, Sprints attendees always find a way to have ad hoc get togethers.
* 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?
Our designer is working on the schedule this month. Since it is small, we have to see if it will have space for adding the open spaces. Can you give me more detail on what you expected for this?
Hi Ewa! That is totally fine about no Open Spaces at the sprints :) We were thinking about something like this Basically just a very small blank column titled “Open Spaces”, just big enough to make a little “X” with a pen. The idea behind this is to remind people that there are Open Spaces going on besides the regular talks and to give them the opportunity to mark the time slots they are planning on attending Open Spaces in. If there was additional space in the program, maybe we could also add 2 small sentences explaining what Open Spaces are and where you can sign up/find the schedule. Please let me know if this makes sense. Thank you so much! Anna --------------------------------- You are appreciated. You are enough. You matter. You are not alone.
On Mar 27, 2017, at 5:05 PM, Ewa Jodlowska <ewa@python.org> wrote:
Hi Anna,
Thank you for putting together such a comprehensive update email. I have cropped out the points I am not addressing, but feel free to ask me anything I miss :) On Sun, Mar 26, 2017 at 6:59 AM, Anna Ossowski <ossanna16@gmx.de <mailto:ossanna16@gmx.de>> wrote:
* 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?
Unfortunately, we do not have the same space as we did in 2016 for Sprints. This year the Sprints will be on the lower level and in the rooms where our tutorials/open space rooms will be prior to the Sprints (section A & B). See map:
<Screen Shot 2017-03-06 at 4.52.53 PM.png>
We have less space than we did in 2016 so we cannot commit any spaces to Open Spaces at this time. However, from my experience, Sprints attendees always find a way to have ad hoc get togethers.
* 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?
Our designer is working on the schedule this month. Since it is small, we have to see if it will have space for adding the open spaces. Can you give me more detail on what you expected for this?
Note that, on the printed schedule, the Open Spaces should not be displayed as though they begin and end when the talks to their left begin and end, because talks start and end at odd times but Open Spaces always (I think?) begin and end right on the hour. This might make them a bit challenging for the printed program folks to display, since the layout is very much dictated by when talks begin and end. On Mon, Mar 27, 2017 at 4:51 PM, Anna Ossowski <ossanna16@gmx.de> wrote:
Hi Ewa!
That is totally fine about no Open Spaces at the sprints :)
We were thinking about something like this
Basically just a very small blank column titled “Open Spaces”, just big enough to make a little “X” with a pen. The idea behind this is to remind people that there are Open Spaces going on besides the regular talks and to give them the opportunity to mark the time slots they are planning on attending Open Spaces in.
If there was additional space in the program, maybe we could also add 2 small sentences explaining what Open Spaces are and where you can sign up/find the schedule.
Please let me know if this makes sense.
Thank you so much! Anna
--------------------------------- You are appreciated. You are enough. You matter. You are not alone.
On Mar 27, 2017, at 5:05 PM, Ewa Jodlowska <ewa@python.org> wrote:
Hi Anna,
Thank you for putting together such a comprehensive update email. I have cropped out the points I am not addressing, but feel free to ask me anything I miss :) On Sun, Mar 26, 2017 at 6:59 AM, Anna Ossowski <ossanna16@gmx.de> wrote:
* 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?
Unfortunately, we do not have the same space as we did in 2016 for Sprints. This year the Sprints will be on the lower level and in the rooms where our tutorials/open space rooms will be prior to the Sprints (section A & B). See map:
<Screen Shot 2017-03-06 at 4.52.53 PM.png>
We have less space than we did in 2016 so we cannot commit any spaces to Open Spaces at this time. However, from my experience, Sprints attendees always find a way to have ad hoc get togethers.
* 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?
Our designer is working on the schedule this month. Since it is small, we have to see if it will have space for adding the open spaces. Can you give me more detail on what you expected for this?
_______________________________________________ Pycon-openspaces mailing list Pycon-openspaces@python.org https://mail.python.org/mailman/listinfo/pycon-openspaces
-- Brandon Rhodes PyCon 2017 Conference Chair pycon.brandon@gmail.com
I have asked Arbi (our designer) to think of something creative. Hopefully he can come up with something that tells the open spaces story well. BTW - I looked over the blog. LGTM. Best regards, Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 On Tue, Mar 28, 2017 at 9:26 AM, Brandon Rhodes <pycon.brandon@gmail.com> wrote:
Note that, on the printed schedule, the Open Spaces should not be displayed as though they begin and end when the talks to their left begin and end, because talks start and end at odd times but Open Spaces always (I think?) begin and end right on the hour. This might make them a bit challenging for the printed program folks to display, since the layout is very much dictated by when talks begin and end.
On Mon, Mar 27, 2017 at 4:51 PM, Anna Ossowski <ossanna16@gmx.de> wrote:
Hi Ewa!
That is totally fine about no Open Spaces at the sprints :)
We were thinking about something like this
Basically just a very small blank column titled “Open Spaces”, just big enough to make a little “X” with a pen. The idea behind this is to remind people that there are Open Spaces going on besides the regular talks and to give them the opportunity to mark the time slots they are planning on attending Open Spaces in.
If there was additional space in the program, maybe we could also add 2 small sentences explaining what Open Spaces are and where you can sign up/find the schedule.
Please let me know if this makes sense.
Thank you so much! Anna
--------------------------------- You are appreciated. You are enough. You matter. You are not alone.
On Mar 27, 2017, at 5:05 PM, Ewa Jodlowska <ewa@python.org> wrote:
Hi Anna,
Thank you for putting together such a comprehensive update email. I have cropped out the points I am not addressing, but feel free to ask me anything I miss :) On Sun, Mar 26, 2017 at 6:59 AM, Anna Ossowski <ossanna16@gmx.de> wrote:
* 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?
Unfortunately, we do not have the same space as we did in 2016 for Sprints. This year the Sprints will be on the lower level and in the rooms where our tutorials/open space rooms will be prior to the Sprints (section A & B). See map:
<Screen Shot 2017-03-06 at 4.52.53 PM.png>
We have less space than we did in 2016 so we cannot commit any spaces to Open Spaces at this time. However, from my experience, Sprints attendees always find a way to have ad hoc get togethers.
* 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?
Our designer is working on the schedule this month. Since it is small, we have to see if it will have space for adding the open spaces. Can you give me more detail on what you expected for this?
_______________________________________________ Pycon-openspaces mailing list Pycon-openspaces@python.org https://mail.python.org/mailman/listinfo/pycon-openspaces
-- Brandon Rhodes PyCon 2017 Conference Chair pycon.brandon@gmail.com
Thank you for clarifying the schedule layout, Brandon. That makes sense! Thank you Ewa for speaking with the designer and for looking over the blog post. If nothing else works, maybe we could at least add 2-3 sentences about the Open Spaces to the printed program? What would be a good time to publish the blog post? Maybe the beginning of May, approximately 2 weeks before PyCon? Thank you and have a wonderful day! Anna --------------------------------- You are appreciated. You are enough. You matter. You are not alone.
On Mar 28, 2017, at 4:29 PM, Ewa Jodlowska <ewa@python.org> wrote:
I have asked Arbi (our designer) to think of something creative. Hopefully he can come up with something that tells the open spaces story well.
BTW - I looked over the blog. LGTM.
Best regards,
Ewa Director of Operations Python Software Foundation Cell: 415-319-5237
On Tue, Mar 28, 2017 at 9:26 AM, Brandon Rhodes <pycon.brandon@gmail.com <mailto:pycon.brandon@gmail.com>> wrote: Note that, on the printed schedule, the Open Spaces should not be displayed as though they begin and end when the talks to their left begin and end, because talks start and end at odd times but Open Spaces always (I think?) begin and end right on the hour. This might make them a bit challenging for the printed program folks to display, since the layout is very much dictated by when talks begin and end.
On Mon, Mar 27, 2017 at 4:51 PM, Anna Ossowski <ossanna16@gmx.de <mailto:ossanna16@gmx.de>> wrote: Hi Ewa!
That is totally fine about no Open Spaces at the sprints :)
We were thinking about something like this
<Screen Shot 2017-03-27 at 10.44.58 PM.png>
Basically just a very small blank column titled “Open Spaces”, just big enough to make a little “X” with a pen. The idea behind this is to remind people that there are Open Spaces going on besides the regular talks and to give them the opportunity to mark the time slots they are planning on attending Open Spaces in.
If there was additional space in the program, maybe we could also add 2 small sentences explaining what Open Spaces are and where you can sign up/find the schedule.
Please let me know if this makes sense.
Thank you so much! Anna
--------------------------------- You are appreciated. You are enough. You matter. You are not alone.
On Mar 27, 2017, at 5:05 PM, Ewa Jodlowska <ewa@python.org <mailto:ewa@python.org>> wrote:
Hi Anna,
Thank you for putting together such a comprehensive update email. I have cropped out the points I am not addressing, but feel free to ask me anything I miss :) On Sun, Mar 26, 2017 at 6:59 AM, Anna Ossowski <ossanna16@gmx.de <mailto:ossanna16@gmx.de>> wrote:
* 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?
Unfortunately, we do not have the same space as we did in 2016 for Sprints. This year the Sprints will be on the lower level and in the rooms where our tutorials/open space rooms will be prior to the Sprints (section A & B). See map:
<Screen Shot 2017-03-06 at 4.52.53 PM.png>
We have less space than we did in 2016 so we cannot commit any spaces to Open Spaces at this time. However, from my experience, Sprints attendees always find a way to have ad hoc get togethers.
* 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?
Our designer is working on the schedule this month. Since it is small, we have to see if it will have space for adding the open spaces. Can you give me more detail on what you expected for this?
_______________________________________________ Pycon-openspaces mailing list Pycon-openspaces@python.org <mailto:Pycon-openspaces@python.org> https://mail.python.org/mailman/listinfo/pycon-openspaces <https://mail.python.org/mailman/listinfo/pycon-openspaces>
-- Brandon Rhodes PyCon 2017 Conference Chair pycon.brandon@gmail.com <mailto:pycon.brandon@gmail.com>
Publishing the blog post right at the end of April or beginning of May sounds good! I already had an entry for it on the social media to-do list, and I've now added a note that the draft has already been written up. Thank you, Anna! On Tue, Mar 28, 2017 at 10:46 AM, Anna Ossowski <ossanna16@gmx.de> wrote:
Thank you for clarifying the schedule layout, Brandon. That makes sense!
Thank you Ewa for speaking with the designer and for looking over the blog post.
If nothing else works, maybe we could at least add 2-3 sentences about the Open Spaces to the printed program?
What would be a good time to publish the blog post? Maybe the beginning of May, approximately 2 weeks before PyCon?
Thank you and have a wonderful day! Anna
--------------------------------- You are appreciated. You are enough. You matter. You are not alone.
On Mar 28, 2017, at 4:29 PM, Ewa Jodlowska <ewa@python.org> wrote:
I have asked Arbi (our designer) to think of something creative. Hopefully he can come up with something that tells the open spaces story well.
BTW - I looked over the blog. LGTM.
Best regards,
Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 <(415)%20319-5237>
On Tue, Mar 28, 2017 at 9:26 AM, Brandon Rhodes <pycon.brandon@gmail.com> wrote:
Note that, on the printed schedule, the Open Spaces should not be displayed as though they begin and end when the talks to their left begin and end, because talks start and end at odd times but Open Spaces always (I think?) begin and end right on the hour. This might make them a bit challenging for the printed program folks to display, since the layout is very much dictated by when talks begin and end.
On Mon, Mar 27, 2017 at 4:51 PM, Anna Ossowski <ossanna16@gmx.de> wrote:
Hi Ewa!
That is totally fine about no Open Spaces at the sprints :)
We were thinking about something like this
<Screen Shot 2017-03-27 at 10.44.58 PM.png>
Basically just a very small blank column titled “Open Spaces”, just big enough to make a little “X” with a pen. The idea behind this is to remind people that there are Open Spaces going on besides the regular talks and to give them the opportunity to mark the time slots they are planning on attending Open Spaces in.
If there was additional space in the program, maybe we could also add 2 small sentences explaining what Open Spaces are and where you can sign up/find the schedule.
Please let me know if this makes sense.
Thank you so much! Anna
--------------------------------- You are appreciated. You are enough. You matter. You are not alone.
On Mar 27, 2017, at 5:05 PM, Ewa Jodlowska <ewa@python.org> wrote:
Hi Anna,
Thank you for putting together such a comprehensive update email. I have cropped out the points I am not addressing, but feel free to ask me anything I miss :) On Sun, Mar 26, 2017 at 6:59 AM, Anna Ossowski <ossanna16@gmx.de> wrote:
* 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?
Unfortunately, we do not have the same space as we did in 2016 for Sprints. This year the Sprints will be on the lower level and in the rooms where our tutorials/open space rooms will be prior to the Sprints (section A & B). See map:
<Screen Shot 2017-03-06 at 4.52.53 PM.png>
We have less space than we did in 2016 so we cannot commit any spaces to Open Spaces at this time. However, from my experience, Sprints attendees always find a way to have ad hoc get togethers.
* 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?
Our designer is working on the schedule this month. Since it is small, we have to see if it will have space for adding the open spaces. Can you give me more detail on what you expected for this?
_______________________________________________ Pycon-openspaces mailing list Pycon-openspaces@python.org https://mail.python.org/mailman/listinfo/pycon-openspaces
-- Brandon Rhodes PyCon 2017 Conference Chair pycon.brandon@gmail.com
-- Brandon Rhodes PyCon 2017 Conference Chair pycon.brandon@gmail.com
Hello Brandon! I made a note in my calendar to double check the blog post one last time on April 24. We still need to add a sentence or two about the Open Spaces bot once we’ve been able to test the bot. I will email you once the blog post is 100% finished. Thank you! Anna --------------------------------- You are appreciated. You are enough. You matter. You are not alone.
On Mar 28, 2017, at 4:50 PM, Brandon Rhodes <pycon.brandon@gmail.com> wrote:
Publishing the blog post right at the end of April or beginning of May sounds good! I already had an entry for it on the social media to-do list, and I've now added a note that the draft has already been written up. Thank you, Anna!
On Tue, Mar 28, 2017 at 10:46 AM, Anna Ossowski <ossanna16@gmx.de <mailto:ossanna16@gmx.de>> wrote: Thank you for clarifying the schedule layout, Brandon. That makes sense!
Thank you Ewa for speaking with the designer and for looking over the blog post.
If nothing else works, maybe we could at least add 2-3 sentences about the Open Spaces to the printed program?
What would be a good time to publish the blog post? Maybe the beginning of May, approximately 2 weeks before PyCon?
Thank you and have a wonderful day! Anna
--------------------------------- You are appreciated. You are enough. You matter. You are not alone.
On Mar 28, 2017, at 4:29 PM, Ewa Jodlowska <ewa@python.org <mailto:ewa@python.org>> wrote:
I have asked Arbi (our designer) to think of something creative. Hopefully he can come up with something that tells the open spaces story well.
BTW - I looked over the blog. LGTM.
Best regards,
Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 <tel:(415)%20319-5237> On Tue, Mar 28, 2017 at 9:26 AM, Brandon Rhodes <pycon.brandon@gmail.com <mailto:pycon.brandon@gmail.com>> wrote: Note that, on the printed schedule, the Open Spaces should not be displayed as though they begin and end when the talks to their left begin and end, because talks start and end at odd times but Open Spaces always (I think?) begin and end right on the hour. This might make them a bit challenging for the printed program folks to display, since the layout is very much dictated by when talks begin and end.
On Mon, Mar 27, 2017 at 4:51 PM, Anna Ossowski <ossanna16@gmx.de <mailto:ossanna16@gmx.de>> wrote: Hi Ewa!
That is totally fine about no Open Spaces at the sprints :)
We were thinking about something like this
<Screen Shot 2017-03-27 at 10.44.58 PM.png>
Basically just a very small blank column titled “Open Spaces”, just big enough to make a little “X” with a pen. The idea behind this is to remind people that there are Open Spaces going on besides the regular talks and to give them the opportunity to mark the time slots they are planning on attending Open Spaces in.
If there was additional space in the program, maybe we could also add 2 small sentences explaining what Open Spaces are and where you can sign up/find the schedule.
Please let me know if this makes sense.
Thank you so much! Anna
--------------------------------- You are appreciated. You are enough. You matter. You are not alone.
On Mar 27, 2017, at 5:05 PM, Ewa Jodlowska <ewa@python.org <mailto:ewa@python.org>> wrote:
Hi Anna,
Thank you for putting together such a comprehensive update email. I have cropped out the points I am not addressing, but feel free to ask me anything I miss :) On Sun, Mar 26, 2017 at 6:59 AM, Anna Ossowski <ossanna16@gmx.de <mailto:ossanna16@gmx.de>> wrote:
* 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?
Unfortunately, we do not have the same space as we did in 2016 for Sprints. This year the Sprints will be on the lower level and in the rooms where our tutorials/open space rooms will be prior to the Sprints (section A & B). See map:
<Screen Shot 2017-03-06 at 4.52.53 PM.png>
We have less space than we did in 2016 so we cannot commit any spaces to Open Spaces at this time. However, from my experience, Sprints attendees always find a way to have ad hoc get togethers.
* 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?
Our designer is working on the schedule this month. Since it is small, we have to see if it will have space for adding the open spaces. Can you give me more detail on what you expected for this?
_______________________________________________ Pycon-openspaces mailing list Pycon-openspaces@python.org <mailto:Pycon-openspaces@python.org> https://mail.python.org/mailman/listinfo/pycon-openspaces <https://mail.python.org/mailman/listinfo/pycon-openspaces>
-- Brandon Rhodes PyCon 2017 Conference Chair pycon.brandon@gmail.com <mailto:pycon.brandon@gmail.com>
-- Brandon Rhodes PyCon 2017 Conference Chair pycon.brandon@gmail.com <mailto:pycon.brandon@gmail.com>
Sounds good! I'll watch for your note near the end of April. On Tue, Mar 28, 2017 at 11:31 AM, Anna Ossowski <ossanna16@gmx.de> wrote:
Hello Brandon!
I made a note in my calendar to double check the blog post one last time on April 24. We still need to add a sentence or two about the Open Spaces bot once we’ve been able to test the bot. I will email you once the blog post is 100% finished.
Thank you! Anna
--------------------------------- You are appreciated. You are enough. You matter. You are not alone.
On Mar 28, 2017, at 4:50 PM, Brandon Rhodes <pycon.brandon@gmail.com> wrote:
Publishing the blog post right at the end of April or beginning of May sounds good! I already had an entry for it on the social media to-do list, and I've now added a note that the draft has already been written up. Thank you, Anna!
On Tue, Mar 28, 2017 at 10:46 AM, Anna Ossowski <ossanna16@gmx.de> wrote:
Thank you for clarifying the schedule layout, Brandon. That makes sense!
Thank you Ewa for speaking with the designer and for looking over the blog post.
If nothing else works, maybe we could at least add 2-3 sentences about the Open Spaces to the printed program?
What would be a good time to publish the blog post? Maybe the beginning of May, approximately 2 weeks before PyCon?
Thank you and have a wonderful day! Anna
--------------------------------- You are appreciated. You are enough. You matter. You are not alone.
On Mar 28, 2017, at 4:29 PM, Ewa Jodlowska <ewa@python.org> wrote:
I have asked Arbi (our designer) to think of something creative. Hopefully he can come up with something that tells the open spaces story well.
BTW - I looked over the blog. LGTM.
Best regards,
Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 <(415)%20319-5237>
On Tue, Mar 28, 2017 at 9:26 AM, Brandon Rhodes <pycon.brandon@gmail.com> wrote:
Note that, on the printed schedule, the Open Spaces should not be displayed as though they begin and end when the talks to their left begin and end, because talks start and end at odd times but Open Spaces always (I think?) begin and end right on the hour. This might make them a bit challenging for the printed program folks to display, since the layout is very much dictated by when talks begin and end.
On Mon, Mar 27, 2017 at 4:51 PM, Anna Ossowski <ossanna16@gmx.de> wrote:
Hi Ewa!
That is totally fine about no Open Spaces at the sprints :)
We were thinking about something like this
<Screen Shot 2017-03-27 at 10.44.58 PM.png>
Basically just a very small blank column titled “Open Spaces”, just big enough to make a little “X” with a pen. The idea behind this is to remind people that there are Open Spaces going on besides the regular talks and to give them the opportunity to mark the time slots they are planning on attending Open Spaces in.
If there was additional space in the program, maybe we could also add 2 small sentences explaining what Open Spaces are and where you can sign up/find the schedule.
Please let me know if this makes sense.
Thank you so much! Anna
--------------------------------- You are appreciated. You are enough. You matter. You are not alone.
On Mar 27, 2017, at 5:05 PM, Ewa Jodlowska <ewa@python.org> wrote:
Hi Anna,
Thank you for putting together such a comprehensive update email. I have cropped out the points I am not addressing, but feel free to ask me anything I miss :) On Sun, Mar 26, 2017 at 6:59 AM, Anna Ossowski <ossanna16@gmx.de> wrote:
* 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?
Unfortunately, we do not have the same space as we did in 2016 for Sprints. This year the Sprints will be on the lower level and in the rooms where our tutorials/open space rooms will be prior to the Sprints (section A & B). See map:
<Screen Shot 2017-03-06 at 4.52.53 PM.png>
We have less space than we did in 2016 so we cannot commit any spaces to Open Spaces at this time. However, from my experience, Sprints attendees always find a way to have ad hoc get togethers.
* 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?
Our designer is working on the schedule this month. Since it is small, we have to see if it will have space for adding the open spaces. Can you give me more detail on what you expected for this?
_______________________________________________ Pycon-openspaces mailing list Pycon-openspaces@python.org https://mail.python.org/mailman/listinfo/pycon-openspaces
-- Brandon Rhodes PyCon 2017 Conference Chair pycon.brandon@gmail.com
-- Brandon Rhodes PyCon 2017 Conference Chair pycon.brandon@gmail.com
-- Brandon Rhodes PyCon 2017 Conference Chair pycon.brandon@gmail.com
participants (4)
-
Anna Ossowski -
Brandon Rhodes -
Ewa Jodlowska -
Hobson Lane