From hobsonlane at gmail.com  Sat Jan 13 20:25:57 2018
From: hobsonlane at gmail.com (Hobson Lane)
Date: Sat, 13 Jan 2018 17:25:57 -0800
Subject: [Pycon-openspaces] Kicking Off the Open Spaces Planning!!!
In-Reply-To: <CA+SHFS_b2TzFvjnjN6376VEFcZqU0ShDvM5jrVRocuM2ZFk6zg@mail.gmail.com>
References: <62217B42-D991-47DC-AB3D-FA9314E137CC@gmail.com>
 <CA+SHFS_b2TzFvjnjN6376VEFcZqU0ShDvM5jrVRocuM2ZFk6zg@mail.gmail.com>
Message-ID: <CACZ_Dod_xTp8YRAUn1CfHFW2WYh2HWM1oU0O-Un0NYRT1biuzw@mail.gmail.com>

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 at 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 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: <http://mail.python.org/pipermail/pycon-openspaces/attachments/20180113/10208aa3/attachment.html>

From annabell.ossowski at gmail.com  Sun Jan 14 18:20:57 2018
From: annabell.ossowski at gmail.com (Anna Ossowski)
Date: Mon, 15 Jan 2018 00:20:57 +0100
Subject: [Pycon-openspaces] Kicking Off the Open Spaces Planning!!!
In-Reply-To: <CACZ_Dod_xTp8YRAUn1CfHFW2WYh2HWM1oU0O-Un0NYRT1biuzw@mail.gmail.com>
References: <62217B42-D991-47DC-AB3D-FA9314E137CC@gmail.com>
 <CA+SHFS_b2TzFvjnjN6376VEFcZqU0ShDvM5jrVRocuM2ZFk6zg@mail.gmail.com>
 <CACZ_Dod_xTp8YRAUn1CfHFW2WYh2HWM1oU0O-Un0NYRT1biuzw@mail.gmail.com>
Message-ID: <0AB51FFC-372F-4DAD-B0B8-3050D110CDB5@gmail.com>

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 at 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 at truthful.technology <mailto:trey at 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 at gmail.com <mailto: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 <mailto:Pycon-openspaces at 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 at python.org <mailto:Pycon-openspaces at python.org>
> https://mail.python.org/mailman/listinfo/pycon-openspaces <https://mail.python.org/mailman/listinfo/pycon-openspaces>
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pycon-openspaces/attachments/20180115/2c08f354/attachment.html>

From hobsonlane at gmail.com  Sun Jan 14 18:28:56 2018
From: hobsonlane at gmail.com (Hobson Lane)
Date: Sun, 14 Jan 2018 23:28:56 +0000
Subject: [Pycon-openspaces] Kicking Off the Open Spaces Planning!!!
In-Reply-To: <0AB51FFC-372F-4DAD-B0B8-3050D110CDB5@gmail.com>
References: <62217B42-D991-47DC-AB3D-FA9314E137CC@gmail.com>
 <CA+SHFS_b2TzFvjnjN6376VEFcZqU0ShDvM5jrVRocuM2ZFk6zg@mail.gmail.com>
 <CACZ_Dod_xTp8YRAUn1CfHFW2WYh2HWM1oU0O-Un0NYRT1biuzw@mail.gmail.com>
 <0AB51FFC-372F-4DAD-B0B8-3050D110CDB5@gmail.com>
Message-ID: <CACZ_DoetzQ23HQRbyD5yekWFSEcUAt=raAF7bcj9Qs3wPo4c+Q@mail.gmail.com>

Yea that's exactly what I intend to do.

On Sun, Jan 14, 2018, 3:21 PM Anna Ossowski <annabell.ossowski at 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 at 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 at 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 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: <http://mail.python.org/pipermail/pycon-openspaces/attachments/20180114/49d7ddd1/attachment-0001.html>

From zak.kent at gmail.com  Sun Jan 21 23:26:54 2018
From: zak.kent at gmail.com (Zak)
Date: Sun, 21 Jan 2018 20:26:54 -0800
Subject: [Pycon-openspaces] Kicking Off the Open Spaces Planning!!!
In-Reply-To: <CACZ_DoetzQ23HQRbyD5yekWFSEcUAt=raAF7bcj9Qs3wPo4c+Q@mail.gmail.com>
References: <62217B42-D991-47DC-AB3D-FA9314E137CC@gmail.com>
 <CA+SHFS_b2TzFvjnjN6376VEFcZqU0ShDvM5jrVRocuM2ZFk6zg@mail.gmail.com>
 <CACZ_Dod_xTp8YRAUn1CfHFW2WYh2HWM1oU0O-Un0NYRT1biuzw@mail.gmail.com>
 <0AB51FFC-372F-4DAD-B0B8-3050D110CDB5@gmail.com>
 <CACZ_DoetzQ23HQRbyD5yekWFSEcUAt=raAF7bcj9Qs3wPo4c+Q@mail.gmail.com>
Message-ID: <CAGTaL05A+Wr5OCD_3Ew+8c=MYT=XXWNFz31opqtdbGFU35A8sg@mail.gmail.com>

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 at gmail.com> wrote:

> Yea that's exactly what I intend to do.
>
> On Sun, Jan 14, 2018, 3:21 PM Anna Ossowski <annabell.ossowski at 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 at 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 at 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 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: <http://mail.python.org/pipermail/pycon-openspaces/attachments/20180121/d7d801af/attachment.html>

From hobsonlane at gmail.com  Sun Jan 21 23:31:14 2018
From: hobsonlane at gmail.com (Hobson Lane)
Date: Mon, 22 Jan 2018 04:31:14 +0000
Subject: [Pycon-openspaces] Kicking Off the Open Spaces Planning!!!
In-Reply-To: <CAGTaL05A+Wr5OCD_3Ew+8c=MYT=XXWNFz31opqtdbGFU35A8sg@mail.gmail.com>
References: <62217B42-D991-47DC-AB3D-FA9314E137CC@gmail.com>
 <CA+SHFS_b2TzFvjnjN6376VEFcZqU0ShDvM5jrVRocuM2ZFk6zg@mail.gmail.com>
 <CACZ_Dod_xTp8YRAUn1CfHFW2WYh2HWM1oU0O-Un0NYRT1biuzw@mail.gmail.com>
 <0AB51FFC-372F-4DAD-B0B8-3050D110CDB5@gmail.com>
 <CACZ_DoetzQ23HQRbyD5yekWFSEcUAt=raAF7bcj9Qs3wPo4c+Q@mail.gmail.com>
 <CAGTaL05A+Wr5OCD_3Ew+8c=MYT=XXWNFz31opqtdbGFU35A8sg@mail.gmail.com>
Message-ID: <CACZ_Dod5uorCNMkF5qK9pPL50EEqouJ2574y8rF_z+FftezFEw@mail.gmail.com>

Excellent Zak. Thank you.

On Sun, Jan 21, 2018, 8:26 PM Zak <zak.kent at 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 at gmail.com> wrote:
>
>> Yea that's exactly what I intend to do.
>>
>> On Sun, Jan 14, 2018, 3:21 PM Anna Ossowski <annabell.ossowski at 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 at 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 at 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 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: <http://mail.python.org/pipermail/pycon-openspaces/attachments/20180122/1d9e62c0/attachment-0001.html>

