From zak.kent at gmail.com Sun Nov 5 23:20:49 2017 From: zak.kent at gmail.com (Zak) Date: Sun, 5 Nov 2017 20:20:49 -0800 Subject: [Pycon-openspaces] Kicking Off the Open Spaces Planning!!! In-Reply-To: <62217B42-D991-47DC-AB3D-FA9314E137CC@gmail.com> References: <62217B42-D991-47DC-AB3D-FA9314E137CC@gmail.com> Message-ID: Hi everyone, I'm excited to help out with the Open Spaces planning this time around! I wasn't very involved in the planning process last year so I'm not exactly sure what went as planned and what did not. However, I will say that from an outsiders perspective the Open Spaces sign up board and process for scheduling things looked fairly organized. It was also nice to see people using the bot :) I'm totally in favor of using a Trello board to organize our planning/thoughts. I've started to think about a few changes that would be nice to make to the bot. Things like, making it a little smarter, possibly adding a few more features, and changing the way the system is deployed so it can be used more easily by others. Hobs added a few issue the totalgood/openchat repo last time around that I'm planning as using as a starting point for adding things (link to issues ). Really looking forward to helping out in any way that I can! Zak On Mon, Oct 30, 2017 at 11:13 AM, Anna Ossowski wrote: > Hi all, > > I hope you?re all well! > > I thought it would be a good idea to officially kick off the planning of > the PyCon US 2018 Open Spaces before the holidays hit everyone. May may > still seem a long time away but it?s never too early to start planning :) > > In the past I have used a Trello board (please let me know if you don?t > have access) to keep track of ideas and tasks but I am open to using > something different. I do think that using some sort of project management > tool, whether that?s something like Trello or GitHub, makes sense and makes > things a little easier. > > Maybe we can start by discussing what went well last year, what didn?t go > as planned, and any ideas we would like to implement for 2018. > > Looking forward to working with all of you again! > Anna > > ?? > You are appreciated. > You are enough. > You matter. > You are not alone. > > > > > _______________________________________________ > Pycon-openspaces mailing list > Pycon-openspaces at python.org > https://mail.python.org/mailman/listinfo/pycon-openspaces > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From hobsonlane at gmail.com Mon Nov 6 17:57:23 2017 From: hobsonlane at gmail.com (Hobson Lane) Date: Mon, 6 Nov 2017 14:57:23 -0800 Subject: [Pycon-openspaces] Kicking Off the Open Spaces Planning!!! In-Reply-To: <62217B42-D991-47DC-AB3D-FA9314E137CC@gmail.com> References: <62217B42-D991-47DC-AB3D-FA9314E137CC@gmail.com> Message-ID: Thank you Anna, I've been swamped adjusting to a new job. I'll make that announcement to PyCon staff this week. I'll try to use GitHub for issue/feature tracking since that's what Zak and I are using for the twitter bot. Will fall back to Trello if GitHub doesn't meet our needs. --Hobson On Mon, Oct 30, 2017 at 11:13 AM, Anna Ossowski wrote: > Hi all, > > I hope you?re all well! > > I thought it would be a good idea to officially kick off the planning of > the PyCon US 2018 Open Spaces before the holidays hit everyone. May may > still seem a long time away but it?s never too early to start planning :) > > In the past I have used a Trello board (please let me know if you don?t > have access) to keep track of ideas and tasks but I am open to using > something different. I do think that using some sort of project management > tool, whether that?s something like Trello or GitHub, makes sense and makes > things a little easier. > > Maybe we can start by discussing what went well last year, what didn?t go > as planned, and any ideas we would like to implement for 2018. > > Looking forward to working with all of you again! > Anna > > ?? > You are appreciated. > You are enough. > You matter. > You are not alone. > > > > > _______________________________________________ > Pycon-openspaces mailing list > Pycon-openspaces at python.org > https://mail.python.org/mailman/listinfo/pycon-openspaces > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From annabell.ossowski at gmail.com Mon Nov 6 18:14:10 2017 From: annabell.ossowski at gmail.com (Anna Ossowski) Date: Tue, 7 Nov 2017 00:14:10 +0100 Subject: [Pycon-openspaces] Kicking Off the Open Spaces Planning!!! In-Reply-To: References: <62217B42-D991-47DC-AB3D-FA9314E137CC@gmail.com> Message-ID: <83D3629B-640A-4714-ABD4-0B0CCFD38C0F@gmail.com> Sounds good, Hobson! Just to summarize, a couple of tasks and ideas from the last 2 years were: Tasks * Adding the Open Spaces section to the PyCon website * Writing a blog post promoting the Open Spaces (to be published about a month before the conference) * Monitoring the Open Spaces board onsite and tidying up around it * Promoting the Open Spaces during the conference via our private Twitter accounts and the Open Spaces bot * Asking the PyCon Chair to mention the Open Spaces in their remarks at PyCon * Making sure the Open Spaces are mentioned in Guidebook Ideas/Feedback - How can we make the Open Spaces board more visible? - Can we grid the Open Spaces schedule according to the talk schedule? Open Spaces slots and talk slots don?t start and end at the same times which means people sometimes miss two talks in order to attend an Open Space. - Can we provide paper + pens + tape so people can label their Open Spaces rooms and people know which Open Space is happening in which room at any given time without having to check the board constantly. ?? You are appreciated. You are enough. You matter. You are not alone. > On Nov 6, 2017, at 11:57 PM, Hobson Lane wrote: > > Thank you Anna, I've been swamped adjusting to a new job. I'll make that announcement to PyCon staff this week. I'll try to use GitHub for issue/feature tracking since that's what Zak and I are using for the twitter bot. Will fall back to Trello if GitHub doesn't meet our needs. > > --Hobson > > > On Mon, Oct 30, 2017 at 11:13 AM, Anna Ossowski > wrote: > Hi all, > > I hope you?re all well! > > I thought it would be a good idea to officially kick off the planning of the PyCon US 2018 Open Spaces before the holidays hit everyone. May may still seem a long time away but it?s never too early to start planning :) > > In the past I have used a Trello board (please let me know if you don?t have access) to keep track of ideas and tasks but I am open to using something different. I do think that using some sort of project management tool, whether that?s something like Trello or GitHub, makes sense and makes things a little easier. > > Maybe we can start by discussing what went well last year, what didn?t go as planned, and any ideas we would like to implement for 2018. > > Looking forward to working with all of you again! > Anna > > ?? > You are appreciated. > You are enough. > You matter. > You are not alone. > > > > > _______________________________________________ > Pycon-openspaces mailing list > Pycon-openspaces at python.org > https://mail.python.org/mailman/listinfo/pycon-openspaces > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From hobsonlane at gmail.com Mon Nov 6 19:17:40 2017 From: hobsonlane at gmail.com (Hobson Lane) Date: Mon, 6 Nov 2017 16:17:40 -0800 Subject: [Pycon-openspaces] Kicking Off the Open Spaces Planning!!! In-Reply-To: <83D3629B-640A-4714-ABD4-0B0CCFD38C0F@gmail.com> References: <62217B42-D991-47DC-AB3D-FA9314E137CC@gmail.com> <83D3629B-640A-4714-ABD4-0B0CCFD38C0F@gmail.com> Message-ID: Thank you Anna! That helps a ton! --Hobson On Mon, Nov 6, 2017 at 3:14 PM, Anna Ossowski wrote: > Sounds good, Hobson! > > Just to summarize, a couple of tasks and ideas from the last 2 years were: > > *Tasks* > > * Adding the Open Spaces section to the PyCon website > * Writing a blog post promoting the Open Spaces (to be published about a > month before the conference) > * Monitoring the Open Spaces board onsite and tidying up around it > * Promoting the Open Spaces during the conference via our private Twitter > accounts and the Open Spaces bot > * Asking the PyCon Chair to mention the Open Spaces in their remarks at > PyCon > * Making sure the Open Spaces are mentioned in Guidebook > > *Ideas/Feedback* > > - How can we make the Open Spaces board more visible? > - Can we grid the Open Spaces schedule according to the talk schedule? > Open Spaces slots and talk slots don?t start and end at the same times > which means people sometimes miss two talks in order to attend an Open > Space. > - Can we provide paper + pens + tape so people can label their Open Spaces > rooms and people know which Open Space is happening in which room at any > given time without having to check the board constantly. > > > ?? > You are appreciated. > You are enough. > You matter. > You are not alone. > > > > On Nov 6, 2017, at 11:57 PM, Hobson Lane wrote: > > Thank you Anna, I've been swamped adjusting to a new job. I'll make that > announcement to PyCon staff this week. I'll try to use GitHub for > issue/feature tracking since that's what Zak and I are using for the > twitter bot. Will fall back to Trello if GitHub doesn't meet our needs. > > --Hobson > > > On Mon, Oct 30, 2017 at 11:13 AM, Anna Ossowski < > annabell.ossowski at gmail.com> wrote: > >> Hi all, >> >> I hope you?re all well! >> >> I thought it would be a good idea to officially kick off the planning of >> the PyCon US 2018 Open Spaces before the holidays hit everyone. May may >> still seem a long time away but it?s never too early to start planning :) >> >> In the past I have used a Trello board (please let me know if you don?t >> have access) to keep track of ideas and tasks but I am open to using >> something different. I do think that using some sort of project management >> tool, whether that?s something like Trello or GitHub, makes sense and makes >> things a little easier. >> >> Maybe we can start by discussing what went well last year, what didn?t go >> as planned, and any ideas we would like to implement for 2018. >> >> Looking forward to working with all of you again! >> Anna >> >> ?? >> You are appreciated. >> You are enough. >> You matter. >> You are not alone. >> >> >> >> >> _______________________________________________ >> Pycon-openspaces mailing list >> Pycon-openspaces at python.org >> https://mail.python.org/mailman/listinfo/pycon-openspaces >> >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From trey at truthful.technology Mon Nov 6 22:30:57 2017 From: trey at truthful.technology (Trey Hunner) Date: Mon, 6 Nov 2017 19:30:57 -0800 Subject: [Pycon-openspaces] Kicking Off the Open Spaces Planning!!! In-Reply-To: <62217B42-D991-47DC-AB3D-FA9314E137CC@gmail.com> References: <62217B42-D991-47DC-AB3D-FA9314E137CC@gmail.com> Message-ID: Hi all! Thanks for kicking off the planning Anna and thanks for continuing the conversation Zak and starting the issue tracking and announcements Hobson. Maybe we should start another thread for this, but I was brainstorming some open spaces ideas recently and wanted to dump them here. I met someone deeply involved in the agile world through a mutual friend recently and we talked quite a bit about communication at tech conferences. We discussed some strategies agile conferences use to get people meeting each other (determining topics to discuss in a group by using a Trello-style to-discuss, discussing, discussed system) and we talked about our views of open spaces. He noted that talks often draw people away from open spaces if they're hosted at the same time and we debated the merits of having dedicated open space days/times vs shared talk and open space times. Some things that I've been thinking about: - Sharing a fairly curated ideas list for open spaces that have been popular/successful in the past and open spaces we'd like to see folks put up in the future - Brainstorming and sharing alternative open space formats with potential open space planners (e.g. quiet room, yoga, sticker exchange, or an open space where people hold 2 minute conversations with a person and then rotate musical chair style) - Making a "how to run a successful open space" cheat sheet with things like recommendations for giving a voice to attendees, taking shared notes, and exchanging contact information with each other and considering continuing the discussion online in a structured way Many of the things I've been thinking about involve more active recommendations/nudging from us to encourage a particular feel/vibe from the open spaces. Thoughts on this? On Mon, Oct 30, 2017 at 11:13 AM, Anna Ossowski wrote: > Hi all, > > I hope you?re all well! > > I thought it would be a good idea to officially kick off the planning of > the PyCon US 2018 Open Spaces before the holidays hit everyone. May may > still seem a long time away but it?s never too early to start planning :) > > In the past I have used a Trello board (please let me know if you don?t > have access) to keep track of ideas and tasks but I am open to using > something different. I do think that using some sort of project management > tool, whether that?s something like Trello or GitHub, makes sense and makes > things a little easier. > > Maybe we can start by discussing what went well last year, what didn?t go > as planned, and any ideas we would like to implement for 2018. > > Looking forward to working with all of you again! > Anna > > ?? > You are appreciated. > You are enough. > You matter. > You are not alone. > > > > > _______________________________________________ > Pycon-openspaces mailing list > Pycon-openspaces at python.org > https://mail.python.org/mailman/listinfo/pycon-openspaces > > -- Trey Hunner Truthful Technology, LLC http://truthful.technology -------------- next part -------------- An HTML attachment was scrubbed... URL: From annabell.ossowski at gmail.com Tue Nov 7 08:20:13 2017 From: annabell.ossowski at gmail.com (Anna Ossowski) Date: Tue, 7 Nov 2017 14:20:13 +0100 Subject: [Pycon-openspaces] Kicking Off the Open Spaces Planning!!! In-Reply-To: References: <62217B42-D991-47DC-AB3D-FA9314E137CC@gmail.com> Message-ID: Hi Trey, Thank you for your ideas! I believe the actual Open Space rooms will only be available during the 3 days of talks. We could however think about encouraging informal Open Spaces (which I think happens anyway) during the tutorials and sprints. We have tried curating a list of topics before and it was semi-successful in my opinion. I like the idea of giving people some ideas, on the other hand I don?t want people to think that we are ?dictating? certain topics or maybe disturb their creativity (?maybe my idea isn?t good enough?) by providing suggestions. I think the quiet room should stay a quiet space. I wouldn?t want to disturb people who are taking a break from the conference, by offering an Open Space in this room, even if it would be yoga or meditation. I like the idea of a sticker exchange. OSCON does speed networking, which is what you described with the musical chairs idea. I do however worry a bit that if we add too much structure, this will take away from the Open Spaces as they are supposed to be open and kind of informal as the name suggests. ++ for the cheat sheet idea! ?? You are appreciated. You are enough. You matter. You are not alone. > On Nov 7, 2017, at 4:30 AM, Trey Hunner wrote: > > Hi all! > > Thanks for kicking off the planning Anna and thanks for continuing the conversation Zak and starting the issue tracking and announcements Hobson. > > Maybe we should start another thread for this, but I was brainstorming some open spaces ideas recently and wanted to dump them here. > > I met someone deeply involved in the agile world through a mutual friend recently and we talked quite a bit about communication at tech conferences. > > We discussed some strategies agile conferences use to get people meeting each other (determining topics to discuss in a group by using a Trello-style to-discuss, discussing, discussed system) and we talked about our views of open spaces. He noted that talks often draw people away from open spaces if they're hosted at the same time and we debated the merits of having dedicated open space days/times vs shared talk and open space times. > > Some things that I've been thinking about: > Sharing a fairly curated ideas list for open spaces that have been popular/successful in the past and open spaces we'd like to see folks put up in the future > Brainstorming and sharing alternative open space formats with potential open space planners (e.g. quiet room, yoga, sticker exchange, or an open space where people hold 2 minute conversations with a person and then rotate musical chair style) > Making a "how to run a successful open space" cheat sheet with things like recommendations for giving a voice to attendees, taking shared notes, and exchanging contact information with each other and considering continuing the discussion online in a structured way > Many of the things I've been thinking about involve more active recommendations/nudging from us to encourage a particular feel/vibe from the open spaces. Thoughts on this? > > On Mon, Oct 30, 2017 at 11:13 AM, Anna Ossowski > wrote: > Hi all, > > I hope you?re all well! > > I thought it would be a good idea to officially kick off the planning of the PyCon US 2018 Open Spaces before the holidays hit everyone. May may still seem a long time away but it?s never too early to start planning :) > > In the past I have used a Trello board (please let me know if you don?t have access) to keep track of ideas and tasks but I am open to using something different. I do think that using some sort of project management tool, whether that?s something like Trello or GitHub, makes sense and makes things a little easier. > > Maybe we can start by discussing what went well last year, what didn?t go as planned, and any ideas we would like to implement for 2018. > > Looking forward to working with all of you again! > Anna > > ?? > You are appreciated. > You are enough. > You matter. > You are not alone. > > > > > _______________________________________________ > Pycon-openspaces mailing list > Pycon-openspaces at python.org > https://mail.python.org/mailman/listinfo/pycon-openspaces > > > > > -- > Trey Hunner > Truthful Technology, LLC > http://truthful.technology -------------- next part -------------- An HTML attachment was scrubbed... URL: From ewa at python.org Tue Nov 7 11:46:31 2017 From: ewa at python.org (Ewa Jodlowska) Date: Tue, 7 Nov 2017 10:46:31 -0600 Subject: [Pycon-openspaces] Kicking Off the Open Spaces Planning!!! In-Reply-To: References: <62217B42-D991-47DC-AB3D-FA9314E137CC@gmail.com> Message-ID: Hi everyone: A few interjections from me: On Tue, Nov 7, 2017 at 7:20 AM, Anna Ossowski wrote: > Hi Trey, > > Thank you for your ideas! > > I believe the actual Open Space rooms will only be available during the 3 > days of talks. We could however think about encouraging informal Open > Spaces (which I think happens anyway) during the tutorials and sprints. > Anna is correct - open space rooms are available May 11-13. > > We have tried curating a list of topics before and it was semi-successful > in my opinion. I like the idea of giving people some ideas, on the other > hand I don?t want people to think that we are ?dictating? certain topics or > maybe disturb their creativity (?maybe my idea isn?t good enough?) by > providing suggestions. > > I think the quiet room should stay a quiet space. I wouldn?t want to > disturb people who are taking a break from the conference, by offering an > Open Space in this room, even if it would be yoga or meditation. I like the > idea of a sticker exchange. OSCON does speed networking, which is what you > described with the musical chairs idea. I do however worry a bit that if we > add too much structure, this will take away from the Open Spaces as they > are supposed to be open and kind of informal as the name suggests. > FYI - I have a separate room (outside of the Open Space Rooms) dedicated to a quiet room. Please do not use one of the open space rooms for this. The "rules" for this room will be based on what I saw at EuroPython:[image: Inline image 1] > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IMG_6808.JPG Type: image/jpeg Size: 355303 bytes Desc: not available URL: From betsy at python.org Tue Nov 7 12:03:34 2017 From: betsy at python.org (Betsy Waliszewski) Date: Tue, 7 Nov 2017 09:03:34 -0800 Subject: [Pycon-openspaces] Kicking Off the Open Spaces Planning!!! Message-ID: On Mon, Nov 6, 2017 at 7:30 PM, Trey Hunner wrote: > Hi all! > > Thanks for kicking off the planning Anna and thanks for continuing the > conversation Zak and starting the issue tracking and announcements Hobson. > > Maybe we should start another thread for this, but I was brainstorming > some open spaces ideas recently and wanted to dump them here. > > I met someone deeply involved in the agile world through a mutual friend > recently and we talked quite a bit about communication at tech conferences. > > We discussed some strategies agile conferences use to get people meeting > each other (determining topics to discuss in a group by using a > Trello-style to-discuss, discussing, discussed system) and we talked about > our views of open spaces. He noted that talks often draw people away from > open spaces if they're hosted at the same time and we debated the merits of > having dedicated open space days/times vs shared talk and open space times. > > Some things that I've been thinking about: > > - Sharing a fairly curated ideas list for open spaces that have been > popular/successful in the past and open spaces we'd like to see folks put > up in the future > - Brainstorming and sharing alternative open space formats with > potential open space planners (e.g. quiet room, yoga, sticker exchange, or > an open space where people hold 2 minute conversations with a person and > then rotate musical chair style) > > I'm planning a Speed Networking event just before the Opening Reception: 30 minutes Location: In front of expo hall Spend two minutes exchanging information with a fellow attendee. When the chime sounds, move on to the next attendee. We can make sure to have participation in Open Space a discussion item :-). > > - Making a "how to run a successful open space" cheat sheet with > things like recommendations for giving a voice to attendees, taking shared > notes, and exchanging contact information with each other and considering > continuing the discussion online in a structured way > > Many of the things I've been thinking about involve more active > recommendations/nudging from us to encourage a particular feel/vibe from > the open spaces. Thoughts on this? > > On Mon, Oct 30, 2017 at 11:13 AM, Anna Ossowski < > annabell.ossowski at gmail.com> wrote: > >> Hi all, >> >> I hope you?re all well! >> >> I thought it would be a good idea to officially kick off the planning of >> the PyCon US 2018 Open Spaces before the holidays hit everyone. May may >> still seem a long time away but it?s never too early to start planning :) >> >> In the past I have used a Trello board (please let me know if you don?t >> have access) to keep track of ideas and tasks but I am open to using >> something different. I do think that using some sort of project management >> tool, whether that?s something like Trello or GitHub, makes sense and makes >> things a little easier. >> >> Maybe we can start by discussing what went well last year, what didn?t go >> as planned, and any ideas we would like to implement for 2018. >> >> Looking forward to working with all of you again! >> Anna >> >> ?? >> You are appreciated. >> You are enough. >> You matter. >> You are not alone. >> >> >> >> >> _______________________________________________ >> Pycon-openspaces mailing list >> Pycon-openspaces at python.org >> https://mail.python.org/mailman/listinfo/pycon-openspaces >> >> > > > -- > Trey Hunner > Truthful Technology, LLC > http://truthful.technology > > _______________________________________________ > Pycon-openspaces mailing list > Pycon-openspaces at python.org > https://mail.python.org/mailman/listinfo/pycon-openspaces > > -------------- next part -------------- An HTML attachment was scrubbed... URL: