Kicking Off the Open Spaces Planning!!!
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.
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 <https://github.com/totalgood/openchat/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 <annabell.ossowski@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@python.org https://mail.python.org/mailman/listinfo/pycon-openspaces
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@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@python.org https://mail.python.org/mailman/listinfo/pycon-openspaces
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 <hobsonlane@gmail.com> 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@gmail.com <mailto:annabell.ossowski@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@python.org <mailto:Pycon-openspaces@python.org> https://mail.python.org/mailman/listinfo/pycon-openspaces <https://mail.python.org/mailman/listinfo/pycon-openspaces>
Thank you Anna! That helps a ton! --Hobson On Mon, Nov 6, 2017 at 3:14 PM, Anna Ossowski <annabell.ossowski@gmail.com> 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 <hobsonlane@gmail.com> 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@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@python.org https://mail.python.org/mailman/listinfo/pycon-openspaces
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 <annabell.ossowski@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@python.org https://mail.python.org/mailman/listinfo/pycon-openspaces
-- Trey Hunner Truthful Technology, LLC http://truthful.technology
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 <trey@truthful.technology> 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 <annabell.ossowski@gmail.com <mailto:annabell.ossowski@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@python.org <mailto:Pycon-openspaces@python.org> https://mail.python.org/mailman/listinfo/pycon-openspaces <https://mail.python.org/mailman/listinfo/pycon-openspaces>
-- Trey Hunner Truthful Technology, LLC http://truthful.technology <http://truthful.technology/>
Hi everyone: A few interjections from me: On Tue, Nov 7, 2017 at 7:20 AM, Anna Ossowski <annabell.ossowski@gmail.com> 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]
Thank you Trey! Apologies for the late response. Really excited to hear your thinking. Those 3 bullets are spot on! Seems very similar to ideas Anna and I have been batting around since I joined her open spaces team. If you or Zak want to take a stab at drafting material to support one or all of those 3 bullet points, I'd be happy to help 1. flesh them out 2. incorporate PyCon staff feedback 3. seek approval for publication by PyCon staff 4. get them incorporated into the website and other announcements (maybe even Zak's twitter bot dialog) I think they'd really advance the quality of the 2018 Open Spaces experience, especially if the Twitter bot can be evolved to incorporate them into its "brain". Regarding Anna's "High's and Low's" list from last year, some things I observed last year: * Low: The chatbot was pretty basic and needs work to be made really useful * High: The chatbot was used by more than 50% of the openspace event planners and seemed to get the word out a bit * Low: Some of the open spaces (inluding the one I led) could have benefited from some of Trey's guideance/ideas in his bullet points * High: Tweeting a pic of the board seemed like it helped some people plan their day * High: The board posting went smoothly once we had a board up * High?: Did we accomplish that 2-board approach we planned? If we can support open spaces organizers with some or all of Trey's ideas/docs this year I'd be super happy. --Hobson On Mon, Nov 6, 2017 at 7:30 PM, Trey Hunner <trey@truthful.technology> 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 < annabell.ossowski@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@python.org https://mail.python.org/mailman/listinfo/pycon-openspaces
-- Trey Hunner Truthful Technology, LLC http://truthful.technology
_______________________________________________ Pycon-openspaces mailing list Pycon-openspaces@python.org https://mail.python.org/mailman/listinfo/pycon-openspaces
Hi all, Thank you for kicking things off! Two things from me: * If we could do a little education on open spaces (like Trey suggested) that would go a long way. Maybe a blog post on how to run an open space, which we could push put before PyCon, and a small cheat sheet with a couple of tips on how to run an open space, which we could distribute during PyCon. * I liked the bot last year and I appreciate all the work that went into making this happen. I also think that it is a good idea to discuss how we can improve the bot, but I wanted to point out that we should also acknowledge that some people won’t use the bot or Twitter so maybe we can think of some other “traditional” ways on how to promote the open spaces, just to make sure we reach as many people as possible. Thank you! Anna —— You are appreciated. You are enough. You matter. You are not alone.
On Jan 14, 2018, at 2:25 AM, Hobson Lane <hobsonlane@gmail.com> wrote:
Thank you Trey! Apologies for the late response. Really excited to hear your thinking. Those 3 bullets are spot on! Seems very similar to ideas Anna and I have been batting around since I joined her open spaces team.
If you or Zak want to take a stab at drafting material to support one or all of those 3 bullet points, I'd be happy to help
1. flesh them out 2. incorporate PyCon staff feedback 3. seek approval for publication by PyCon staff 4. get them incorporated into the website and other announcements (maybe even Zak's twitter bot dialog)
I think they'd really advance the quality of the 2018 Open Spaces experience, especially if the Twitter bot can be evolved to incorporate them into its "brain".
Regarding Anna's "High's and Low's" list from last year, some things I observed last year:
* Low: The chatbot was pretty basic and needs work to be made really useful * High: The chatbot was used by more than 50% of the openspace event planners and seemed to get the word out a bit * Low: Some of the open spaces (inluding the one I led) could have benefited from some of Trey's guideance/ideas in his bullet points * High: Tweeting a pic of the board seemed like it helped some people plan their day * High: The board posting went smoothly once we had a board up * High?: Did we accomplish that 2-board approach we planned?
If we can support open spaces organizers with some or all of Trey's ideas/docs this year I'd be super happy.
--Hobson
On Mon, Nov 6, 2017 at 7:30 PM, Trey Hunner <trey@truthful.technology <mailto:trey@truthful.technology>> 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 <annabell.ossowski@gmail.com <mailto:annabell.ossowski@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@python.org <mailto:Pycon-openspaces@python.org> https://mail.python.org/mailman/listinfo/pycon-openspaces <https://mail.python.org/mailman/listinfo/pycon-openspaces>
-- Trey Hunner Truthful Technology, LLC http://truthful.technology <http://truthful.technology/> _______________________________________________ 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>
Yea that's exactly what I intend to do. On Sun, Jan 14, 2018, 3:21 PM Anna Ossowski <annabell.ossowski@gmail.com> wrote:
Hi all,
Thank you for kicking things off!
Two things from me:
* If we could do a little education on open spaces (like Trey suggested) that would go a long way. Maybe a blog post on how to run an open space, which we could push put before PyCon, and a small cheat sheet with a couple of tips on how to run an open space, which we could distribute during PyCon.
* I liked the bot last year and I appreciate all the work that went into making this happen. I also think that it is a good idea to discuss how we can improve the bot, but I wanted to point out that we should also acknowledge that some people won’t use the bot or Twitter so maybe we can think of some other “traditional” ways on how to promote the open spaces, just to make sure we reach as many people as possible.
Thank you! Anna
—— You are appreciated. You are enough. You matter. You are not alone.
On Jan 14, 2018, at 2:25 AM, Hobson Lane <hobsonlane@gmail.com> wrote:
Thank you Trey! Apologies for the late response. Really excited to hear your thinking. Those 3 bullets are spot on! Seems very similar to ideas Anna and I have been batting around since I joined her open spaces team.
If you or Zak want to take a stab at drafting material to support one or all of those 3 bullet points, I'd be happy to help
1. flesh them out 2. incorporate PyCon staff feedback 3. seek approval for publication by PyCon staff 4. get them incorporated into the website and other announcements (maybe even Zak's twitter bot dialog)
I think they'd really advance the quality of the 2018 Open Spaces experience, especially if the Twitter bot can be evolved to incorporate them into its "brain".
Regarding Anna's "High's and Low's" list from last year, some things I observed last year:
* Low: The chatbot was pretty basic and needs work to be made really useful * High: The chatbot was used by more than 50% of the openspace event planners and seemed to get the word out a bit * Low: Some of the open spaces (inluding the one I led) could have benefited from some of Trey's guideance/ideas in his bullet points * High: Tweeting a pic of the board seemed like it helped some people plan their day * High: The board posting went smoothly once we had a board up * High?: Did we accomplish that 2-board approach we planned?
If we can support open spaces organizers with some or all of Trey's ideas/docs this year I'd be super happy.
--Hobson
On Mon, Nov 6, 2017 at 7:30 PM, Trey Hunner <trey@truthful.technology> 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 < annabell.ossowski@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@python.org https://mail.python.org/mailman/listinfo/pycon-openspaces
-- Trey Hunner Truthful Technology, LLC http://truthful.technology
_______________________________________________ Pycon-openspaces mailing list Pycon-openspaces@python.org https://mail.python.org/mailman/listinfo/pycon-openspaces
Hello everyone, I'm excited to start working in earnest on some of the Openspaces stuff :) I can make a rough pass at drafting a google doc with possible tips for running an Openspace sometime this week. Having never run myself, I'm planning on looking through older sources of information about Openspaces from previous Pycons and going from there. Any suggestions on existing material that's worth looking at are most welcome. I've also begun looking at ways to improve the bot this year. I added a few new issues to the github repo and will start working on making improvements in the coming days/weeks. Planning on starting with cleaning things up, fixing some minor bugs, adding better Slack integration, and making it easier to deploy. From there will work on making the bot more useful and expanding the types of tweets it recognizes and its available responses. I hope you're all doing well! - Zak On Sun, Jan 14, 2018 at 3:28 PM, Hobson Lane <hobsonlane@gmail.com> wrote:
Yea that's exactly what I intend to do.
On Sun, Jan 14, 2018, 3:21 PM Anna Ossowski <annabell.ossowski@gmail.com> wrote:
Hi all,
Thank you for kicking things off!
Two things from me:
* If we could do a little education on open spaces (like Trey suggested) that would go a long way. Maybe a blog post on how to run an open space, which we could push put before PyCon, and a small cheat sheet with a couple of tips on how to run an open space, which we could distribute during PyCon.
* I liked the bot last year and I appreciate all the work that went into making this happen. I also think that it is a good idea to discuss how we can improve the bot, but I wanted to point out that we should also acknowledge that some people won’t use the bot or Twitter so maybe we can think of some other “traditional” ways on how to promote the open spaces, just to make sure we reach as many people as possible.
Thank you! Anna
—— You are appreciated. You are enough. You matter. You are not alone.
On Jan 14, 2018, at 2:25 AM, Hobson Lane <hobsonlane@gmail.com> wrote:
Thank you Trey! Apologies for the late response. Really excited to hear your thinking. Those 3 bullets are spot on! Seems very similar to ideas Anna and I have been batting around since I joined her open spaces team.
If you or Zak want to take a stab at drafting material to support one or all of those 3 bullet points, I'd be happy to help
1. flesh them out 2. incorporate PyCon staff feedback 3. seek approval for publication by PyCon staff 4. get them incorporated into the website and other announcements (maybe even Zak's twitter bot dialog)
I think they'd really advance the quality of the 2018 Open Spaces experience, especially if the Twitter bot can be evolved to incorporate them into its "brain".
Regarding Anna's "High's and Low's" list from last year, some things I observed last year:
* Low: The chatbot was pretty basic and needs work to be made really useful * High: The chatbot was used by more than 50% of the openspace event planners and seemed to get the word out a bit * Low: Some of the open spaces (inluding the one I led) could have benefited from some of Trey's guideance/ideas in his bullet points * High: Tweeting a pic of the board seemed like it helped some people plan their day * High: The board posting went smoothly once we had a board up * High?: Did we accomplish that 2-board approach we planned?
If we can support open spaces organizers with some or all of Trey's ideas/docs this year I'd be super happy.
--Hobson
On Mon, Nov 6, 2017 at 7:30 PM, Trey Hunner <trey@truthful.technology> 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 < annabell.ossowski@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@python.org https://mail.python.org/mailman/listinfo/pycon-openspaces
-- Trey Hunner Truthful Technology, LLC http://truthful.technology
_______________________________________________ Pycon-openspaces mailing list Pycon-openspaces@python.org https://mail.python.org/mailman/listinfo/pycon-openspaces
Excellent Zak. Thank you. On Sun, Jan 21, 2018, 8:26 PM Zak <zak.kent@gmail.com> wrote:
Hello everyone,
I'm excited to start working in earnest on some of the Openspaces stuff :)
I can make a rough pass at drafting a google doc with possible tips for running an Openspace sometime this week. Having never run myself, I'm planning on looking through older sources of information about Openspaces from previous Pycons and going from there. Any suggestions on existing material that's worth looking at are most welcome.
I've also begun looking at ways to improve the bot this year. I added a few new issues to the github repo and will start working on making improvements in the coming days/weeks. Planning on starting with cleaning things up, fixing some minor bugs, adding better Slack integration, and making it easier to deploy. From there will work on making the bot more useful and expanding the types of tweets it recognizes and its available responses.
I hope you're all doing well!
- Zak
On Sun, Jan 14, 2018 at 3:28 PM, Hobson Lane <hobsonlane@gmail.com> wrote:
Yea that's exactly what I intend to do.
On Sun, Jan 14, 2018, 3:21 PM Anna Ossowski <annabell.ossowski@gmail.com> wrote:
Hi all,
Thank you for kicking things off!
Two things from me:
* If we could do a little education on open spaces (like Trey suggested) that would go a long way. Maybe a blog post on how to run an open space, which we could push put before PyCon, and a small cheat sheet with a couple of tips on how to run an open space, which we could distribute during PyCon.
* I liked the bot last year and I appreciate all the work that went into making this happen. I also think that it is a good idea to discuss how we can improve the bot, but I wanted to point out that we should also acknowledge that some people won’t use the bot or Twitter so maybe we can think of some other “traditional” ways on how to promote the open spaces, just to make sure we reach as many people as possible.
Thank you! Anna
—— You are appreciated. You are enough. You matter. You are not alone.
On Jan 14, 2018, at 2:25 AM, Hobson Lane <hobsonlane@gmail.com> wrote:
Thank you Trey! Apologies for the late response. Really excited to hear your thinking. Those 3 bullets are spot on! Seems very similar to ideas Anna and I have been batting around since I joined her open spaces team.
If you or Zak want to take a stab at drafting material to support one or all of those 3 bullet points, I'd be happy to help
1. flesh them out 2. incorporate PyCon staff feedback 3. seek approval for publication by PyCon staff 4. get them incorporated into the website and other announcements (maybe even Zak's twitter bot dialog)
I think they'd really advance the quality of the 2018 Open Spaces experience, especially if the Twitter bot can be evolved to incorporate them into its "brain".
Regarding Anna's "High's and Low's" list from last year, some things I observed last year:
* Low: The chatbot was pretty basic and needs work to be made really useful * High: The chatbot was used by more than 50% of the openspace event planners and seemed to get the word out a bit * Low: Some of the open spaces (inluding the one I led) could have benefited from some of Trey's guideance/ideas in his bullet points * High: Tweeting a pic of the board seemed like it helped some people plan their day * High: The board posting went smoothly once we had a board up * High?: Did we accomplish that 2-board approach we planned?
If we can support open spaces organizers with some or all of Trey's ideas/docs this year I'd be super happy.
--Hobson
On Mon, Nov 6, 2017 at 7:30 PM, Trey Hunner <trey@truthful.technology> 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 < annabell.ossowski@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@python.org https://mail.python.org/mailman/listinfo/pycon-openspaces
-- Trey Hunner Truthful Technology, LLC http://truthful.technology
_______________________________________________ Pycon-openspaces mailing list Pycon-openspaces@python.org https://mail.python.org/mailman/listinfo/pycon-openspaces
Thanks Zak. I can help you on the Google Doc. Send me a link once you've got it started and I'll add what I've seen in open space organizing so far. On Sun, Jan 21, 2018 at 8:26 PM, Zak <zak.kent@gmail.com> wrote:
Hello everyone,
I'm excited to start working in earnest on some of the Openspaces stuff :)
I can make a rough pass at drafting a google doc with possible tips for running an Openspace sometime this week. Having never run myself, I'm planning on looking through older sources of information about Openspaces from previous Pycons and going from there. Any suggestions on existing material that's worth looking at are most welcome.
I've also begun looking at ways to improve the bot this year. I added a few new issues to the github repo and will start working on making improvements in the coming days/weeks. Planning on starting with cleaning things up, fixing some minor bugs, adding better Slack integration, and making it easier to deploy. From there will work on making the bot more useful and expanding the types of tweets it recognizes and its available responses.
I hope you're all doing well!
- Zak
On Sun, Jan 14, 2018 at 3:28 PM, Hobson Lane <hobsonlane@gmail.com> wrote:
Yea that's exactly what I intend to do.
On Sun, Jan 14, 2018, 3:21 PM Anna Ossowski <annabell.ossowski@gmail.com> wrote:
Hi all,
Thank you for kicking things off!
Two things from me:
* If we could do a little education on open spaces (like Trey suggested) that would go a long way. Maybe a blog post on how to run an open space, which we could push put before PyCon, and a small cheat sheet with a couple of tips on how to run an open space, which we could distribute during PyCon.
* I liked the bot last year and I appreciate all the work that went into making this happen. I also think that it is a good idea to discuss how we can improve the bot, but I wanted to point out that we should also acknowledge that some people won’t use the bot or Twitter so maybe we can think of some other “traditional” ways on how to promote the open spaces, just to make sure we reach as many people as possible.
Thank you! Anna
—— You are appreciated. You are enough. You matter. You are not alone.
On Jan 14, 2018, at 2:25 AM, Hobson Lane <hobsonlane@gmail.com> wrote:
Thank you Trey! Apologies for the late response. Really excited to hear your thinking. Those 3 bullets are spot on! Seems very similar to ideas Anna and I have been batting around since I joined her open spaces team.
If you or Zak want to take a stab at drafting material to support one or all of those 3 bullet points, I'd be happy to help
1. flesh them out 2. incorporate PyCon staff feedback 3. seek approval for publication by PyCon staff 4. get them incorporated into the website and other announcements (maybe even Zak's twitter bot dialog)
I think they'd really advance the quality of the 2018 Open Spaces experience, especially if the Twitter bot can be evolved to incorporate them into its "brain".
Regarding Anna's "High's and Low's" list from last year, some things I observed last year:
* Low: The chatbot was pretty basic and needs work to be made really useful * High: The chatbot was used by more than 50% of the openspace event planners and seemed to get the word out a bit * Low: Some of the open spaces (inluding the one I led) could have benefited from some of Trey's guideance/ideas in his bullet points * High: Tweeting a pic of the board seemed like it helped some people plan their day * High: The board posting went smoothly once we had a board up * High?: Did we accomplish that 2-board approach we planned?
If we can support open spaces organizers with some or all of Trey's ideas/docs this year I'd be super happy.
--Hobson
On Mon, Nov 6, 2017 at 7:30 PM, Trey Hunner <trey@truthful.technology> 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 < annabell.ossowski@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@python.org https://mail.python.org/mailman/listinfo/pycon-openspaces
-- Trey Hunner Truthful Technology, LLC http://truthful.technology
_______________________________________________ Pycon-openspaces mailing list Pycon-openspaces@python.org https://mail.python.org/mailman/listinfo/pycon-openspaces
-- Trey Hunner Truthful Technology, LLC http://truthful.technology
Thanks Trey and Hobs, Here is a link to what I have so far, it's not much but hopefully it will help get the ball rolling. Any feedback/ideas are most welcome :) I just added the possible topics that Hobs suggested and then created a few general tips that might be useful to mention to organizers. I still have questions about what the best way to format and distribute a guide to running an Openspace might be, possibly a blog post that we can point people to when signing up? I'll probably add more things to the doc in the coming days. https://docs.google.com/document/d/1scTO9mNxNk2vXbK-_yubvPLH51DCM97u4Jag4HL4... On Tue, Jan 23, 2018 at 8:53 AM, Trey Hunner <trey@truthful.technology> wrote:
Thanks Zak. I can help you on the Google Doc. Send me a link once you've got it started and I'll add what I've seen in open space organizing so far.
On Sun, Jan 21, 2018 at 8:26 PM, Zak <zak.kent@gmail.com> wrote:
Hello everyone,
I'm excited to start working in earnest on some of the Openspaces stuff :)
I can make a rough pass at drafting a google doc with possible tips for running an Openspace sometime this week. Having never run myself, I'm planning on looking through older sources of information about Openspaces from previous Pycons and going from there. Any suggestions on existing material that's worth looking at are most welcome.
I've also begun looking at ways to improve the bot this year. I added a few new issues to the github repo and will start working on making improvements in the coming days/weeks. Planning on starting with cleaning things up, fixing some minor bugs, adding better Slack integration, and making it easier to deploy. From there will work on making the bot more useful and expanding the types of tweets it recognizes and its available responses.
I hope you're all doing well!
- Zak
On Sun, Jan 14, 2018 at 3:28 PM, Hobson Lane <hobsonlane@gmail.com> wrote:
Yea that's exactly what I intend to do.
On Sun, Jan 14, 2018, 3:21 PM Anna Ossowski <annabell.ossowski@gmail.com> wrote:
Hi all,
Thank you for kicking things off!
Two things from me:
* If we could do a little education on open spaces (like Trey suggested) that would go a long way. Maybe a blog post on how to run an open space, which we could push put before PyCon, and a small cheat sheet with a couple of tips on how to run an open space, which we could distribute during PyCon.
* I liked the bot last year and I appreciate all the work that went into making this happen. I also think that it is a good idea to discuss how we can improve the bot, but I wanted to point out that we should also acknowledge that some people won’t use the bot or Twitter so maybe we can think of some other “traditional” ways on how to promote the open spaces, just to make sure we reach as many people as possible.
Thank you! Anna
—— You are appreciated. You are enough. You matter. You are not alone.
On Jan 14, 2018, at 2:25 AM, Hobson Lane <hobsonlane@gmail.com> wrote:
Thank you Trey! Apologies for the late response. Really excited to hear your thinking. Those 3 bullets are spot on! Seems very similar to ideas Anna and I have been batting around since I joined her open spaces team.
If you or Zak want to take a stab at drafting material to support one or all of those 3 bullet points, I'd be happy to help
1. flesh them out 2. incorporate PyCon staff feedback 3. seek approval for publication by PyCon staff 4. get them incorporated into the website and other announcements (maybe even Zak's twitter bot dialog)
I think they'd really advance the quality of the 2018 Open Spaces experience, especially if the Twitter bot can be evolved to incorporate them into its "brain".
Regarding Anna's "High's and Low's" list from last year, some things I observed last year:
* Low: The chatbot was pretty basic and needs work to be made really useful * High: The chatbot was used by more than 50% of the openspace event planners and seemed to get the word out a bit * Low: Some of the open spaces (inluding the one I led) could have benefited from some of Trey's guideance/ideas in his bullet points * High: Tweeting a pic of the board seemed like it helped some people plan their day * High: The board posting went smoothly once we had a board up * High?: Did we accomplish that 2-board approach we planned?
If we can support open spaces organizers with some or all of Trey's ideas/docs this year I'd be super happy.
--Hobson
On Mon, Nov 6, 2017 at 7:30 PM, Trey Hunner <trey@truthful.technology> 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 < annabell.ossowski@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@python.org https://mail.python.org/mailman/listinfo/pycon-openspaces
-- Trey Hunner Truthful Technology, LLC http://truthful.technology
_______________________________________________ Pycon-openspaces mailing list Pycon-openspaces@python.org https://mail.python.org/mailman/listinfo/pycon-openspaces
-- Trey Hunner Truthful Technology, LLC http://truthful.technology
Excellent, Zak. --Hobson On Wed, Jan 24, 2018 at 8:51 PM, Zak <zak.kent@gmail.com> wrote:
Thanks Trey and Hobs,
Here is a link to what I have so far, it's not much but hopefully it will help get the ball rolling. Any feedback/ideas are most welcome :)
I just added the possible topics that Hobs suggested and then created a few general tips that might be useful to mention to organizers. I still have questions about what the best way to format and distribute a guide to running an Openspace might be, possibly a blog post that we can point people to when signing up? I'll probably add more things to the doc in the coming days.
https://docs.google.com/document/d/1scTO9mNxNk2vXbK-_ yubvPLH51DCM97u4Jag4HL4-eM/edit?usp=sharing
On Tue, Jan 23, 2018 at 8:53 AM, Trey Hunner <trey@truthful.technology> wrote:
Thanks Zak. I can help you on the Google Doc. Send me a link once you've got it started and I'll add what I've seen in open space organizing so far.
On Sun, Jan 21, 2018 at 8:26 PM, Zak <zak.kent@gmail.com> wrote:
Hello everyone,
I'm excited to start working in earnest on some of the Openspaces stuff :)
I can make a rough pass at drafting a google doc with possible tips for running an Openspace sometime this week. Having never run myself, I'm planning on looking through older sources of information about Openspaces from previous Pycons and going from there. Any suggestions on existing material that's worth looking at are most welcome.
I've also begun looking at ways to improve the bot this year. I added a few new issues to the github repo and will start working on making improvements in the coming days/weeks. Planning on starting with cleaning things up, fixing some minor bugs, adding better Slack integration, and making it easier to deploy. From there will work on making the bot more useful and expanding the types of tweets it recognizes and its available responses.
I hope you're all doing well!
- Zak
On Sun, Jan 14, 2018 at 3:28 PM, Hobson Lane <hobsonlane@gmail.com> wrote:
Yea that's exactly what I intend to do.
On Sun, Jan 14, 2018, 3:21 PM Anna Ossowski < annabell.ossowski@gmail.com> wrote:
Hi all,
Thank you for kicking things off!
Two things from me:
* If we could do a little education on open spaces (like Trey suggested) that would go a long way. Maybe a blog post on how to run an open space, which we could push put before PyCon, and a small cheat sheet with a couple of tips on how to run an open space, which we could distribute during PyCon.
* I liked the bot last year and I appreciate all the work that went into making this happen. I also think that it is a good idea to discuss how we can improve the bot, but I wanted to point out that we should also acknowledge that some people won’t use the bot or Twitter so maybe we can think of some other “traditional” ways on how to promote the open spaces, just to make sure we reach as many people as possible.
Thank you! Anna
—— You are appreciated. You are enough. You matter. You are not alone.
On Jan 14, 2018, at 2:25 AM, Hobson Lane <hobsonlane@gmail.com> wrote:
Thank you Trey! Apologies for the late response. Really excited to hear your thinking. Those 3 bullets are spot on! Seems very similar to ideas Anna and I have been batting around since I joined her open spaces team.
If you or Zak want to take a stab at drafting material to support one or all of those 3 bullet points, I'd be happy to help
1. flesh them out 2. incorporate PyCon staff feedback 3. seek approval for publication by PyCon staff 4. get them incorporated into the website and other announcements (maybe even Zak's twitter bot dialog)
I think they'd really advance the quality of the 2018 Open Spaces experience, especially if the Twitter bot can be evolved to incorporate them into its "brain".
Regarding Anna's "High's and Low's" list from last year, some things I observed last year:
* Low: The chatbot was pretty basic and needs work to be made really useful * High: The chatbot was used by more than 50% of the openspace event planners and seemed to get the word out a bit * Low: Some of the open spaces (inluding the one I led) could have benefited from some of Trey's guideance/ideas in his bullet points * High: Tweeting a pic of the board seemed like it helped some people plan their day * High: The board posting went smoothly once we had a board up * High?: Did we accomplish that 2-board approach we planned?
If we can support open spaces organizers with some or all of Trey's ideas/docs this year I'd be super happy.
--Hobson
On Mon, Nov 6, 2017 at 7:30 PM, Trey Hunner <trey@truthful.technology> 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 < annabell.ossowski@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@python.org > https://mail.python.org/mailman/listinfo/pycon-openspaces > >
-- Trey Hunner Truthful Technology, LLC http://truthful.technology
_______________________________________________ Pycon-openspaces mailing list Pycon-openspaces@python.org https://mail.python.org/mailman/listinfo/pycon-openspaces
-- Trey Hunner Truthful Technology, LLC http://truthful.technology
I left a tiny comment in the doc about supplies. Let me know if you come up with other ways I can support ya'll! On Thu, Jan 25, 2018 at 5:34 AM, Hobson Lane <hobsonlane@gmail.com> wrote:
Excellent, Zak.
--Hobson
On Wed, Jan 24, 2018 at 8:51 PM, Zak <zak.kent@gmail.com> wrote:
Thanks Trey and Hobs,
Here is a link to what I have so far, it's not much but hopefully it will help get the ball rolling. Any feedback/ideas are most welcome :)
I just added the possible topics that Hobs suggested and then created a few general tips that might be useful to mention to organizers. I still have questions about what the best way to format and distribute a guide to running an Openspace might be, possibly a blog post that we can point people to when signing up? I'll probably add more things to the doc in the coming days.
https://docs.google.com/document/d/1scTO9mNxNk2vXbK-_yubvPLH 51DCM97u4Jag4HL4-eM/edit?usp=sharing
On Tue, Jan 23, 2018 at 8:53 AM, Trey Hunner <trey@truthful.technology> wrote:
Thanks Zak. I can help you on the Google Doc. Send me a link once you've got it started and I'll add what I've seen in open space organizing so far.
On Sun, Jan 21, 2018 at 8:26 PM, Zak <zak.kent@gmail.com> wrote:
Hello everyone,
I'm excited to start working in earnest on some of the Openspaces stuff :)
I can make a rough pass at drafting a google doc with possible tips for running an Openspace sometime this week. Having never run myself, I'm planning on looking through older sources of information about Openspaces from previous Pycons and going from there. Any suggestions on existing material that's worth looking at are most welcome.
I've also begun looking at ways to improve the bot this year. I added a few new issues to the github repo and will start working on making improvements in the coming days/weeks. Planning on starting with cleaning things up, fixing some minor bugs, adding better Slack integration, and making it easier to deploy. From there will work on making the bot more useful and expanding the types of tweets it recognizes and its available responses.
I hope you're all doing well!
- Zak
On Sun, Jan 14, 2018 at 3:28 PM, Hobson Lane <hobsonlane@gmail.com> wrote:
Yea that's exactly what I intend to do.
On Sun, Jan 14, 2018, 3:21 PM Anna Ossowski < annabell.ossowski@gmail.com> wrote:
Hi all,
Thank you for kicking things off!
Two things from me:
* If we could do a little education on open spaces (like Trey suggested) that would go a long way. Maybe a blog post on how to run an open space, which we could push put before PyCon, and a small cheat sheet with a couple of tips on how to run an open space, which we could distribute during PyCon.
* I liked the bot last year and I appreciate all the work that went into making this happen. I also think that it is a good idea to discuss how we can improve the bot, but I wanted to point out that we should also acknowledge that some people won’t use the bot or Twitter so maybe we can think of some other “traditional” ways on how to promote the open spaces, just to make sure we reach as many people as possible.
Thank you! Anna
—— You are appreciated. You are enough. You matter. You are not alone.
On Jan 14, 2018, at 2:25 AM, Hobson Lane <hobsonlane@gmail.com> wrote:
Thank you Trey! Apologies for the late response. Really excited to hear your thinking. Those 3 bullets are spot on! Seems very similar to ideas Anna and I have been batting around since I joined her open spaces team.
If you or Zak want to take a stab at drafting material to support one or all of those 3 bullet points, I'd be happy to help
1. flesh them out 2. incorporate PyCon staff feedback 3. seek approval for publication by PyCon staff 4. get them incorporated into the website and other announcements (maybe even Zak's twitter bot dialog)
I think they'd really advance the quality of the 2018 Open Spaces experience, especially if the Twitter bot can be evolved to incorporate them into its "brain".
Regarding Anna's "High's and Low's" list from last year, some things I observed last year:
* Low: The chatbot was pretty basic and needs work to be made really useful * High: The chatbot was used by more than 50% of the openspace event planners and seemed to get the word out a bit * Low: Some of the open spaces (inluding the one I led) could have benefited from some of Trey's guideance/ideas in his bullet points * High: Tweeting a pic of the board seemed like it helped some people plan their day * High: The board posting went smoothly once we had a board up * High?: Did we accomplish that 2-board approach we planned?
If we can support open spaces organizers with some or all of Trey's ideas/docs this year I'd be super happy.
--Hobson
On Mon, Nov 6, 2017 at 7:30 PM, Trey Hunner <trey@truthful.technology > 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 < > annabell.ossowski@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@python.org >> https://mail.python.org/mailman/listinfo/pycon-openspaces >> >> > > > -- > Trey Hunner > Truthful Technology, LLC > http://truthful.technology > > _______________________________________________ > Pycon-openspaces mailing list > Pycon-openspaces@python.org > https://mail.python.org/mailman/listinfo/pycon-openspaces > >
-- Trey Hunner Truthful Technology, LLC http://truthful.technology
_______________________________________________ Pycon-openspaces mailing list Pycon-openspaces@python.org https://mail.python.org/mailman/listinfo/pycon-openspaces
Thanks Zak! This looks great! I left a few comments as well. For distribution I would suggest a number of different approaches: * A blog post about 2 weeks before the conference * Add the information to the Open Spaces page on the PyCon website. In previous years we also had a section on there encouraging people who already had concrete ideas for Open Spaces, to email us and we would list their idea (and possibly even a time and date) on our website. * Maybe print small posters with the tips and put them up in the Open Spaces rooms? If Ewa can organize easels or whiteboards as she suggested, that would be super beneficial. * Have a poster or a table center piece including this information by our Open Spaces board at the conference. Thank you for the great work! Anna —— You are appreciated. You are enough. You matter. You are not alone.
On Jan 25, 2018, at 9:01 AM, Ewa Jodlowska <ewa@python.org> wrote:
I left a tiny comment in the doc about supplies. Let me know if you come up with other ways I can support ya'll!
On Thu, Jan 25, 2018 at 5:34 AM, Hobson Lane <hobsonlane@gmail.com <mailto:hobsonlane@gmail.com>> wrote: Excellent, Zak.
--Hobson
On Wed, Jan 24, 2018 at 8:51 PM, Zak <zak.kent@gmail.com <mailto:zak.kent@gmail.com>> wrote: Thanks Trey and Hobs,
Here is a link to what I have so far, it's not much but hopefully it will help get the ball rolling. Any feedback/ideas are most welcome :)
I just added the possible topics that Hobs suggested and then created a few general tips that might be useful to mention to organizers. I still have questions about what the best way to format and distribute a guide to running an Openspace might be, possibly a blog post that we can point people to when signing up? I'll probably add more things to the doc in the coming days.
https://docs.google.com/document/d/1scTO9mNxNk2vXbK-_yubvPLH51DCM97u4Jag4HL4... <https://docs.google.com/document/d/1scTO9mNxNk2vXbK-_yubvPLH51DCM97u4Jag4HL4...>
On Tue, Jan 23, 2018 at 8:53 AM, Trey Hunner <trey@truthful.technology <mailto:trey@truthful.technology>> wrote: Thanks Zak. I can help you on the Google Doc. Send me a link once you've got it started and I'll add what I've seen in open space organizing so far.
On Sun, Jan 21, 2018 at 8:26 PM, Zak <zak.kent@gmail.com <mailto:zak.kent@gmail.com>> wrote: Hello everyone,
I'm excited to start working in earnest on some of the Openspaces stuff :)
I can make a rough pass at drafting a google doc with possible tips for running an Openspace sometime this week. Having never run myself, I'm planning on looking through older sources of information about Openspaces from previous Pycons and going from there. Any suggestions on existing material that's worth looking at are most welcome.
I've also begun looking at ways to improve the bot this year. I added a few new issues to the github repo and will start working on making improvements in the coming days/weeks. Planning on starting with cleaning things up, fixing some minor bugs, adding better Slack integration, and making it easier to deploy. From there will work on making the bot more useful and expanding the types of tweets it recognizes and its available responses.
I hope you're all doing well!
- Zak
On Sun, Jan 14, 2018 at 3:28 PM, Hobson Lane <hobsonlane@gmail.com <mailto:hobsonlane@gmail.com>> wrote: Yea that's exactly what I intend to do.
On Sun, Jan 14, 2018, 3:21 PM Anna Ossowski <annabell.ossowski@gmail.com <mailto:annabell.ossowski@gmail.com>> wrote: Hi all,
Thank you for kicking things off!
Two things from me:
* If we could do a little education on open spaces (like Trey suggested) that would go a long way. Maybe a blog post on how to run an open space, which we could push put before PyCon, and a small cheat sheet with a couple of tips on how to run an open space, which we could distribute during PyCon.
* I liked the bot last year and I appreciate all the work that went into making this happen. I also think that it is a good idea to discuss how we can improve the bot, but I wanted to point out that we should also acknowledge that some people won’t use the bot or Twitter so maybe we can think of some other “traditional” ways on how to promote the open spaces, just to make sure we reach as many people as possible.
Thank you! Anna
—— You are appreciated. You are enough. You matter. You are not alone.
On Jan 14, 2018, at 2:25 AM, Hobson Lane <hobsonlane@gmail.com <mailto:hobsonlane@gmail.com>> wrote:
Thank you Trey! Apologies for the late response. Really excited to hear your thinking. Those 3 bullets are spot on! Seems very similar to ideas Anna and I have been batting around since I joined her open spaces team.
If you or Zak want to take a stab at drafting material to support one or all of those 3 bullet points, I'd be happy to help
1. flesh them out 2. incorporate PyCon staff feedback 3. seek approval for publication by PyCon staff 4. get them incorporated into the website and other announcements (maybe even Zak's twitter bot dialog)
I think they'd really advance the quality of the 2018 Open Spaces experience, especially if the Twitter bot can be evolved to incorporate them into its "brain".
Regarding Anna's "High's and Low's" list from last year, some things I observed last year:
* Low: The chatbot was pretty basic and needs work to be made really useful * High: The chatbot was used by more than 50% of the openspace event planners and seemed to get the word out a bit * Low: Some of the open spaces (inluding the one I led) could have benefited from some of Trey's guideance/ideas in his bullet points * High: Tweeting a pic of the board seemed like it helped some people plan their day * High: The board posting went smoothly once we had a board up * High?: Did we accomplish that 2-board approach we planned?
If we can support open spaces organizers with some or all of Trey's ideas/docs this year I'd be super happy.
--Hobson
On Mon, Nov 6, 2017 at 7:30 PM, Trey Hunner <trey@truthful.technology <mailto:trey@truthful.technology>> 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 <annabell.ossowski@gmail.com <mailto:annabell.ossowski@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@python.org <mailto:Pycon-openspaces@python.org> https://mail.python.org/mailman/listinfo/pycon-openspaces <https://mail.python.org/mailman/listinfo/pycon-openspaces>
-- Trey Hunner Truthful Technology, LLC http://truthful.technology <http://truthful.technology/> _______________________________________________ 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>
-- Trey Hunner Truthful Technology, LLC http://truthful.technology <http://truthful.technology/>
_______________________________________________ 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>
_______________________________________________ Pycon-openspaces mailing list Pycon-openspaces@python.org https://mail.python.org/mailman/listinfo/pycon-openspaces
On Thu, Jan 25, 2018 at 9:12 AM, Anna Ossowski <annabell.ossowski@gmail.com> wrote:
Thanks Zak! This looks great! I left a few comments as well.
For distribution I would suggest a number of different approaches:
* A blog post about 2 weeks before the conference * Add the information to the Open Spaces page on the PyCon website. In previous years we also had a section on there encouraging people who already had concrete ideas for Open Spaces, to email us and we would list their idea (and possibly even a time and date) on our website. * Maybe print small posters with the tips and put them up in the Open Spaces rooms?
I love this idea! I can order more of the sign holders we use https://www.staples.com/sign+holders/directory_sign+holders. We can also print the actual signs from the staff office printer. (I think I am in the mood to buy supplies today :D)
That is exactly what I meant :) We could have one on the table by the Open Spaces board, where we also have the cards and pens. And then one in each Open Spaces room. —— You are appreciated. You are enough. You matter. You are not alone.
On Jan 25, 2018, at 9:17 AM, Ewa Jodlowska <ewa@python.org> wrote:
On Thu, Jan 25, 2018 at 9:12 AM, Anna Ossowski <annabell.ossowski@gmail.com <mailto:annabell.ossowski@gmail.com>> wrote: Thanks Zak! This looks great! I left a few comments as well.
For distribution I would suggest a number of different approaches:
* A blog post about 2 weeks before the conference * Add the information to the Open Spaces page on the PyCon website. In previous years we also had a section on there encouraging people who already had concrete ideas for Open Spaces, to email us and we would list their idea (and possibly even a time and date) on our website. * Maybe print small posters with the tips and put them up in the Open Spaces rooms?
I love this idea! I can order more of the sign holders we use https://www.staples.com/sign+holders/directory_sign+holders <https://www.staples.com/sign+holders/directory_sign+holders>. We can also print the actual signs from the staff office printer.
(I think I am in the mood to buy supplies today :D)
Thanks for the feedback y'all, I made some minor changes to the doc in response. Talk to you soon On Thu, Jan 25, 2018 at 7:18 AM, Anna Ossowski <annabell.ossowski@gmail.com> wrote:
That is exactly what I meant :) We could have one on the table by the Open Spaces board, where we also have the cards and pens. And then one in each Open Spaces room.
—— You are appreciated. You are enough. You matter. You are not alone.
On Jan 25, 2018, at 9:17 AM, Ewa Jodlowska <ewa@python.org> wrote:
On Thu, Jan 25, 2018 at 9:12 AM, Anna Ossowski <annabell.ossowski@ gmail.com> wrote:
Thanks Zak! This looks great! I left a few comments as well.
For distribution I would suggest a number of different approaches:
* A blog post about 2 weeks before the conference * Add the information to the Open Spaces page on the PyCon website. In previous years we also had a section on there encouraging people who already had concrete ideas for Open Spaces, to email us and we would list their idea (and possibly even a time and date) on our website. * Maybe print small posters with the tips and put them up in the Open Spaces rooms?
I love this idea! I can order more of the sign holders we use https://www.staples.com/sign+holders/directory_sign+holders. We can also print the actual signs from the staff office printer.
(I think I am in the mood to buy supplies today :D)
_______________________________________________ Pycon-openspaces mailing list Pycon-openspaces@python.org https://mail.python.org/mailman/listinfo/pycon-openspaces
participants (5)
-
Anna Ossowski -
Ewa Jodlowska -
Hobson Lane -
Trey Hunner -
Zak