From trey at truthful.technology  Tue Jan 23 11:53:30 2018
From: trey at truthful.technology (Trey Hunner)
Date: Tue, 23 Jan 2018 08:53:30 -0800
Subject: [Pycon-openspaces] Kicking Off the Open Spaces Planning!!!
In-Reply-To: <CAGTaL05A+Wr5OCD_3Ew+8c=MYT=XXWNFz31opqtdbGFU35A8sg@mail.gmail.com>
References: <62217B42-D991-47DC-AB3D-FA9314E137CC@gmail.com>
 <CA+SHFS_b2TzFvjnjN6376VEFcZqU0ShDvM5jrVRocuM2ZFk6zg@mail.gmail.com>
 <CACZ_Dod_xTp8YRAUn1CfHFW2WYh2HWM1oU0O-Un0NYRT1biuzw@mail.gmail.com>
 <0AB51FFC-372F-4DAD-B0B8-3050D110CDB5@gmail.com>
 <CACZ_DoetzQ23HQRbyD5yekWFSEcUAt=raAF7bcj9Qs3wPo4c+Q@mail.gmail.com>
 <CAGTaL05A+Wr5OCD_3Ew+8c=MYT=XXWNFz31opqtdbGFU35A8sg@mail.gmail.com>
Message-ID: <CA+SHFS-OEYOVTGo_ESfdfp3oHFxfoNzBDgK5mPDQZrQW+xexqQ@mail.gmail.com>

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 at 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 at gmail.com> wrote:
>
>> Yea that's exactly what I intend to do.
>>
>> On Sun, Jan 14, 2018, 3:21 PM Anna Ossowski <annabell.ossowski at 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 at 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 at 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 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
>>>>
>>>>
>>>
>>>
>


-- 
Trey Hunner
Truthful Technology, LLC
http://truthful.technology
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pycon-openspaces/attachments/20180123/884e0e6c/attachment.html>

From zak.kent at gmail.com  Wed Jan 24 23:51:14 2018
From: zak.kent at gmail.com (Zak)
Date: Wed, 24 Jan 2018 20:51:14 -0800
Subject: [Pycon-openspaces] Kicking Off the Open Spaces Planning!!!
In-Reply-To: <CA+SHFS-OEYOVTGo_ESfdfp3oHFxfoNzBDgK5mPDQZrQW+xexqQ@mail.gmail.com>
References: <62217B42-D991-47DC-AB3D-FA9314E137CC@gmail.com>
 <CA+SHFS_b2TzFvjnjN6376VEFcZqU0ShDvM5jrVRocuM2ZFk6zg@mail.gmail.com>
 <CACZ_Dod_xTp8YRAUn1CfHFW2WYh2HWM1oU0O-Un0NYRT1biuzw@mail.gmail.com>
 <0AB51FFC-372F-4DAD-B0B8-3050D110CDB5@gmail.com>
 <CACZ_DoetzQ23HQRbyD5yekWFSEcUAt=raAF7bcj9Qs3wPo4c+Q@mail.gmail.com>
 <CAGTaL05A+Wr5OCD_3Ew+8c=MYT=XXWNFz31opqtdbGFU35A8sg@mail.gmail.com>
 <CA+SHFS-OEYOVTGo_ESfdfp3oHFxfoNzBDgK5mPDQZrQW+xexqQ@mail.gmail.com>
Message-ID: <CAGTaL07aSTEp_KQcwKBj07eR_D8L4AA+eCdGEZV2-tj=nZ-3Gg@mail.gmail.com>

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 at 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 at 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 at gmail.com>
>> wrote:
>>
>>> Yea that's exactly what I intend to do.
>>>
>>> On Sun, Jan 14, 2018, 3:21 PM Anna Ossowski <annabell.ossowski at 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 at 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 at 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 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
>>>>>
>>>>>
>>>>
>>>>
>>
>
>
> --
> Trey Hunner
> Truthful Technology, LLC
> http://truthful.technology
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pycon-openspaces/attachments/20180124/eed76dfe/attachment-0001.html>

