[Pycon-openspaces] Open Spaces Update

[Brandon Rhodes]

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 at 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 at 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 at 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_EcWt5me0Y6tlMP4QOwLfbLVM/edit#heading=h.a5etkmit3rbc>
>> 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 at python.org
> https://mail.python.org/mailman/listinfo/pycon-openspaces
>
>


-- 
Brandon Rhodes
PyCon 2017 Conference Chair
pycon.brandon at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pycon-openspaces/attachments/20170328/98e7060a/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2017-03-27 at 10.44.58 PM.png
Type: image/png
Size: 22015 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/pycon-openspaces/attachments/20170328/98e7060a/attachment-0001.png>