From hobsonlane at gmail.com  Thu Jan 25 06:34:27 2018
From: hobsonlane at gmail.com (Hobson Lane)
Date: Thu, 25 Jan 2018 03:34:27 -0800
Subject: [Pycon-openspaces] Kicking Off the Open Spaces Planning!!!
In-Reply-To: <CAGTaL07aSTEp_KQcwKBj07eR_D8L4AA+eCdGEZV2-tj=nZ-3Gg@mail.gmail.com>
References: <62217B42-D991-47DC-AB3D-FA9314E137CC@gmail.com>
 <CA+SHFS_b2TzFvjnjN6376VEFcZqU0ShDvM5jrVRocuM2ZFk6zg@mail.gmail.com>
 <CACZ_Dod_xTp8YRAUn1CfHFW2WYh2HWM1oU0O-Un0NYRT1biuzw@mail.gmail.com>
 <0AB51FFC-372F-4DAD-B0B8-3050D110CDB5@gmail.com>
 <CACZ_DoetzQ23HQRbyD5yekWFSEcUAt=raAF7bcj9Qs3wPo4c+Q@mail.gmail.com>
 <CAGTaL05A+Wr5OCD_3Ew+8c=MYT=XXWNFz31opqtdbGFU35A8sg@mail.gmail.com>
 <CA+SHFS-OEYOVTGo_ESfdfp3oHFxfoNzBDgK5mPDQZrQW+xexqQ@mail.gmail.com>
 <CAGTaL07aSTEp_KQcwKBj07eR_D8L4AA+eCdGEZV2-tj=nZ-3Gg@mail.gmail.com>
Message-ID: <CACZ_DofdOoK5iL4qUgDm3yQugEnNciKad=CzWZmDV3vfCL5G_w@mail.gmail.com>

Excellent, Zak.

--Hobson


On Wed, Jan 24, 2018 at 8:51 PM, Zak <zak.kent at 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 at 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 at 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 at gmail.com>
>>> wrote:
>>>
>>>> Yea that's exactly what I intend to do.
>>>>
>>>> On Sun, Jan 14, 2018, 3:21 PM Anna Ossowski <
>>>> annabell.ossowski at 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 at 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 at 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 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
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>
>>
>>
>> --
>> Trey Hunner
>> Truthful Technology, LLC
>> http://truthful.technology
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pycon-openspaces/attachments/20180125/91ab5e96/attachment-0001.html>

From ewa at python.org  Thu Jan 25 10:01:37 2018
From: ewa at python.org (Ewa Jodlowska)
Date: Thu, 25 Jan 2018 09:01:37 -0600
Subject: [Pycon-openspaces] Kicking Off the Open Spaces Planning!!!
In-Reply-To: <CACZ_DofdOoK5iL4qUgDm3yQugEnNciKad=CzWZmDV3vfCL5G_w@mail.gmail.com>
References: <62217B42-D991-47DC-AB3D-FA9314E137CC@gmail.com>
 <CA+SHFS_b2TzFvjnjN6376VEFcZqU0ShDvM5jrVRocuM2ZFk6zg@mail.gmail.com>
 <CACZ_Dod_xTp8YRAUn1CfHFW2WYh2HWM1oU0O-Un0NYRT1biuzw@mail.gmail.com>
 <0AB51FFC-372F-4DAD-B0B8-3050D110CDB5@gmail.com>
 <CACZ_DoetzQ23HQRbyD5yekWFSEcUAt=raAF7bcj9Qs3wPo4c+Q@mail.gmail.com>
 <CAGTaL05A+Wr5OCD_3Ew+8c=MYT=XXWNFz31opqtdbGFU35A8sg@mail.gmail.com>
 <CA+SHFS-OEYOVTGo_ESfdfp3oHFxfoNzBDgK5mPDQZrQW+xexqQ@mail.gmail.com>
 <CAGTaL07aSTEp_KQcwKBj07eR_D8L4AA+eCdGEZV2-tj=nZ-3Gg@mail.gmail.com>
 <CACZ_DofdOoK5iL4qUgDm3yQugEnNciKad=CzWZmDV3vfCL5G_w@mail.gmail.com>
Message-ID: <CA+=WmzV+OEYhefnA39OBhRaJdNbfNYSOzykkvBCO103WjT9cwQ@mail.gmail.com>

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 at gmail.com> wrote:

> Excellent, Zak.
>
> --Hobson
>
>
> On Wed, Jan 24, 2018 at 8:51 PM, Zak <zak.kent at 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 at 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 at 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 at gmail.com>
>>>> wrote:
>>>>
>>>>> Yea that's exactly what I intend to do.
>>>>>
>>>>> On Sun, Jan 14, 2018, 3:21 PM Anna Ossowski <
>>>>> annabell.ossowski at 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 at 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 at 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 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
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>
>>>
>>>
>>> --
>>> 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: <http://mail.python.org/pipermail/pycon-openspaces/attachments/20180125/99a441de/attachment-0001.html>

From annabell.ossowski at gmail.com  Thu Jan 25 10:12:07 2018
From: annabell.ossowski at gmail.com (Anna Ossowski)
Date: Thu, 25 Jan 2018 09:12:07 -0600
Subject: [Pycon-openspaces] Kicking Off the Open Spaces Planning!!!
In-Reply-To: <CA+=WmzV+OEYhefnA39OBhRaJdNbfNYSOzykkvBCO103WjT9cwQ@mail.gmail.com>
References: <62217B42-D991-47DC-AB3D-FA9314E137CC@gmail.com>
 <CA+SHFS_b2TzFvjnjN6376VEFcZqU0ShDvM5jrVRocuM2ZFk6zg@mail.gmail.com>
 <CACZ_Dod_xTp8YRAUn1CfHFW2WYh2HWM1oU0O-Un0NYRT1biuzw@mail.gmail.com>
 <0AB51FFC-372F-4DAD-B0B8-3050D110CDB5@gmail.com>
 <CACZ_DoetzQ23HQRbyD5yekWFSEcUAt=raAF7bcj9Qs3wPo4c+Q@mail.gmail.com>
 <CAGTaL05A+Wr5OCD_3Ew+8c=MYT=XXWNFz31opqtdbGFU35A8sg@mail.gmail.com>
 <CA+SHFS-OEYOVTGo_ESfdfp3oHFxfoNzBDgK5mPDQZrQW+xexqQ@mail.gmail.com>
 <CAGTaL07aSTEp_KQcwKBj07eR_D8L4AA+eCdGEZV2-tj=nZ-3Gg@mail.gmail.com>
 <CACZ_DofdOoK5iL4qUgDm3yQugEnNciKad=CzWZmDV3vfCL5G_w@mail.gmail.com>
 <CA+=WmzV+OEYhefnA39OBhRaJdNbfNYSOzykkvBCO103WjT9cwQ@mail.gmail.com>
Message-ID: <0A7BB16B-86B3-4CFD-B68C-2900F5B63629@gmail.com>

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 at 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 at gmail.com <mailto:hobsonlane at gmail.com>> wrote:
> Excellent, Zak.
> 
> --Hobson
> 
> 
> On Wed, Jan 24, 2018 at 8:51 PM, Zak <zak.kent at gmail.com <mailto:zak.kent at 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 <https://docs.google.com/document/d/1scTO9mNxNk2vXbK-_yubvPLH51DCM97u4Jag4HL4-eM/edit?usp=sharing>
> 
> On Tue, Jan 23, 2018 at 8:53 AM, Trey Hunner <trey at truthful.technology <mailto:trey at 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 at gmail.com <mailto:zak.kent at 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 at gmail.com <mailto:hobsonlane at gmail.com>> wrote:
> Yea that's exactly what I intend to do.
> 
> 
> On Sun, Jan 14, 2018, 3:21 PM Anna Ossowski <annabell.ossowski at gmail.com <mailto:annabell.ossowski at 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 at gmail.com <mailto:hobsonlane at 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 at truthful.technology <mailto:trey at 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 at gmail.com <mailto: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 <mailto:Pycon-openspaces at 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 at python.org <mailto:Pycon-openspaces at 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 at python.org <mailto:Pycon-openspaces at python.org>
> https://mail.python.org/mailman/listinfo/pycon-openspaces <https://mail.python.org/mailman/listinfo/pycon-openspaces>
> 
> 
> _______________________________________________
> 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: <http://mail.python.org/pipermail/pycon-openspaces/attachments/20180125/c99190f4/attachment-0001.html>

From ewa at python.org  Thu Jan 25 10:17:06 2018
From: ewa at python.org (Ewa Jodlowska)
Date: Thu, 25 Jan 2018 09:17:06 -0600
Subject: [Pycon-openspaces] Kicking Off the Open Spaces Planning!!!
In-Reply-To: <0A7BB16B-86B3-4CFD-B68C-2900F5B63629@gmail.com>
References: <62217B42-D991-47DC-AB3D-FA9314E137CC@gmail.com>
 <CA+SHFS_b2TzFvjnjN6376VEFcZqU0ShDvM5jrVRocuM2ZFk6zg@mail.gmail.com>
 <CACZ_Dod_xTp8YRAUn1CfHFW2WYh2HWM1oU0O-Un0NYRT1biuzw@mail.gmail.com>
 <0AB51FFC-372F-4DAD-B0B8-3050D110CDB5@gmail.com>
 <CACZ_DoetzQ23HQRbyD5yekWFSEcUAt=raAF7bcj9Qs3wPo4c+Q@mail.gmail.com>
 <CAGTaL05A+Wr5OCD_3Ew+8c=MYT=XXWNFz31opqtdbGFU35A8sg@mail.gmail.com>
 <CA+SHFS-OEYOVTGo_ESfdfp3oHFxfoNzBDgK5mPDQZrQW+xexqQ@mail.gmail.com>
 <CAGTaL07aSTEp_KQcwKBj07eR_D8L4AA+eCdGEZV2-tj=nZ-3Gg@mail.gmail.com>
 <CACZ_DofdOoK5iL4qUgDm3yQugEnNciKad=CzWZmDV3vfCL5G_w@mail.gmail.com>
 <CA+=WmzV+OEYhefnA39OBhRaJdNbfNYSOzykkvBCO103WjT9cwQ@mail.gmail.com>
 <0A7BB16B-86B3-4CFD-B68C-2900F5B63629@gmail.com>
Message-ID: <CA+=WmzW95u67Yx8o__ojg1zwEgcUa0MELhDFWcUfvWiTgX5TPA@mail.gmail.com>

On Thu, Jan 25, 2018 at 9:12 AM, Anna Ossowski <annabell.ossowski at 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)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pycon-openspaces/attachments/20180125/82c6623b/attachment.html>

From annabell.ossowski at gmail.com  Thu Jan 25 10:18:43 2018
From: annabell.ossowski at gmail.com (Anna Ossowski)
Date: Thu, 25 Jan 2018 09:18:43 -0600
Subject: [Pycon-openspaces] Kicking Off the Open Spaces Planning!!!
In-Reply-To: <CA+=WmzW95u67Yx8o__ojg1zwEgcUa0MELhDFWcUfvWiTgX5TPA@mail.gmail.com>
References: <62217B42-D991-47DC-AB3D-FA9314E137CC@gmail.com>
 <CA+SHFS_b2TzFvjnjN6376VEFcZqU0ShDvM5jrVRocuM2ZFk6zg@mail.gmail.com>
 <CACZ_Dod_xTp8YRAUn1CfHFW2WYh2HWM1oU0O-Un0NYRT1biuzw@mail.gmail.com>
 <0AB51FFC-372F-4DAD-B0B8-3050D110CDB5@gmail.com>
 <CACZ_DoetzQ23HQRbyD5yekWFSEcUAt=raAF7bcj9Qs3wPo4c+Q@mail.gmail.com>
 <CAGTaL05A+Wr5OCD_3Ew+8c=MYT=XXWNFz31opqtdbGFU35A8sg@mail.gmail.com>
 <CA+SHFS-OEYOVTGo_ESfdfp3oHFxfoNzBDgK5mPDQZrQW+xexqQ@mail.gmail.com>
 <CAGTaL07aSTEp_KQcwKBj07eR_D8L4AA+eCdGEZV2-tj=nZ-3Gg@mail.gmail.com>
 <CACZ_DofdOoK5iL4qUgDm3yQugEnNciKad=CzWZmDV3vfCL5G_w@mail.gmail.com>
 <CA+=WmzV+OEYhefnA39OBhRaJdNbfNYSOzykkvBCO103WjT9cwQ@mail.gmail.com>
 <0A7BB16B-86B3-4CFD-B68C-2900F5B63629@gmail.com>
 <CA+=WmzW95u67Yx8o__ojg1zwEgcUa0MELhDFWcUfvWiTgX5TPA@mail.gmail.com>
Message-ID: <28FB2C3A-FB24-43B2-B2C9-0FDBDB72B76A@gmail.com>

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 at python.org> wrote:
> 
> On Thu, Jan 25, 2018 at 9:12 AM, Anna Ossowski <annabell.ossowski at gmail.com <mailto:annabell.ossowski at 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)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pycon-openspaces/attachments/20180125/3841d6c1/attachment.html>

From zak.kent at gmail.com  Sun Jan 28 19:24:13 2018
From: zak.kent at gmail.com (Zak)
Date: Sun, 28 Jan 2018 16:24:13 -0800
Subject: [Pycon-openspaces] Kicking Off the Open Spaces Planning!!!
In-Reply-To: <28FB2C3A-FB24-43B2-B2C9-0FDBDB72B76A@gmail.com>
References: <62217B42-D991-47DC-AB3D-FA9314E137CC@gmail.com>
 <CA+SHFS_b2TzFvjnjN6376VEFcZqU0ShDvM5jrVRocuM2ZFk6zg@mail.gmail.com>
 <CACZ_Dod_xTp8YRAUn1CfHFW2WYh2HWM1oU0O-Un0NYRT1biuzw@mail.gmail.com>
 <0AB51FFC-372F-4DAD-B0B8-3050D110CDB5@gmail.com>
 <CACZ_DoetzQ23HQRbyD5yekWFSEcUAt=raAF7bcj9Qs3wPo4c+Q@mail.gmail.com>
 <CAGTaL05A+Wr5OCD_3Ew+8c=MYT=XXWNFz31opqtdbGFU35A8sg@mail.gmail.com>
 <CA+SHFS-OEYOVTGo_ESfdfp3oHFxfoNzBDgK5mPDQZrQW+xexqQ@mail.gmail.com>
 <CAGTaL07aSTEp_KQcwKBj07eR_D8L4AA+eCdGEZV2-tj=nZ-3Gg@mail.gmail.com>
 <CACZ_DofdOoK5iL4qUgDm3yQugEnNciKad=CzWZmDV3vfCL5G_w@mail.gmail.com>
 <CA+=WmzV+OEYhefnA39OBhRaJdNbfNYSOzykkvBCO103WjT9cwQ@mail.gmail.com>
 <0A7BB16B-86B3-4CFD-B68C-2900F5B63629@gmail.com>
 <CA+=WmzW95u67Yx8o__ojg1zwEgcUa0MELhDFWcUfvWiTgX5TPA@mail.gmail.com>
 <28FB2C3A-FB24-43B2-B2C9-0FDBDB72B76A@gmail.com>
Message-ID: <CAGTaL05jtwGDRY-UEgds8+TSUCe6XAeoytC-hHaKo=RY6=A7KA@mail.gmail.com>

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 at 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 at 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 at python.org
> https://mail.python.org/mailman/listinfo/pycon-openspaces
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pycon-openspaces/attachments/20180128/f1da8165/attachment.html>