From ossanna16 at gmx.de  Thu Jan  5 21:21:25 2017
From: ossanna16 at gmx.de (Anna Ossowski)
Date: Fri, 6 Jan 2017 03:21:25 +0100
Subject: [Pycon-openspaces] Pycon-openspaces post from gina@nectarpr.com
 requires approval
In-Reply-To: <mailman.2073.1483569911.2394.pycon-openspaces@python.org>
References: <mailman.2073.1483569911.2394.pycon-openspaces@python.org>
Message-ID: <F636CD06-A8FF-4165-A497-F386D35D2473@gmx.de>

Hey Gina!

Thank you for reaching out!
As you mentioned, the CFP is closed and there are no other speaking slots or panelist sessions available that I?m aware of.
I would encourage Yusuf to organize an Open Space at PyCon and to submit a talk next year before the end of the CFP deadline.

Best,
Anna

---------------------------------
You are appreciated.
You are enough.
You matter.
You are not alone.


> 
> From: Gina Famulari <gina at nectarpr.com>
> Subject: CFP / Panels?
> Date: January 4, 2017 at 11:44:22 PM GMT+1
> To: pycon-openspaces at python.org
> 
> 
> Hi Anna,
> 
> Not sure if you're the best contact for my question, but I was interested in finding out if there are any speaking slots still available. I know the general CFP has closed, but just wanted to check in as Yusuf Simonson <https://www.themuse.com/companies/themuse/people/yusuf>, CTO of TheMuse? <https://www.themuse.com/>is very interested in participating. I would be curious to find out if there are traditional speaking slots or even panelist or break out sessions available.
> 
> Looking forward to hearing from you.
> 
> Thanks in advance!
> Gina 
> 
> -- 
> gina famulari
> nectar communications
> gina at nectarpr.com <mailto:ssmith at nectarpr.com>
> o: 646 854 9808 <tel:646%20854%209808> || m: 631 923 8732 
>  
> 
> 
> 
> 
> From: pycon-openspaces-request at python.org
> Subject: confirm 291fe468e9b2e0fdb6ab05739c5a153a36125632
> Date: January 4, 2017 at 11:45:11 PM GMT+1
> 
> 
> If you reply to this message, keeping the Subject: header intact,
> Mailman will discard the held message.  Do this if the message is
> spam.  If you reply to this message and include an Approved: header
> with the list password in it, the message will be approved for posting
> to the list.  The Approved: header can also appear in the first line
> of the body of the reply.
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pycon-openspaces/attachments/20170106/92f7fa82/attachment.html>

From ossanna16 at gmx.de  Thu Jan  5 22:32:32 2017
From: ossanna16 at gmx.de (Anna Ossowski)
Date: Fri, 6 Jan 2017 04:32:32 +0100
Subject: [Pycon-openspaces] Open Spaces 2017 Kick Off!
Message-ID: <5CF5E3BC-0F73-43CB-9A5C-4A275867E57B@gmx.de>

Hello everyone and Happy New Year!

The beginning of the new year means that PyCon is only a little over 4 months away and it?s time to kick off Open Spaces planning.

First of all I would like to welcome our new Open Spaces co-chair, Trey Hunner, again. Trey, I?m so happy to have you on board :)

During our weekly call Trey and I brainstormed a few ideas on how to improve the Open Spaces this year. I think we did a pretty great job with the Open Spaces last year, they were successful and everything went smoothly, but there is always room for improvements. I wanted to summarize our ideas here for everyone to read. I also added everything to our Open Spaces Trello board. 
Trey, Hobson, and Brandon, you all should have access to the Trello board. 
Ewa, please let me know if you?d like to be added as well.
Everyone is of course welcome to add their own ideas to the Trello board.

Here?s a summary of what Trey and I discussed:

What worked last year:

* We should add a section about the Open Spaces to the PyCon website. There was a section last year but it looks like this hasn?t been transferred to this year?s website.

* We should continue tweeting about the Open Spaces using #pyconopenspace. Taking a picture of the board a few times day and tweeting it out for attendees to see would also be a good idea.

* We should write another blog post about the Open Spaces and maybe try to have it added to some popular Python newsletters to gain more visibility.


Ideas/To Discuss:

* How can we make the Open Spaces board more visible? The board last year was beautiful following the PyCon color scheme but it might have been too easy to walk by/not visible enough. Can we make it more visible by getting the board printed in brighter colors? Other ideas?

* It might be a good idea to add a small column to the printed hand-out schedule indicating the Open Spaces. Attendees could then go ahead and mark their schedule with an ?X? for the times they are planning on attending an Open Space.

* Can we add a column about the Open Spaces to Guidebook? This might be useful to make attendees aware of the Open Spaces. We could also add a simple section to Guidebook explaining what Open Spaces are and how to ?sign up?.

* We could ask the registration desk workers to make people aware of the Open Spaces board when they register. The board is right next to the registration desk.

* In general it might be useful to write a short script for registration desk workers indicating what information to forward to attendees, specifically things that may not be as obvious like the hallway track, what to do in the evenings, PyLadies auction, Open Spaces, etc. This may not be possible doing busy times but at least when time allows.

* Can we keep the Open Spaces going during sprints? We could maybe add a column to the sprints board letting people add cards for Open Spaces. Maybe there is an extra room available. If not we could do it ?pick your own location?-style.

* We could create a short slideshow targeted at people who are attending PyCon for the first time and send it to meetup organizers to be presented at their meetups before PyCon. The slide show could include everything first time attendees may not be aware of like the Open Spaces, PyLadies auction, Education Summit, hallway track, evening activities, etc.
(Side note: DjangoCon US this year had a 1 hour event for first time DjangoCon attendees which took place the afternoon before the talk part of the conference started. It was very successful and well received by attendees. It was comparable to the introduction to sprints workshop at PyCon. It may be worth considering doing something like this at PyCon as well.)

I would love to hear your thoughts on all of those ideas and welcome you to share your own ideas as well.

I look forward to working with all of you again!

Warm regards,
Anna


---------------------------------
You are appreciated.
You are enough.
You matter.
You are not alone.




From pycon.brandon at gmail.com  Fri Jan  6 01:02:39 2017
From: pycon.brandon at gmail.com (Brandon Rhodes)
Date: Fri, 6 Jan 2017 01:02:39 -0500
Subject: [Pycon-openspaces] Open Spaces 2017 Kick Off!
In-Reply-To: <5CF5E3BC-0F73-43CB-9A5C-4A275867E57B@gmx.de>
References: <5CF5E3BC-0F73-43CB-9A5C-4A275867E57B@gmx.de>
Message-ID: <CAD05_otZc9XU+sY1MJWobFkWdAhLa4=bo4C4gaE6vt+e-4LSLQ@mail.gmail.com>

Thank you for all of this work, Anna and Trey ? I am very happy, again for
this year, to have an excited and engaged Open Spaces team ? this will only
be the second year ever that we have Chairs of Open Spaces, and I look
forward to seeing yet another year of the spaces becoming ever more
valuable to the conference!

I am in San Francisco this week visiting my employer (Dropbox), which
leaves me a bit bandwidth-limited for answering emails, but I look forward
to diving into these ideas late this weekend when I am home again snuggled
up with the cats, and can respond in detail.

Quick question: the staff list currently on the 2017 site (which maybe was
just cut and pasted from last year?) lists Hobson as the co-chair. I assume
that he should now be removed, and that I should add Trey (hi, Trey!) in
that slot for this year?

(If so: then, as the Conference Chair, I am happy to welcome to your new
official volunteer role!)

On Thu, Jan 5, 2017 at 10:32 PM, Anna Ossowski <ossanna16 at gmx.de> wrote:

> Hello everyone and Happy New Year!
>
> The beginning of the new year means that PyCon is only a little over 4
> months away and it?s time to kick off Open Spaces planning.
>
> First of all I would like to welcome our new Open Spaces co-chair, Trey
> Hunner, again. Trey, I?m so happy to have you on board :)
>
> During our weekly call Trey and I brainstormed a few ideas on how to
> improve the Open Spaces this year. I think we did a pretty great job with
> the Open Spaces last year, they were successful and everything went
> smoothly, but there is always room for improvements. I wanted to summarize
> our ideas here for everyone to read. I also added everything to our Open
> Spaces Trello board.
> Trey, Hobson, and Brandon, you all should have access to the Trello board.
> Ewa, please let me know if you?d like to be added as well.
> Everyone is of course welcome to add their own ideas to the Trello board.
>
> Here?s a summary of what Trey and I discussed:
>
> What worked last year:
>
> * We should add a section about the Open Spaces to the PyCon website.
> There was a section last year but it looks like this hasn?t been
> transferred to this year?s website.
>
> * We should continue tweeting about the Open Spaces using #pyconopenspace.
> Taking a picture of the board a few times day and tweeting it out for
> attendees to see would also be a good idea.
>
> * We should write another blog post about the Open Spaces and maybe try to
> have it added to some popular Python newsletters to gain more visibility.
>
>
> Ideas/To Discuss:
>
> * How can we make the Open Spaces board more visible? The board last year
> was beautiful following the PyCon color scheme but it might have been too
> easy to walk by/not visible enough. Can we make it more visible by getting
> the board printed in brighter colors? Other ideas?
>
> * It might be a good idea to add a small column to the printed hand-out
> schedule indicating the Open Spaces. Attendees could then go ahead and mark
> their schedule with an ?X? for the times they are planning on attending an
> Open Space.
>
> * Can we add a column about the Open Spaces to Guidebook? This might be
> useful to make attendees aware of the Open Spaces. We could also add a
> simple section to Guidebook explaining what Open Spaces are and how to
> ?sign up?.
>
> * We could ask the registration desk workers to make people aware of the
> Open Spaces board when they register. The board is right next to the
> registration desk.
>
> * In general it might be useful to write a short script for registration
> desk workers indicating what information to forward to attendees,
> specifically things that may not be as obvious like the hallway track, what
> to do in the evenings, PyLadies auction, Open Spaces, etc. This may not be
> possible doing busy times but at least when time allows.
>
> * Can we keep the Open Spaces going during sprints? We could maybe add a
> column to the sprints board letting people add cards for Open Spaces. Maybe
> there is an extra room available. If not we could do it ?pick your own
> location?-style.
>
> * We could create a short slideshow targeted at people who are attending
> PyCon for the first time and send it to meetup organizers to be presented
> at their meetups before PyCon. The slide show could include everything
> first time attendees may not be aware of like the Open Spaces, PyLadies
> auction, Education Summit, hallway track, evening activities, etc.
> (Side note: DjangoCon US this year had a 1 hour event for first time
> DjangoCon attendees which took place the afternoon before the talk part of
> the conference started. It was very successful and well received by
> attendees. It was comparable to the introduction to sprints workshop at
> PyCon. It may be worth considering doing something like this at PyCon as
> well.)
>
> I would love to hear your thoughts on all of those ideas and welcome you
> to share your own ideas as well.
>
> I look forward to working with all of you again!
>
> Warm regards,
> 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
>



-- 
Brandon Rhodes
PyCon 2016 Conference Chair
pycon.brandon at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pycon-openspaces/attachments/20170106/69d5238b/attachment-0001.html>

From ossanna16 at gmx.de  Fri Jan  6 01:16:21 2017
From: ossanna16 at gmx.de (Anna Ossowski)
Date: Fri, 6 Jan 2017 07:16:21 +0100
Subject: [Pycon-openspaces] Fwd:  Open Spaces 2017 Kick Off!
References: <46F535CC-47B6-4C6C-8BEB-1EA0250FC775@gmx.de>
Message-ID: <6AFACDFE-5C49-4937-A21E-D95FD3244D84@gmx.de>

Oops, I forgot to hit the ?reply to all? button. My apologies.



> Begin forwarded message:
> 
> From: Anna Ossowski <ossanna16 at gmx.de>
> Subject: Re: [Pycon-openspaces] Open Spaces 2017 Kick Off!
> Date: January 6, 2017 at 7:15:25 AM GMT+1
> To: Brandon Rhodes <pycon.brandon at gmail.com>
> 
> Hey Brandon!
> 
> Hobson is still on our team as co-chair this year, which I?m thankful for :) Kinga stepped down and Trey stepped up as our second co-chair so yes it would be great if Trey could be added to the website as well. I didn?t even think about that so thank you for mentioning it!
> 
> I look forward to reading your thoughts later this week. Have a great time in sunny San Francisco! (It?s really cold and snowy here in Germany so I?m a little envious :) )
> Anna
> 
> ---------------------------------
> You are appreciated.
> You are enough.
> You matter.
> You are not alone.
> 
> 
> 
>> On Jan 6, 2017, at 7:02 AM, Brandon Rhodes <pycon.brandon at gmail.com <mailto:pycon.brandon at gmail.com>> wrote:
>> 
>> Thank you for all of this work, Anna and Trey ? I am very happy, again for this year, to have an excited and engaged Open Spaces team ? this will only be the second year ever that we have Chairs of Open Spaces, and I look forward to seeing yet another year of the spaces becoming ever more valuable to the conference!
>> 
>> I am in San Francisco this week visiting my employer (Dropbox), which leaves me a bit bandwidth-limited for answering emails, but I look forward to diving into these ideas late this weekend when I am home again snuggled up with the cats, and can respond in detail.
>> 
>> Quick question: the staff list currently on the 2017 site (which maybe was just cut and pasted from last year?) lists Hobson as the co-chair. I assume that he should now be removed, and that I should add Trey (hi, Trey!) in that slot for this year?
>> 
>> (If so: then, as the Conference Chair, I am happy to welcome to your new official volunteer role!)
>> 
>> On Thu, Jan 5, 2017 at 10:32 PM, Anna Ossowski <ossanna16 at gmx.de <mailto:ossanna16 at gmx.de>> wrote:
>> Hello everyone and Happy New Year!
>> 
>> The beginning of the new year means that PyCon is only a little over 4 months away and it?s time to kick off Open Spaces planning.
>> 
>> First of all I would like to welcome our new Open Spaces co-chair, Trey Hunner, again. Trey, I?m so happy to have you on board :)
>> 
>> During our weekly call Trey and I brainstormed a few ideas on how to improve the Open Spaces this year. I think we did a pretty great job with the Open Spaces last year, they were successful and everything went smoothly, but there is always room for improvements. I wanted to summarize our ideas here for everyone to read. I also added everything to our Open Spaces Trello board.
>> Trey, Hobson, and Brandon, you all should have access to the Trello board.
>> Ewa, please let me know if you?d like to be added as well.
>> Everyone is of course welcome to add their own ideas to the Trello board.
>> 
>> Here?s a summary of what Trey and I discussed:
>> 
>> What worked last year:
>> 
>> * We should add a section about the Open Spaces to the PyCon website. There was a section last year but it looks like this hasn?t been transferred to this year?s website.
>> 
>> * We should continue tweeting about the Open Spaces using #pyconopenspace. Taking a picture of the board a few times day and tweeting it out for attendees to see would also be a good idea.
>> 
>> * We should write another blog post about the Open Spaces and maybe try to have it added to some popular Python newsletters to gain more visibility.
>> 
>> 
>> Ideas/To Discuss:
>> 
>> * How can we make the Open Spaces board more visible? The board last year was beautiful following the PyCon color scheme but it might have been too easy to walk by/not visible enough. Can we make it more visible by getting the board printed in brighter colors? Other ideas?
>> 
>> * It might be a good idea to add a small column to the printed hand-out schedule indicating the Open Spaces. Attendees could then go ahead and mark their schedule with an ?X? for the times they are planning on attending an Open Space.
>> 
>> * Can we add a column about the Open Spaces to Guidebook? This might be useful to make attendees aware of the Open Spaces. We could also add a simple section to Guidebook explaining what Open Spaces are and how to ?sign up?.
>> 
>> * We could ask the registration desk workers to make people aware of the Open Spaces board when they register. The board is right next to the registration desk.
>> 
>> * In general it might be useful to write a short script for registration desk workers indicating what information to forward to attendees, specifically things that may not be as obvious like the hallway track, what to do in the evenings, PyLadies auction, Open Spaces, etc. This may not be possible doing busy times but at least when time allows.
>> 
>> * Can we keep the Open Spaces going during sprints? We could maybe add a column to the sprints board letting people add cards for Open Spaces. Maybe there is an extra room available. If not we could do it ?pick your own location?-style.
>> 
>> * We could create a short slideshow targeted at people who are attending PyCon for the first time and send it to meetup organizers to be presented at their meetups before PyCon. The slide show could include everything first time attendees may not be aware of like the Open Spaces, PyLadies auction, Education Summit, hallway track, evening activities, etc.
>> (Side note: DjangoCon US this year had a 1 hour event for first time DjangoCon attendees which took place the afternoon before the talk part of the conference started. It was very successful and well received by attendees. It was comparable to the introduction to sprints workshop at PyCon. It may be worth considering doing something like this at PyCon as well.)
>> 
>> I would love to hear your thoughts on all of those ideas and welcome you to share your own ideas as well.
>> 
>> I look forward to working with all of you again!
>> 
>> Warm regards,
>> 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>
>> 
>> 
>> 
>> -- 
>> Brandon Rhodes
>> PyCon 2016 Conference Chair
>> pycon.brandon at gmail.com <mailto:pycon.brandon at gmail.com>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pycon-openspaces/attachments/20170106/06f11c95/attachment.html>

From ewa at python.org  Fri Jan  6 09:27:41 2017
From: ewa at python.org (Ewa Jodlowska)
Date: Fri, 6 Jan 2017 08:27:41 -0600
Subject: [Pycon-openspaces] Open Spaces 2017 Kick Off!
In-Reply-To: <CAD05_otZc9XU+sY1MJWobFkWdAhLa4=bo4C4gaE6vt+e-4LSLQ@mail.gmail.com>
References: <5CF5E3BC-0F73-43CB-9A5C-4A275867E57B@gmx.de>
 <CAD05_otZc9XU+sY1MJWobFkWdAhLa4=bo4C4gaE6vt+e-4LSLQ@mail.gmail.com>
Message-ID: <CADx+GQMHdtgfgkqEHLbC=dJQnvVkdKRXFRsJF6BsEeKFVg5+kw@mail.gmail.com>

On Fri, Jan 6, 2017 at 12:02 AM, Brandon Rhodes <pycon.brandon at gmail.com>
wrote:

> Thank you for all of this work, Anna and Trey ? I am very happy, again for
> this year, to have an excited and engaged Open Spaces team ? this will only
> be the second year ever that we have Chairs of Open Spaces, and I look
> forward to seeing yet another year of the spaces becoming ever more
> valuable to the conference!
>
> I am in San Francisco this week visiting my employer (Dropbox), which
> leaves me a bit bandwidth-limited for answering emails, but I look forward
> to diving into these ideas late this weekend when I am home again snuggled
> up with the cats, and can respond in detail.
>
> Quick question: the staff list currently on the 2017 site (which maybe was
> just cut and pasted from last year?) lists Hobson as the co-chair. I assume
> that he should now be removed, and that I should add Trey (hi, Trey!) in
> that slot for this year?
>

It is being updating as changes are made known to me. I will update it to
Trey.

Trey - please also join:
https://mail.python.org/mailman/listinfo/pycon-staff.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pycon-openspaces/attachments/20170106/240a0a23/attachment-0001.html>

From ewa at python.org  Fri Jan  6 09:46:53 2017
From: ewa at python.org (Ewa Jodlowska)
Date: Fri, 6 Jan 2017 08:46:53 -0600
Subject: [Pycon-openspaces] Open Spaces 2017 Kick Off!
In-Reply-To: <5CF5E3BC-0F73-43CB-9A5C-4A275867E57B@gmx.de>
References: <5CF5E3BC-0F73-43CB-9A5C-4A275867E57B@gmx.de>
Message-ID: <CADx+GQM400JLoMbRzvNDMqNYDCQP8-_c8FzgzYgvo-VPY3GRLA@mail.gmail.com>

On Thu, Jan 5, 2017 at 9:32 PM, Anna Ossowski <ossanna16 at gmx.de> wrote:

[clipped]

>
> * We should add a section about the Open Spaces to the PyCon website.
> There was a section last year but it looks like this hasn?t been
> transferred to this year?s website.
>

The work flow for the website is once something is ready to launch, we add
it to the website. This way things do not get overlooked and go "stale". If
you would like to let me know what text you want on it, I can add the page
for you. After that you will have edit rights so you can change whatever is
needed. Attached is last year's text.

>
> * We should continue tweeting about the Open Spaces using #pyconopenspace.
> Taking a picture of the board a few times day and tweeting it out for
> attendees to see would also be a good idea.
>
> * We should write another blog post about the Open Spaces and maybe try to
> have it added to some popular Python newsletters to gain more visibility.
>
>
> Ideas/To Discuss:
>
>
> [clipped]

>
> * In general it might be useful to write a short script for registration
> desk workers indicating what information to forward to attendees,
> specifically things that may not be as obvious like the hallway track, what
> to do in the evenings, PyLadies auction, Open Spaces, etc. This may not be
> possible doing busy times but at least when time allows.
>

I'm going to chime in on two points and leave the rest to Brandon.

Point 1 is regarding info at registration: having the volunteers verbally
mention all of these things will hold up the lines, especially the first
day of tutorials and the first day of the conference, which are the two
days that almost all people check-in. During the mornings there are super
long lines with people trying to get checked in in time for their tutorials
and/or the opening plenary. I do not want to strain that process further.
Here we have two options to consider:

   1. Have a short handout with bulleted FYIs. Open Spaces can be one of
   them. This handout can be given to each person that checks in. The downside
   is that it is just another thing that someone gets at registration. Not
   sure how effective it will be.
   2. For those busy check-in times, have a short handout with bulleted
   FYIs. Open Spaces can be one of them. After the busy times, we can have the
   people verbally mention it. However, I am not sure how much we retain
   during that interaction. As an attendee myself (actually going to a
   conference this following week) I tend to be over stimulated at check-in
   and don't retain what is verbally said to me. I tend to go back through
   what was given to me to make sure I did not miss anything.

Personally, I think adding it to the printed schedule and to the Guidebook
is the best way forward.

>
> * Can we keep the Open Spaces going during sprints? We could maybe add a
> column to the sprints board letting people add cards for Open Spaces. Maybe
> there is an extra room available. If not we could do it ?pick your own
> location?-style.
>

>From what I see, this tends to happen naturally. When Sprinters are onsite
and they want to meet with a few people to discuss anything, they find
their own space and it happens. In Portland we have an unusual amount of
space available for Sprints, which will not be the case for 2018 and 2019.
We can try it in 2017, but I cannot guarantee that I will have enough space
in 2018/19 to give to this.

For 2017, the D rooms (if you visualize walking to the Portland Ballroom on
the lower level, the D rooms were the small rooms on the right) can be used
for this effort because in 2016 that section was completely abandoned
during Sprints since there was so much space in the Portland Ballrooms.
There was no need for people to be so far away from the rest.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pycon-openspaces/attachments/20170106/32067fd7/attachment.html>

From hobsonlane at gmail.com  Fri Jan  6 12:45:57 2017
From: hobsonlane at gmail.com (Hobson Lane)
Date: Fri, 6 Jan 2017 09:45:57 -0800
Subject: [Pycon-openspaces] Fwd: Open Spaces 2017 Kick Off!
In-Reply-To: <6AFACDFE-5C49-4937-A21E-D95FD3244D84@gmx.de>
References: <46F535CC-47B6-4C6C-8BEB-1EA0250FC775@gmx.de>
 <6AFACDFE-5C49-4937-A21E-D95FD3244D84@gmx.de>
Message-ID: <CACZ_DodC1iv99e4qYCJAm5dhf6SF4whX0724+E+9DFproK3bDQ@mail.gmail.com>

One way I could contribute is to build a twitter bot to maintain a calendar
of open space events.

The open space bot would:

- Receive and parse tweets from open space organizers when they post a
proposal on the board
- Retweet the proposal at an appropriate schedule based on the openspace
schedule (say 15 minutes before the scheduled start time)
- Maintain a basic webpage showing that schedule of open spaces which it
would link to in its tweets.

I'd curate the time/location information in the tweets and its calendar of
open spaces, and I could transfer it to any other spreadsheets where you
need to maintain an open space schedule for the GuideBook app, etc.
Organizers (at their wim) could tweet to the bot if they see an open space
proposal go up on the board that they'd like included in the retweet
schedule.

Since it would only augment the poster board (the official schedule), it
shouldn't interfere with your normal workflow and only increase the
exposure for open spaces whose organizers decide to use it. And I'd take
full responsibility for maintaining it and keeping it from retweeting
anything inappropriate.

The twitter bot would be pure python, all open source. I've built similar
bots in the past. If attendees seem interested, I could hold an open space
and/or a lightning talk to describe how it works and help others build
similar bots for their organizations.

--Hobson
(503) 974-6274


On Thu, Jan 5, 2017 at 10:16 PM, Anna Ossowski <ossanna16 at gmx.de> wrote:

> Oops, I forgot to hit the ?reply to all? button. My apologies.
>
>
>
> Begin forwarded message:
>
> *From: *Anna Ossowski <ossanna16 at gmx.de>
> *Subject: **Re: [Pycon-openspaces] Open Spaces 2017 Kick Off!*
> *Date: *January 6, 2017 at 7:15:25 AM GMT+1
> *To: *Brandon Rhodes <pycon.brandon at gmail.com>
>
> Hey Brandon!
>
> Hobson is still on our team as co-chair this year, which I?m thankful for
> :) Kinga stepped down and Trey stepped up as our second co-chair so yes it
> would be great if Trey could be added to the website as well. I didn?t even
> think about that so thank you for mentioning it!
>
> I look forward to reading your thoughts later this week. Have a great time
> in sunny San Francisco! (It?s really cold and snowy here in Germany so I?m
> a little envious :) )
> Anna
>
> ---------------------------------
> You are appreciated.
> You are enough.
> You matter.
> You are not alone.
>
>
>
> On Jan 6, 2017, at 7:02 AM, Brandon Rhodes <pycon.brandon at gmail.com>
> wrote:
>
> Thank you for all of this work, Anna and Trey ? I am very happy, again for
> this year, to have an excited and engaged Open Spaces team ? this will only
> be the second year ever that we have Chairs of Open Spaces, and I look
> forward to seeing yet another year of the spaces becoming ever more
> valuable to the conference!
>
> I am in San Francisco this week visiting my employer (Dropbox), which
> leaves me a bit bandwidth-limited for answering emails, but I look forward
> to diving into these ideas late this weekend when I am home again snuggled
> up with the cats, and can respond in detail.
>
> Quick question: the staff list currently on the 2017 site (which maybe was
> just cut and pasted from last year?) lists Hobson as the co-chair. I assume
> that he should now be removed, and that I should add Trey (hi, Trey!) in
> that slot for this year?
>
> (If so: then, as the Conference Chair, I am happy to welcome to your new
> official volunteer role!)
>
> On Thu, Jan 5, 2017 at 10:32 PM, Anna Ossowski <ossanna16 at gmx.de> wrote:
>
>> Hello everyone and Happy New Year!
>>
>> The beginning of the new year means that PyCon is only a little over 4
>> months away and it?s time to kick off Open Spaces planning.
>>
>> First of all I would like to welcome our new Open Spaces co-chair, Trey
>> Hunner, again. Trey, I?m so happy to have you on board :)
>>
>> During our weekly call Trey and I brainstormed a few ideas on how to
>> improve the Open Spaces this year. I think we did a pretty great job with
>> the Open Spaces last year, they were successful and everything went
>> smoothly, but there is always room for improvements. I wanted to summarize
>> our ideas here for everyone to read. I also added everything to our Open
>> Spaces Trello board.
>> Trey, Hobson, and Brandon, you all should have access to the Trello board.
>> Ewa, please let me know if you?d like to be added as well.
>> Everyone is of course welcome to add their own ideas to the Trello board.
>>
>> Here?s a summary of what Trey and I discussed:
>>
>> What worked last year:
>>
>> * We should add a section about the Open Spaces to the PyCon website.
>> There was a section last year but it looks like this hasn?t been
>> transferred to this year?s website.
>>
>> * We should continue tweeting about the Open Spaces using
>> #pyconopenspace. Taking a picture of the board a few times day and tweeting
>> it out for attendees to see would also be a good idea.
>>
>> * We should write another blog post about the Open Spaces and maybe try
>> to have it added to some popular Python newsletters to gain more visibility.
>>
>>
>> Ideas/To Discuss:
>>
>> * How can we make the Open Spaces board more visible? The board last year
>> was beautiful following the PyCon color scheme but it might have been too
>> easy to walk by/not visible enough. Can we make it more visible by getting
>> the board printed in brighter colors? Other ideas?
>>
>> * It might be a good idea to add a small column to the printed hand-out
>> schedule indicating the Open Spaces. Attendees could then go ahead and mark
>> their schedule with an ?X? for the times they are planning on attending an
>> Open Space.
>>
>> * Can we add a column about the Open Spaces to Guidebook? This might be
>> useful to make attendees aware of the Open Spaces. We could also add a
>> simple section to Guidebook explaining what Open Spaces are and how to
>> ?sign up?.
>>
>> * We could ask the registration desk workers to make people aware of the
>> Open Spaces board when they register. The board is right next to the
>> registration desk.
>>
>> * In general it might be useful to write a short script for registration
>> desk workers indicating what information to forward to attendees,
>> specifically things that may not be as obvious like the hallway track, what
>> to do in the evenings, PyLadies auction, Open Spaces, etc. This may not be
>> possible doing busy times but at least when time allows.
>>
>> * Can we keep the Open Spaces going during sprints? We could maybe add a
>> column to the sprints board letting people add cards for Open Spaces. Maybe
>> there is an extra room available. If not we could do it ?pick your own
>> location?-style.
>>
>> * We could create a short slideshow targeted at people who are attending
>> PyCon for the first time and send it to meetup organizers to be presented
>> at their meetups before PyCon. The slide show could include everything
>> first time attendees may not be aware of like the Open Spaces, PyLadies
>> auction, Education Summit, hallway track, evening activities, etc.
>> (Side note: DjangoCon US this year had a 1 hour event for first time
>> DjangoCon attendees which took place the afternoon before the talk part of
>> the conference started. It was very successful and well received by
>> attendees. It was comparable to the introduction to sprints workshop at
>> PyCon. It may be worth considering doing something like this at PyCon as
>> well.)
>>
>> I would love to hear your thoughts on all of those ideas and welcome you
>> to share your own ideas as well.
>>
>> I look forward to working with all of you again!
>>
>> Warm regards,
>> 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
>>
>
>
>
> --
> Brandon Rhodes
> PyCon 2016 Conference Chair
> pycon.brandon at gmail.com
>
>
>
>
> _______________________________________________
> 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/20170106/7c88455a/attachment.html>

From ossanna16 at gmx.de  Fri Jan  6 19:58:36 2017
From: ossanna16 at gmx.de (Anna Ossowski)
Date: Sat, 7 Jan 2017 01:58:36 +0100
Subject: [Pycon-openspaces] Open Spaces 2017 Kick Off!
In-Reply-To: <CB767435-7AD3-4ED8-9C30-E4979503D81A@gmx.de>
References: <46F535CC-47B6-4C6C-8BEB-1EA0250FC775@gmx.de>
 <6AFACDFE-5C49-4937-A21E-D95FD3244D84@gmx.de>
 <CACZ_DodC1iv99e4qYCJAm5dhf6SF4whX0724+E+9DFproK3bDQ@mail.gmail.com>
 <CB767435-7AD3-4ED8-9C30-E4979503D81A@gmx.de>
Message-ID: <893B5A78-57D8-4657-A609-86EF38EA7399@gmx.de>

I?m sorry! I failed at hitting the ?reply to all? button again.


> On Jan 7, 2017, at 1:57 AM, Anna Ossowski <ossanna16 at gmx.de> wrote:
> 
> Hobson, I like that idea a lot!
> 
> Just to clarify, your bot would parse tweets using the hashtag #pyconopenspace and retweet those, is that correct?
> 
> I think it would be a good idea to have the bot retweet the tweets as soon as they go up and then additionally 15 minutes before the actual Open Space is happening to remind people of it. What do you think? Would that be possible?
> 
> Also a great idea to maintain a basic overview/schedule website of all Open Spaces that were sent to the bot.
> 
> A lightning talk, as well as an Open Space about the topic, would be excellent! Especially the lightning talk would be great promotion for the Open Spaces as well. You could consider submitting a talk proposal for this topic next year. It?s a cool and hands-on idea. Definitely a talk I would love to see at PyCon.
> 
> Thank you, Hobson, and have a good weekend! :)
> Anna
> 
> ---------------------------------
> You are appreciated.
> You are enough.
> You matter.
> You are not alone.
> 
> 
> 
>> On Jan 6, 2017, at 6:45 PM, Hobson Lane <hobsonlane at gmail.com <mailto:hobsonlane at gmail.com>> wrote:
>> 
>> One way I could contribute is to build a twitter bot to maintain a calendar of open space events.
>> 
>> The open space bot would: 
>> 
>> - Receive and parse tweets from open space organizers when they post a proposal on the board
>> - Retweet the proposal at an appropriate schedule based on the openspace schedule (say 15 minutes before the scheduled start time)
>> - Maintain a basic webpage showing that schedule of open spaces which it would link to in its tweets.
>> 
>> I'd curate the time/location information in the tweets and its calendar of open spaces, and I could transfer it to any other spreadsheets where you need to maintain an open space schedule for the GuideBook app, etc. Organizers (at their wim) could tweet to the bot if they see an open space proposal go up on the board that they'd like included in the retweet schedule.
>> 
>> Since it would only augment the poster board (the official schedule), it shouldn't interfere with your normal workflow and only increase the exposure for open spaces whose organizers decide to use it. And I'd take full responsibility for maintaining it and keeping it from retweeting anything inappropriate.
>> 
>> The twitter bot would be pure python, all open source. I've built similar bots in the past. If attendees seem interested, I could hold an open space and/or a lightning talk to describe how it works and help others build similar bots for their organizations.
>> 
>> --Hobson
>> (503) 974-6274
>> 
>> 
>> On Thu, Jan 5, 2017 at 10:16 PM, Anna Ossowski <ossanna16 at gmx.de <mailto:ossanna16 at gmx.de>> wrote:
>> Oops, I forgot to hit the ?reply to all? button. My apologies.
>> 
>> 
>> 
>>> Begin forwarded message:
>>> 
>>> From: Anna Ossowski <ossanna16 at gmx.de <mailto:ossanna16 at gmx.de>>
>>> Subject: Re: [Pycon-openspaces] Open Spaces 2017 Kick Off!
>>> Date: January 6, 2017 at 7:15:25 AM GMT+1
>>> To: Brandon Rhodes <pycon.brandon at gmail.com <mailto:pycon.brandon at gmail.com>>
>>> 
>>> Hey Brandon!
>>> 
>>> Hobson is still on our team as co-chair this year, which I?m thankful for :) Kinga stepped down and Trey stepped up as our second co-chair so yes it would be great if Trey could be added to the website as well. I didn?t even think about that so thank you for mentioning it!
>>> 
>>> I look forward to reading your thoughts later this week. Have a great time in sunny San Francisco! (It?s really cold and snowy here in Germany so I?m a little envious :) )
>>> Anna
>>> 
>>> ---------------------------------
>>> You are appreciated.
>>> You are enough.
>>> You matter.
>>> You are not alone.
>>> 
>>> 
>>> 
>>>> On Jan 6, 2017, at 7:02 AM, Brandon Rhodes <pycon.brandon at gmail.com <mailto:pycon.brandon at gmail.com>> wrote:
>>>> 
>>>> Thank you for all of this work, Anna and Trey ? I am very happy, again for this year, to have an excited and engaged Open Spaces team ? this will only be the second year ever that we have Chairs of Open Spaces, and I look forward to seeing yet another year of the spaces becoming ever more valuable to the conference!
>>>> 
>>>> I am in San Francisco this week visiting my employer (Dropbox), which leaves me a bit bandwidth-limited for answering emails, but I look forward to diving into these ideas late this weekend when I am home again snuggled up with the cats, and can respond in detail.
>>>> 
>>>> Quick question: the staff list currently on the 2017 site (which maybe was just cut and pasted from last year?) lists Hobson as the co-chair. I assume that he should now be removed, and that I should add Trey (hi, Trey!) in that slot for this year?
>>>> 
>>>> (If so: then, as the Conference Chair, I am happy to welcome to your new official volunteer role!)
>>>> 
>>>> On Thu, Jan 5, 2017 at 10:32 PM, Anna Ossowski <ossanna16 at gmx.de <mailto:ossanna16 at gmx.de>> wrote:
>>>> Hello everyone and Happy New Year!
>>>> 
>>>> The beginning of the new year means that PyCon is only a little over 4 months away and it?s time to kick off Open Spaces planning.
>>>> 
>>>> First of all I would like to welcome our new Open Spaces co-chair, Trey Hunner, again. Trey, I?m so happy to have you on board :)
>>>> 
>>>> During our weekly call Trey and I brainstormed a few ideas on how to improve the Open Spaces this year. I think we did a pretty great job with the Open Spaces last year, they were successful and everything went smoothly, but there is always room for improvements. I wanted to summarize our ideas here for everyone to read. I also added everything to our Open Spaces Trello board.
>>>> Trey, Hobson, and Brandon, you all should have access to the Trello board.
>>>> Ewa, please let me know if you?d like to be added as well.
>>>> Everyone is of course welcome to add their own ideas to the Trello board.
>>>> 
>>>> Here?s a summary of what Trey and I discussed:
>>>> 
>>>> What worked last year:
>>>> 
>>>> * We should add a section about the Open Spaces to the PyCon website. There was a section last year but it looks like this hasn?t been transferred to this year?s website.
>>>> 
>>>> * We should continue tweeting about the Open Spaces using #pyconopenspace. Taking a picture of the board a few times day and tweeting it out for attendees to see would also be a good idea.
>>>> 
>>>> * We should write another blog post about the Open Spaces and maybe try to have it added to some popular Python newsletters to gain more visibility.
>>>> 
>>>> 
>>>> Ideas/To Discuss:
>>>> 
>>>> * How can we make the Open Spaces board more visible? The board last year was beautiful following the PyCon color scheme but it might have been too easy to walk by/not visible enough. Can we make it more visible by getting the board printed in brighter colors? Other ideas?
>>>> 
>>>> * It might be a good idea to add a small column to the printed hand-out schedule indicating the Open Spaces. Attendees could then go ahead and mark their schedule with an ?X? for the times they are planning on attending an Open Space.
>>>> 
>>>> * Can we add a column about the Open Spaces to Guidebook? This might be useful to make attendees aware of the Open Spaces. We could also add a simple section to Guidebook explaining what Open Spaces are and how to ?sign up?.
>>>> 
>>>> * We could ask the registration desk workers to make people aware of the Open Spaces board when they register. The board is right next to the registration desk.
>>>> 
>>>> * In general it might be useful to write a short script for registration desk workers indicating what information to forward to attendees, specifically things that may not be as obvious like the hallway track, what to do in the evenings, PyLadies auction, Open Spaces, etc. This may not be possible doing busy times but at least when time allows.
>>>> 
>>>> * Can we keep the Open Spaces going during sprints? We could maybe add a column to the sprints board letting people add cards for Open Spaces. Maybe there is an extra room available. If not we could do it ?pick your own location?-style.
>>>> 
>>>> * We could create a short slideshow targeted at people who are attending PyCon for the first time and send it to meetup organizers to be presented at their meetups before PyCon. The slide show could include everything first time attendees may not be aware of like the Open Spaces, PyLadies auction, Education Summit, hallway track, evening activities, etc.
>>>> (Side note: DjangoCon US this year had a 1 hour event for first time DjangoCon attendees which took place the afternoon before the talk part of the conference started. It was very successful and well received by attendees. It was comparable to the introduction to sprints workshop at PyCon. It may be worth considering doing something like this at PyCon as well.)
>>>> 
>>>> I would love to hear your thoughts on all of those ideas and welcome you to share your own ideas as well.
>>>> 
>>>> I look forward to working with all of you again!
>>>> 
>>>> Warm regards,
>>>> 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>
>>>> 
>>>> 
>>>> 
>>>> -- 
>>>> Brandon Rhodes
>>>> PyCon 2016 Conference Chair
>>>> pycon.brandon at gmail.com <mailto:pycon.brandon at gmail.com>
>> 
>> 
>> _______________________________________________
>> 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/20170107/5df9aaa0/attachment-0001.html>

From ossanna16 at gmx.de  Fri Jan  6 20:33:46 2017
From: ossanna16 at gmx.de (Anna Ossowski)
Date: Sat, 7 Jan 2017 02:33:46 +0100
Subject: [Pycon-openspaces] Open Spaces 2017 Kick Off!
In-Reply-To: <CADx+GQM400JLoMbRzvNDMqNYDCQP8-_c8FzgzYgvo-VPY3GRLA@mail.gmail.com>
References: <5CF5E3BC-0F73-43CB-9A5C-4A275867E57B@gmx.de>
 <CADx+GQM400JLoMbRzvNDMqNYDCQP8-_c8FzgzYgvo-VPY3GRLA@mail.gmail.com>
Message-ID: <43917198-829F-44D5-8E88-95F53D1BB78A@gmx.de>


> On Jan 6, 2017, at 3:46 PM, Ewa Jodlowska <ewa at python.org> wrote:
> 
> On Thu, Jan 5, 2017 at 9:32 PM, Anna Ossowski <ossanna16 at gmx.de <mailto:ossanna16 at gmx.de>> wrote:
> 
> [clipped] 
> 
> * We should add a section about the Open Spaces to the PyCon website. There was a section last year but it looks like this hasn?t been transferred to this year?s website.
> 
> The work flow for the website is once something is ready to launch, we add it to the website. This way things do not get overlooked and go "stale". If you would like to let me know what text you want on it, I can add the page for you. After that you will have edit rights so you can change whatever is needed. Attached is last year's text. 

Thank you for clarifying the work flow, Ewa! I think we can just re-use the text from last year and I will update the little bits that need to be updated for this year as soon as it?s up on the website. Does that work?
> 
> * We should continue tweeting about the Open Spaces using #pyconopenspace. Taking a picture of the board a few times day and tweeting it out for attendees to see would also be a good idea.
> 
> * We should write another blog post about the Open Spaces and maybe try to have it added to some popular Python newsletters to gain more visibility.
> 
> 
> Ideas/To Discuss:
> 
> 
> [clipped]  
> 
> * In general it might be useful to write a short script for registration desk workers indicating what information to forward to attendees, specifically things that may not be as obvious like the hallway track, what to do in the evenings, PyLadies auction, Open Spaces, etc. This may not be possible doing busy times but at least when time allows.
> 
> I'm going to chime in on two points and leave the rest to Brandon. 
> 
> Point 1 is regarding info at registration: having the volunteers verbally mention all of these things will hold up the lines, especially the first day of tutorials and the first day of the conference, which are the two days that almost all people check-in. During the mornings there are super long lines with people trying to get checked in in time for their tutorials and/or the opening plenary. I do not want to strain that process further. Here we have two options to consider:

Agreed!
> Have a short handout with bulleted FYIs. Open Spaces can be one of them. This handout can be given to each person that checks in. The downside is that it is just another thing that someone gets at registration. Not sure how effective it will be.
> For those busy check-in times, have a short handout with bulleted FYIs. Open Spaces can be one of them. After the busy times, we can have the people verbally mention it. However, I am not sure how much we retain during that interaction. As an attendee myself (actually going to a conference this following week) I tend to be over stimulated at check-in and don't retain what is verbally said to me. I tend to go back through what was given to me to make sure I did not miss anything.
> Personally, I think adding it to the printed schedule and to the Guidebook is the best way forward. 

Good points! I agree that adding an FYI section to the printed schedule and Guidebook would work best.
> 
> * Can we keep the Open Spaces going during sprints? We could maybe add a column to the sprints board letting people add cards for Open Spaces. Maybe there is an extra room available. If not we could do it ?pick your own location?-style.
> 
> From what I see, this tends to happen naturally. When Sprinters are onsite and they want to meet with a few people to discuss anything, they find their own space and it happens. In Portland we have an unusual amount of space available for Sprints, which will not be the case for 2018 and 2019. We can try it in 2017, but I cannot guarantee that I will have enough space in 2018/19 to give to this.
> 
> For 2017, the D rooms (if you visualize walking to the Portland Ballroom on the lower level, the D rooms were the small rooms on the right) can be used for this effort because in 2016 that section was completely abandoned during Sprints since there was so much space in the Portland Ballrooms. There was no need for people to be so far away from the rest.

I?d say let?s try it and see how people like it. If there?s no interest or we can?t do it again in following years due to limited space, that?s ok. Would it be possible to have the Open Spaces board up for the sprints too then?

Have a good weekend everyone :)
Anna

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pycon-openspaces/attachments/20170107/9c2dbe49/attachment.html>

From hobsonlane at gmail.com  Fri Jan  6 21:21:06 2017
From: hobsonlane at gmail.com (Hobson Lane)
Date: Sat, 07 Jan 2017 02:21:06 +0000
Subject: [Pycon-openspaces] Open Spaces 2017 Kick Off!
In-Reply-To: <43917198-829F-44D5-8E88-95F53D1BB78A@gmx.de>
References: <5CF5E3BC-0F73-43CB-9A5C-4A275867E57B@gmx.de>
 <CADx+GQM400JLoMbRzvNDMqNYDCQP8-_c8FzgzYgvo-VPY3GRLA@mail.gmail.com>
 <43917198-829F-44D5-8E88-95F53D1BB78A@gmx.de>
Message-ID: <CACZ_DoekFgCdG=Qm=sNnfBuD-Z4cb-ugCRGoqpjbz9B2VxU=Jg@mail.gmail.com>

Excellent. That's what I was thinking, Anna. I'll get started.

The main challenge will be to avoid getting tricked by spam tweets with
that hashtag (getting misled like Tai), so at first I'd manually confirm
every tweet before sending, as well as every entry into the schedule before
updating the page. I'll try to have it running by April 1 so we can test it
thoroughly. This will be fun!

On Fri, Jan 6, 2017, 5:33 PM Anna Ossowski <ossanna16 at gmx.de> wrote:

> On Jan 6, 2017, at 3:46 PM, Ewa Jodlowska <ewa at python.org> wrote:
>
> On Thu, Jan 5, 2017 at 9:32 PM, Anna Ossowski <ossanna16 at gmx.de> wrote:
>
> [clipped]
>
>
> * We should add a section about the Open Spaces to the PyCon website.
> There was a section last year but it looks like this hasn?t been
> transferred to this year?s website.
>
>
> The work flow for the website is once something is ready to launch, we add
> it to the website. This way things do not get overlooked and go "stale". If
> you would like to let me know what text you want on it, I can add the page
> for you. After that you will have edit rights so you can change whatever is
> needed. Attached is last year's text.
>
>
> Thank you for clarifying the work flow, Ewa! I think we can just re-use
> the text from last year and I will update the little bits that need to be
> updated for this year as soon as it?s up on the website. Does that work?
>
>
> * We should continue tweeting about the Open Spaces using #pyconopenspace.
> Taking a picture of the board a few times day and tweeting it out for
> attendees to see would also be a good idea.
>
> * We should write another blog post about the Open Spaces and maybe try to
> have it added to some popular Python newsletters to gain more visibility.
>
>
> Ideas/To Discuss:
>
>
> [clipped]
>
>
> * In general it might be useful to write a short script for registration
> desk workers indicating what information to forward to attendees,
> specifically things that may not be as obvious like the hallway track, what
> to do in the evenings, PyLadies auction, Open Spaces, etc. This may not be
> possible doing busy times but at least when time allows.
>
>
> I'm going to chime in on two points and leave the rest to Brandon.
>
> Point 1 is regarding info at registration: having the volunteers verbally
> mention all of these things will hold up the lines, especially the first
> day of tutorials and the first day of the conference, which are the two
> days that almost all people check-in. During the mornings there are super
> long lines with people trying to get checked in in time for their tutorials
> and/or the opening plenary. I do not want to strain that process further.
> Here we have two options to consider:
>
>
> Agreed!
>
>
>    1. Have a short handout with bulleted FYIs. Open Spaces can be one of
>    them. This handout can be given to each person that checks in. The downside
>    is that it is just another thing that someone gets at registration. Not
>    sure how effective it will be.
>    2. For those busy check-in times, have a short handout with bulleted
>    FYIs. Open Spaces can be one of them. After the busy times, we can have the
>    people verbally mention it. However, I am not sure how much we retain
>    during that interaction. As an attendee myself (actually going to a
>    conference this following week) I tend to be over stimulated at check-in
>    and don't retain what is verbally said to me. I tend to go back through
>    what was given to me to make sure I did not miss anything.
>
> Personally, I think adding it to the printed schedule and to the Guidebook
> is the best way forward.
>
>
> Good points! I agree that adding an FYI section to the printed schedule
> and Guidebook would work best.
>
>
> * Can we keep the Open Spaces going during sprints? We could maybe add a
> column to the sprints board letting people add cards for Open Spaces. Maybe
> there is an extra room available. If not we could do it ?pick your own
> location?-style.
>
>
> From what I see, this tends to happen naturally. When Sprinters are onsite
> and they want to meet with a few people to discuss anything, they find
> their own space and it happens. In Portland we have an unusual amount of
> space available for Sprints, which will not be the case for 2018 and 2019.
> We can try it in 2017, but I cannot guarantee that I will have enough space
> in 2018/19 to give to this.
>
> For 2017, the D rooms (if you visualize walking to the Portland Ballroom
> on the lower level, the D rooms were the small rooms on the right) can be
> used for this effort because in 2016 that section was completely abandoned
> during Sprints since there was so much space in the Portland Ballrooms.
> There was no need for people to be so far away from the rest.
>
>
> I?d say let?s try it and see how people like it. If there?s no interest or
> we can?t do it again in following years due to limited space, that?s ok.
> Would it be possible to have the Open Spaces board up for the sprints too
> then?
>
> Have a good weekend everyone :)
> Anna
>
> _______________________________________________
> 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/20170107/e44033a9/attachment-0001.html>

From ossanna16 at gmx.de  Sat Jan  7 16:59:06 2017
From: ossanna16 at gmx.de (Anna Ossowski)
Date: Sat, 7 Jan 2017 22:59:06 +0100
Subject: [Pycon-openspaces] Open Spaces 2017 Kick Off!
In-Reply-To: <CACZ_DoekFgCdG=Qm=sNnfBuD-Z4cb-ugCRGoqpjbz9B2VxU=Jg@mail.gmail.com>
References: <5CF5E3BC-0F73-43CB-9A5C-4A275867E57B@gmx.de>
 <CADx+GQM400JLoMbRzvNDMqNYDCQP8-_c8FzgzYgvo-VPY3GRLA@mail.gmail.com>
 <43917198-829F-44D5-8E88-95F53D1BB78A@gmx.de>
 <CACZ_DoekFgCdG=Qm=sNnfBuD-Z4cb-ugCRGoqpjbz9B2VxU=Jg@mail.gmail.com>
Message-ID: <F2157A2B-64B2-4A05-9A8B-C3C780F5FF31@gmx.de>

Hey Hobson,

I?d love to hear Ewa?s, Brandon?s, and Trey?s thoughts and get the official go from Brandon before you start working on the bot. I hope that is ok :)

April 1 sounds like a great timeline. I can help out with the manual confirmation if you?d like so you can get some breaks.

Thank you again for this excellent idea! I?m really excited!
Anna

---------------------------------
You are appreciated.
You are enough.
You matter.
You are not alone.



> On Jan 7, 2017, at 3:21 AM, Hobson Lane <hobsonlane at gmail.com> wrote:
> 
> Excellent. That's what I was thinking, Anna. I'll get started.
> 
> The main challenge will be to avoid getting tricked by spam tweets with that hashtag (getting misled like Tai), so at first I'd manually confirm every tweet before sending, as well as every entry into the schedule before updating the page. I'll try to have it running by April 1 so we can test it thoroughly. This will be fun!
> 
> 
> On Fri, Jan 6, 2017, 5:33 PM Anna Ossowski <ossanna16 at gmx.de <mailto:ossanna16 at gmx.de>> wrote:
>> On Jan 6, 2017, at 3:46 PM, Ewa Jodlowska <ewa at python.org <mailto:ewa at python.org>> wrote:
>> 
>> On Thu, Jan 5, 2017 at 9:32 PM, Anna Ossowski <ossanna16 at gmx.de <mailto:ossanna16 at gmx.de>> wrote:
>> 
>> [clipped] 
>> 
>> * We should add a section about the Open Spaces to the PyCon website. There was a section last year but it looks like this hasn?t been transferred to this year?s website.
>> 
>> The work flow for the website is once something is ready to launch, we add it to the website. This way things do not get overlooked and go "stale". If you would like to let me know what text you want on it, I can add the page for you. After that you will have edit rights so you can change whatever is needed. Attached is last year's text. 
> 
> Thank you for clarifying the work flow, Ewa! I think we can just re-use the text from last year and I will update the little bits that need to be updated for this year as soon as it?s up on the website. Does that work?
> 
>> 
>> * We should continue tweeting about the Open Spaces using #pyconopenspace. Taking a picture of the board a few times day and tweeting it out for attendees to see would also be a good idea.
>> 
>> * We should write another blog post about the Open Spaces and maybe try to have it added to some popular Python newsletters to gain more visibility.
>> 
>> 
>> Ideas/To Discuss:
>> 
>> 
>> [clipped]  
>> 
>> * In general it might be useful to write a short script for registration desk workers indicating what information to forward to attendees, specifically things that may not be as obvious like the hallway track, what to do in the evenings, PyLadies auction, Open Spaces, etc. This may not be possible doing busy times but at least when time allows.
>> 
>> I'm going to chime in on two points and leave the rest to Brandon. 
>> 
>> Point 1 is regarding info at registration: having the volunteers verbally mention all of these things will hold up the lines, especially the first day of tutorials and the first day of the conference, which are the two days that almost all people check-in. During the mornings there are super long lines with people trying to get checked in in time for their tutorials and/or the opening plenary. I do not want to strain that process further. Here we have two options to consider:
> 
> Agreed!
> 
>> Have a short handout with bulleted FYIs. Open Spaces can be one of them. This handout can be given to each person that checks in. The downside is that it is just another thing that someone gets at registration. Not sure how effective it will be.
>> For those busy check-in times, have a short handout with bulleted FYIs. Open Spaces can be one of them. After the busy times, we can have the people verbally mention it. However, I am not sure how much we retain during that interaction. As an attendee myself (actually going to a conference this following week) I tend to be over stimulated at check-in and don't retain what is verbally said to me. I tend to go back through what was given to me to make sure I did not miss anything.
>> Personally, I think adding it to the printed schedule and to the Guidebook is the best way forward. 
> 
> Good points! I agree that adding an FYI section to the printed schedule and Guidebook would work best.
> 
>> 
>> * Can we keep the Open Spaces going during sprints? We could maybe add a column to the sprints board letting people add cards for Open Spaces. Maybe there is an extra room available. If not we could do it ?pick your own location?-style.
>> 
>> From what I see, this tends to happen naturally. When Sprinters are onsite and they want to meet with a few people to discuss anything, they find their own space and it happens. In Portland we have an unusual amount of space available for Sprints, which will not be the case for 2018 and 2019. We can try it in 2017, but I cannot guarantee that I will have enough space in 2018/19 to give to this.
>> 
>> For 2017, the D rooms (if you visualize walking to the Portland Ballroom on the lower level, the D rooms were the small rooms on the right) can be used for this effort because in 2016 that section was completely abandoned during Sprints since there was so much space in the Portland Ballrooms. There was no need for people to be so far away from the rest.
> 
> I?d say let?s try it and see how people like it. If there?s no interest or we can?t do it again in following years due to limited space, that?s ok. Would it be possible to have the Open Spaces board up for the sprints too then?
> 
> Have a good weekend everyone :)
> Anna
> 
> _______________________________________________
> 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/20170107/cc6b3772/attachment.html>

From trey at truthful.technology  Sat Jan  7 18:57:54 2017
From: trey at truthful.technology (Trey Hunner)
Date: Sat, 07 Jan 2017 23:57:54 +0000
Subject: [Pycon-openspaces] Open Spaces 2017 Kick Off!
In-Reply-To: <43917198-829F-44D5-8E88-95F53D1BB78A@gmx.de>
References: <5CF5E3BC-0F73-43CB-9A5C-4A275867E57B@gmx.de>
 <CADx+GQM400JLoMbRzvNDMqNYDCQP8-_c8FzgzYgvo-VPY3GRLA@mail.gmail.com>
 <43917198-829F-44D5-8E88-95F53D1BB78A@gmx.de>
Message-ID: <1e6065we301jubp7zows9t244-0@mailer.nylas.com>

Hi all!

  

Thanks for the welcome Brandon. Nice to meet you Hobson. Ewa, I just requested
to join the pycon-staff list. Thanks for the reminder!

  

I replied inline below.

  

On Jan 6 2017, at 5:33 pm, Anna Ossowski <ossanna16 at gmx.de> wrote:  

>  

>

>> On Jan 6, 2017, at 3:46 PM, Ewa Jodlowska
<[ewa at python.org](mailto:ewa at python.org)> wrote:

>>

>>  

>>

>> On Thu, Jan 5, 2017 at 9:32 PM, Anna Ossowski
<[ossanna16 at gmx.de](mailto:ossanna16 at gmx.de)> wrote:  

>>

>>  

>>

>> [clipped]

>>

>>>  
* We should add a section about the Open Spaces to the PyCon website. There was a section last year but it looks like this hasn?t been transferred to this year?s website.  

>>

>>  

>>

>> The work flow for the website is once something is ready to launch, we add
it to the website. This way things do not get overlooked and go "stale". If
you would like to let me know what text you want on it, I can add the page for
you. After that you will have edit rights so you can change whatever is
needed. Attached is last year's text.

>

>  

>

> Thank you for clarifying the work flow, Ewa! I think we can just re-use the
text from last year and I will update the little bits that need to be updated
for this year as soon as it?s up on the website. Does that work?

  

Two ideas I had that differ from what we had last year:

  

  * I wonder whether we should list an empty schedule-like thing on the open spaces page that lists room numbers and time slots... something that explains/conveys the fact that there is a schedule but we make it ourselves. Open Source Bridge does something like this for their "Birds of a Feather" day on the last day of their conference schedule on their website.
  * Should we move the Open Spaces page from Events to Schedule? I see open spaces as parallel to the main talk schedule and I missed them entirely my first year at PyCon because I thought they were one-off after hour events like the auction, dinners, 5k run, etc.
  

  

> > > * We should continue tweeting about the Open Spaces using
#pyconopenspace. Taking a picture of the board a few times day and tweeting it
out for attendees to see would also be a good idea.  
  
* We should write another blog post about the Open Spaces and maybe try to have it added to some popular Python newsletters to gain more visibility.  
  
  
Ideas/To Discuss:  
  
  

>>

>> [clipped]  
>>

>>>  
* In general it might be useful to write a short script for registration desk workers indicating what information to forward to attendees, specifically things that may not be as obvious like the hallway track, what to do in the evenings, PyLadies auction, Open Spaces, etc. This may not be possible doing busy times but at least when time allows.  

>>

>>  

>>

>> I'm going to chime in on two points and leave the rest to Brandon.

>>

>>  

>>

>> Point 1 is regarding info at registration: having the volunteers verbally
mention all of these things will hold up the lines, especially the first day
of tutorials and the first day of the conference, which are the two days that
almost all people check-in. During the mornings there are super long lines
with people trying to get checked in in time for their tutorials and/or the
opening plenary. I do not want to strain that process further. Here we have
two options to consider:  

>

>  

>

> Agreed!  

>

>>   1. Have a short handout with bulleted FYIs. Open Spaces can be one of
them. This handout can be given to each person that checks in. The downside is
that it is just another thing that someone gets at registration. Not sure how
effective it will be.  

>>   2. For those busy check-in times, have a short handout with bulleted
FYIs. Open Spaces can be one of them. After the busy times, we can have the
people verbally mention it. However, I am not sure how much we retain during
that interaction. As an attendee myself (actually going to a conference this
following week) I tend to be over stimulated at check-in and don't retain what
is verbally said to me. I tend to go back through what was given to me to make
sure I did not miss anything.

>>

>> Personally, I think adding it to the printed schedule and to the Guidebook
is the best way forward.

>

>  

>

> Good points! I agree that adding an FYI section to the printed schedule and
Guidebook would work best.

  

Yes keeping folks at the reg desk informed is great, but I also agree that
most folks are going to get through registration quickly and benefit most from
an informational section in the printed schedule. A one-page "PyCon
cheatsheet" aimed at first time or newer PyCon attendees could be helpful. Or
maybe a very small grid representation of the empty open space board on the
schedule print out (if it fits)?  
  
  
  

> > > * Can we keep the Open Spaces going during sprints? We could maybe add a
column to the sprints board letting people add cards for Open Spaces. Maybe
there is an extra room available. If not we could do it ?pick your own
location?-style.  

>>

>>  

>>

>> From what I see, this tends to happen naturally. When Sprinters are onsite
and they want to meet with a few people to discuss anything, they find their
own space and it happens. In Portland we have an unusual amount of space
available for Sprints, which will not be the case for 2018 and 2019. We can
try it in 2017, but I cannot guarantee that I will have enough space in
2018/19 to give to this.

>>

>>  

>>

>> For 2017, the D rooms (if you visualize walking to the Portland Ballroom on
the lower level, the D rooms were the small rooms on the right) can be used
for this effort because in 2016 that section was completely abandoned during
Sprints since there was so much space in the Portland Ballrooms. There was no
need for people to be so far away from the rest.

>

>  

>

> I?d say let?s try it and see how people like it. If there?s no interest or
we can?t do it again in following years due to limited space, that?s ok. Would
it be possible to have the Open Spaces board up for the sprints too then?

  

Yeah. Maybe this is a conversation maybe we could coordinate with the sprint
board coordinators?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pycon-openspaces/attachments/20170107/386e42ca/attachment-0001.html>

From hobsonlane at gmail.com  Sat Jan  7 19:10:31 2017
From: hobsonlane at gmail.com (Hobson Lane)
Date: Sun, 08 Jan 2017 00:10:31 +0000
Subject: [Pycon-openspaces] Open Spaces 2017 Kick Off!
In-Reply-To: <1e6065we301jubp7zows9t244-0@mailer.nylas.com>
References: <5CF5E3BC-0F73-43CB-9A5C-4A275867E57B@gmx.de>
 <CADx+GQM400JLoMbRzvNDMqNYDCQP8-_c8FzgzYgvo-VPY3GRLA@mail.gmail.com>
 <43917198-829F-44D5-8E88-95F53D1BB78A@gmx.de>
 <1e6065we301jubp7zows9t244-0@mailer.nylas.com>
Message-ID: <CACZ_DocmSNcMf8ouDcYQ2iKYOv5Dw2TC8xGKZRmzcQNkC8VKnA@mail.gmail.com>

Good point, Anna. I'll focus on a similar bot for another application for
now. I can definitely use your help curating tweets. Thank you! If we do go
ahead with it, you'll have direct control over the tweets: to turn them
off, require approval/editting by you, or me, or both, and/or anyone else
you designate.

On Sat, Jan 7, 2017, 3:58 PM Trey Hunner <trey at truthful.technology> wrote:

> Hi all!
>
> Thanks for the welcome Brandon. Nice to meet you Hobson. Ewa, I just
> requested to join the pycon-staff list. Thanks for the reminder!
>
> I replied inline below.
>
> On Jan 6 2017, at 5:33 pm, Anna Ossowski <ossanna16 at gmx.de> wrote:
>
>
> On Jan 6, 2017, at 3:46 PM, Ewa Jodlowska <ewa at python.org> wrote:
>
> On Thu, Jan 5, 2017 at 9:32 PM, Anna Ossowski <ossanna16 at gmx.de> wrote:
>
> [clipped]
>
>
> * We should add a section about the Open Spaces to the PyCon website.
> There was a section last year but it looks like this hasn?t been
> transferred to this year?s website.
>
>
> The work flow for the website is once something is ready to launch, we add
> it to the website. This way things do not get overlooked and go "stale". If
> you would like to let me know what text you want on it, I can add the page
> for you. After that you will have edit rights so you can change whatever is
> needed. Attached is last year's text.
>
>
> Thank you for clarifying the work flow, Ewa! I think we can just re-use
> the text from last year and I will update the little bits that need to be
> updated for this year as soon as it?s up on the website. Does that work?
>
>
> Two ideas I had that differ from what we had last year:
>
>
>    - I wonder whether we should list an empty schedule-like thing on the
>    open spaces page that lists room numbers and time slots... something that
>    explains/conveys the fact that there is a schedule but we make it
>    ourselves. Open Source Bridge does something like this for their "Birds of
>    a Feather" day on the last day of their conference schedule on their
>    website.
>    - Should we move the Open Spaces page from Events to Schedule? I see
>    open spaces as parallel to the main talk schedule and I missed them
>    entirely my first year at PyCon because I thought they were one-off after
>    hour events like the auction, dinners, 5k run, etc.
>
>
>
> * We should continue tweeting about the Open Spaces using #pyconopenspace.
> Taking a picture of the board a few times day and tweeting it out for
> attendees to see would also be a good idea.
>
> * We should write another blog post about the Open Spaces and maybe try to
> have it added to some popular Python newsletters to gain more visibility.
>
>
> Ideas/To Discuss:
>
>
> [clipped]
>
>
> * In general it might be useful to write a short script for registration
> desk workers indicating what information to forward to attendees,
> specifically things that may not be as obvious like the hallway track, what
> to do in the evenings, PyLadies auction, Open Spaces, etc. This may not be
> possible doing busy times but at least when time allows.
>
>
> I'm going to chime in on two points and leave the rest to Brandon.
>
> Point 1 is regarding info at registration: having the volunteers verbally
> mention all of these things will hold up the lines, especially the first
> day of tutorials and the first day of the conference, which are the two
> days that almost all people check-in. During the mornings there are super
> long lines with people trying to get checked in in time for their tutorials
> and/or the opening plenary. I do not want to strain that process further.
> Here we have two options to consider:
>
>
> Agreed!
>
>
>    1. Have a short handout with bulleted FYIs. Open Spaces can be one of
>    them. This handout can be given to each person that checks in. The downside
>    is that it is just another thing that someone gets at registration. Not
>    sure how effective it will be.
>    2. For those busy check-in times, have a short handout with bulleted
>    FYIs. Open Spaces can be one of them. After the busy times, we can have the
>    people verbally mention it. However, I am not sure how much we retain
>    during that interaction. As an attendee myself (actually going to a
>    conference this following week) I tend to be over stimulated at check-in
>    and don't retain what is verbally said to me. I tend to go back through
>    what was given to me to make sure I did not miss anything.
>
> Personally, I think adding it to the printed schedule and to the Guidebook
> is the best way forward.
>
>
> Good points! I agree that adding an FYI section to the printed schedule
> and Guidebook would work best.
>
>
> Yes keeping folks at the reg desk informed is great, but I also agree that
> most folks are going to get through registration quickly and benefit most
> from an informational section in the printed schedule. A one-page "PyCon
> cheatsheet" aimed at first time or newer PyCon attendees could be helpful.
> Or maybe a very small grid representation of the empty open space board on
> the schedule print out (if it fits)?
>
>
>
>
> * Can we keep the Open Spaces going during sprints? We could maybe add a
> column to the sprints board letting people add cards for Open Spaces. Maybe
> there is an extra room available. If not we could do it ?pick your own
> location?-style.
>
>
> From what I see, this tends to happen naturally. When Sprinters are onsite
> and they want to meet with a few people to discuss anything, they find
> their own space and it happens. In Portland we have an unusual amount of
> space available for Sprints, which will not be the case for 2018 and 2019.
> We can try it in 2017, but I cannot guarantee that I will have enough space
> in 2018/19 to give to this.
>
> For 2017, the D rooms (if you visualize walking to the Portland Ballroom
> on the lower level, the D rooms were the small rooms on the right) can be
> used for this effort because in 2016 that section was completely abandoned
> during Sprints since there was so much space in the Portland Ballrooms.
> There was no need for people to be so far away from the rest.
>
>
> I?d say let?s try it and see how people like it. If there?s no interest or
> we can?t do it again in following years due to limited space, that?s ok.
> Would it be possible to have the Open Spaces board up for the sprints too
> then?
>
>
> Yeah. Maybe this is a conversation maybe we could coordinate with the
> sprint board coordinators?
> _______________________________________________
> 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/20170108/b66da9c0/attachment.html>

From trey at truthful.technology  Sat Jan  7 20:43:28 2017
From: trey at truthful.technology (Trey Hunner)
Date: Sun, 08 Jan 2017 01:43:28 +0000
Subject: [Pycon-openspaces] Open Spaces 2017 Kick Off!
In-Reply-To: <CACZ_DoekFgCdG=Qm=sNnfBuD-Z4cb-ugCRGoqpjbz9B2VxU=Jg@mail.gmail.com>
References: <5CF5E3BC-0F73-43CB-9A5C-4A275867E57B@gmx.de>
 <CADx+GQM400JLoMbRzvNDMqNYDCQP8-_c8FzgzYgvo-VPY3GRLA@mail.gmail.com>
 <43917198-829F-44D5-8E88-95F53D1BB78A@gmx.de>
 <CACZ_DoekFgCdG=Qm=sNnfBuD-Z4cb-ugCRGoqpjbz9B2VxU=Jg@mail.gmail.com>
Message-ID: <dyg8174rjfz3iu8kus48e2f4g-0@mailer.nylas.com>

On Jan 6 2017, at 6:21 pm, Hobson Lane <hobsonlane at gmail.com> wrote:  

> Excellent. That's what I was thinking, Anna. I'll get started.

>

> The main challenge will be to avoid getting tricked by spam tweets with that
hashtag (getting misled like Tai), so at first I'd manually confirm every
tweet before sending, as well as every entry into the schedule before updating
the page. I'll try to have it running by April 1 so we can test it thoroughly.
This will be fun!

  

Hey Hobson!

  

That Twitter bot sounds like it might be more engineering than necessary, but
I'm not opposed to that.

  

That does sound like it could be helpful for semi-automating our process. I
just wouldn't want you to spend a lot of time on it unless you find that work
personally fulfilling.

  

If you do end up making it, I'd prefer to err on the side of semi-automation
rather than full automation just to play it safe and not accidentally
retweet/promote things we'd prefer not to.

  

\--  

Trey Hunner

Python and Django trainer  

[http://truthful.technology](http://truthful.technology/)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pycon-openspaces/attachments/20170108/4fba1c04/attachment-0001.html>

From hobsonlane at gmail.com  Sat Jan  7 23:28:04 2017
From: hobsonlane at gmail.com (Hobson Lane)
Date: Sun, 08 Jan 2017 04:28:04 +0000
Subject: [Pycon-openspaces] Open Spaces 2017 Kick Off!
In-Reply-To: <dyg8174rjfz3iu8kus48e2f4g-0@mailer.nylas.com>
References: <5CF5E3BC-0F73-43CB-9A5C-4A275867E57B@gmx.de>
 <CADx+GQM400JLoMbRzvNDMqNYDCQP8-_c8FzgzYgvo-VPY3GRLA@mail.gmail.com>
 <43917198-829F-44D5-8E88-95F53D1BB78A@gmx.de>
 <CACZ_DoekFgCdG=Qm=sNnfBuD-Z4cb-ugCRGoqpjbz9B2VxU=Jg@mail.gmail.com>
 <dyg8174rjfz3iu8kus48e2f4g-0@mailer.nylas.com>
Message-ID: <CACZ_DocC9SW-1ma7T=SE0gfU8_0z10rx8=G4nq4EvAevn=DsKQ@mail.gmail.com>

Totally. We think alike. Building chatbots is what gets me excited on the
weekends, so definitely not too much hassel.

On Sat, Jan 7, 2017, 5:43 PM Trey Hunner <trey at truthful.technology> wrote:

> On Jan 6 2017, at 6:21 pm, Hobson Lane <hobsonlane at gmail.com> wrote:
>
> Excellent. That's what I was thinking, Anna. I'll get started.
>
> The main challenge will be to avoid getting tricked by spam tweets with
> that hashtag (getting misled like Tai), so at first I'd manually confirm
> every tweet before sending, as well as every entry into the schedule before
> updating the page. I'll try to have it running by April 1 so we can test it
> thoroughly. This will be fun!
>
>
> Hey Hobson!
>
> That Twitter bot sounds like it might be more engineering than necessary,
> but I'm not opposed to that.
>
> That does sound like it could be helpful for semi-automating our process.
> I just wouldn't want you to spend a lot of time on it unless you find that
> work personally fulfilling.
>
> If you do end up making it, I'd prefer to err on the side of
> semi-automation rather than full automation just to play it safe and not
> accidentally retweet/promote things we'd prefer not to.
>
> --
> Trey Hunner
> Python and Django trainer
> http://truthful.technology
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pycon-openspaces/attachments/20170108/205991e6/attachment.html>

From ewa at python.org  Mon Jan  9 10:30:43 2017
From: ewa at python.org (Ewa Jodlowska)
Date: Mon, 9 Jan 2017 09:30:43 -0600
Subject: [Pycon-openspaces] Open Spaces 2017 Kick Off!
In-Reply-To: <43917198-829F-44D5-8E88-95F53D1BB78A@gmx.de>
References: <5CF5E3BC-0F73-43CB-9A5C-4A275867E57B@gmx.de>
 <CADx+GQM400JLoMbRzvNDMqNYDCQP8-_c8FzgzYgvo-VPY3GRLA@mail.gmail.com>
 <43917198-829F-44D5-8E88-95F53D1BB78A@gmx.de>
Message-ID: <CADx+GQPizVDR3+Gaz5--pO+VnXi2KA8upve3bfZRbjJt014cbQ@mail.gmail.com>

On Fri, Jan 6, 2017 at 7:33 PM, Anna Ossowski <ossanna16 at gmx.de> wrote:

>
> On Jan 6, 2017, at 3:46 PM, Ewa Jodlowska <ewa at python.org> wrote:
>
> On Thu, Jan 5, 2017 at 9:32 PM, Anna Ossowski <ossanna16 at gmx.de> wrote:
>
> [clipped]
>
>>
>> * We should add a section about the Open Spaces to the PyCon website.
>> There was a section last year but it looks like this hasn?t been
>> transferred to this year?s website.
>>
>
> The work flow for the website is once something is ready to launch, we add
> it to the website. This way things do not get overlooked and go "stale". If
> you would like to let me know what text you want on it, I can add the page
> for you. After that you will have edit rights so you can change whatever is
> needed. Attached is last year's text.
>
>
> Thank you for clarifying the work flow, Ewa! I think we can just re-use
> the text from last year and I will update the little bits that need to be
> updated for this year as soon as it?s up on the website. Does that work?
>

I have added the text from 2016, but just edited the dates and removed the
open spaces listed from 2016: https://us.pycon.org/2017/events/open-spaces/.
It may take a few minutes for it to appear in the nav.

[clipped]

>
> I?d say let?s try it and see how people like it. If there?s no interest or
> we can?t do it again in following years due to limited space, that?s ok.
> Would it be possible to have the Open Spaces board up for the sprints too
> then?
>

Yes, we can keep the board for Monday-Thursday.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pycon-openspaces/attachments/20170109/9f572150/attachment.html>

From ossanna16 at gmx.de  Mon Jan  9 18:53:46 2017
From: ossanna16 at gmx.de (Anna Ossowski)
Date: Tue, 10 Jan 2017 00:53:46 +0100
Subject: [Pycon-openspaces] Open Spaces 2017 Kick Off!
In-Reply-To: <CADx+GQPizVDR3+Gaz5--pO+VnXi2KA8upve3bfZRbjJt014cbQ@mail.gmail.com>
References: <5CF5E3BC-0F73-43CB-9A5C-4A275867E57B@gmx.de>
 <CADx+GQM400JLoMbRzvNDMqNYDCQP8-_c8FzgzYgvo-VPY3GRLA@mail.gmail.com>
 <43917198-829F-44D5-8E88-95F53D1BB78A@gmx.de>
 <CADx+GQPizVDR3+Gaz5--pO+VnXi2KA8upve3bfZRbjJt014cbQ@mail.gmail.com>
Message-ID: <63EB39A8-117D-45DB-9264-772281EDADBC@gmx.de>

Thank you, Ewa!

---------------------------------
You are appreciated.
You are enough.
You matter.
You are not alone.



> On Jan 9, 2017, at 4:30 PM, Ewa Jodlowska <ewa at python.org> wrote:
> 
> 
> 
> On Fri, Jan 6, 2017 at 7:33 PM, Anna Ossowski <ossanna16 at gmx.de <mailto:ossanna16 at gmx.de>> wrote:
> 
>> On Jan 6, 2017, at 3:46 PM, Ewa Jodlowska <ewa at python.org <mailto:ewa at python.org>> wrote:
>> 
>> On Thu, Jan 5, 2017 at 9:32 PM, Anna Ossowski <ossanna16 at gmx.de <mailto:ossanna16 at gmx.de>> wrote:
>> 
>> [clipped] 
>> 
>> * We should add a section about the Open Spaces to the PyCon website. There was a section last year but it looks like this hasn?t been transferred to this year?s website.
>> 
>> The work flow for the website is once something is ready to launch, we add it to the website. This way things do not get overlooked and go "stale". If you would like to let me know what text you want on it, I can add the page for you. After that you will have edit rights so you can change whatever is needed. Attached is last year's text. 
> 
> Thank you for clarifying the work flow, Ewa! I think we can just re-use the text from last year and I will update the little bits that need to be updated for this year as soon as it?s up on the website. Does that work?
> 
> I have added the text from 2016, but just edited the dates and removed the open spaces listed from 2016: https://us.pycon.org/2017/events/open-spaces/ <https://us.pycon.org/2017/events/open-spaces/>. It may take a few minutes for it to appear in the nav. 
> 
> [clipped]
> 
> I?d say let?s try it and see how people like it. If there?s no interest or we can?t do it again in following years due to limited space, that?s ok. Would it be possible to have the Open Spaces board up for the sprints too then?
> 
> Yes, we can keep the board for Monday-Thursday. 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pycon-openspaces/attachments/20170110/0882fb2a/attachment.html>

From ossanna16 at gmx.de  Mon Jan  9 18:57:26 2017
From: ossanna16 at gmx.de (Anna Ossowski)
Date: Tue, 10 Jan 2017 00:57:26 +0100
Subject: [Pycon-openspaces] Open Spaces 2017 Kick Off!
In-Reply-To: <dyg8174rjfz3iu8kus48e2f4g-0@mailer.nylas.com>
References: <5CF5E3BC-0F73-43CB-9A5C-4A275867E57B@gmx.de>
 <CADx+GQM400JLoMbRzvNDMqNYDCQP8-_c8FzgzYgvo-VPY3GRLA@mail.gmail.com>
 <43917198-829F-44D5-8E88-95F53D1BB78A@gmx.de>
 <CACZ_DoekFgCdG=Qm=sNnfBuD-Z4cb-ugCRGoqpjbz9B2VxU=Jg@mail.gmail.com>
 <dyg8174rjfz3iu8kus48e2f4g-0@mailer.nylas.com>
Message-ID: <3EADA661-8237-4C4B-B438-6C12E05B1F0F@gmx.de>


Hey Trey and Hobson!

My one concern about the bot is how much time we?ll spend approving tweets etc. during the conference. We are Open Spaces chairs but we are also attendees and I wouldn?t want us to worry about being on our laptops and ?feeding? the bot the whole time. What are your thoughts on this?

Thank you!
Anna


> On Jan 8, 2017, at 2:43 AM, Trey Hunner <trey at truthful.technology> wrote:
> 
> On Jan 6 2017, at 6:21 pm, Hobson Lane <hobsonlane at gmail.com> wrote: 
> Excellent. That's what I was thinking, Anna. I'll get started.
> 
> The main challenge will be to avoid getting tricked by spam tweets with that hashtag (getting misled like Tai), so at first I'd manually confirm every tweet before sending, as well as every entry into the schedule before updating the page. I'll try to have it running by April 1 so we can test it thoroughly. This will be fun!
> 
> 
> Hey Hobson!
> 
> That Twitter bot sounds like it might be more engineering than necessary, but I'm not opposed to that.
> 
> That does sound like it could be helpful for semi-automating our process. I just wouldn't want you to spend a lot of time on it unless you find that work personally fulfilling.
> 
> If you do end up making it, I'd prefer to err on the side of semi-automation rather than full automation just to play it safe and not accidentally retweet/promote things we'd prefer not to.
> 
> -- 
> Trey Hunner
> Python and Django trainer
> http://truthful.technology <http://truthful.technology/>

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

From ossanna16 at gmx.de  Mon Jan  9 19:15:23 2017
From: ossanna16 at gmx.de (Anna Ossowski)
Date: Tue, 10 Jan 2017 01:15:23 +0100
Subject: [Pycon-openspaces] Open Spaces 2017 Kick Off!
In-Reply-To: <1e6065we301jubp7zows9t244-0@mailer.nylas.com>
References: <5CF5E3BC-0F73-43CB-9A5C-4A275867E57B@gmx.de>
 <CADx+GQM400JLoMbRzvNDMqNYDCQP8-_c8FzgzYgvo-VPY3GRLA@mail.gmail.com>
 <43917198-829F-44D5-8E88-95F53D1BB78A@gmx.de>
 <1e6065we301jubp7zows9t244-0@mailer.nylas.com>
Message-ID: <B259B330-A111-409C-B418-71D38D705683@gmx.de>


I support Trey?s idea of making more prominent on the website that the Open Spaces are an event that takes place parallel to the talks and isn?t an evening event like the PyLadies auction and the PyCon dinners for example.
Adding a grid to the Open Spaces page, as well as moving the Open Spaces page from the Events to the Schedule tab, are both great ideas.

Ewa and Brandon, I would love to hear your thoughts.

Thank you!
Anna


> On Jan 8, 2017, at 12:57 AM, Trey Hunner <trey at truthful.technology> wrote:
> 
> Hi all!
> 
> Thanks for the welcome Brandon. Nice to meet you Hobson. Ewa, I just requested to join the pycon-staff list. Thanks for the reminder!
> 
> I replied inline below.
> 
> On Jan 6 2017, at 5:33 pm, Anna Ossowski <ossanna16 at gmx.de> wrote: 
> 
>> On Jan 6, 2017, at 3:46 PM, Ewa Jodlowska <ewa at python.org <mailto:ewa at python.org>> wrote:
>> 
>> On Thu, Jan 5, 2017 at 9:32 PM, Anna Ossowski <ossanna16 at gmx.de <mailto:ossanna16 at gmx.de>> wrote:
>> 
>> [clipped] 
>> 
>> * We should add a section about the Open Spaces to the PyCon website. There was a section last year but it looks like this hasn?t been transferred to this year?s website.
>> 
>> The work flow for the website is once something is ready to launch, we add it to the website. This way things do not get overlooked and go "stale". If you would like to let me know what text you want on it, I can add the page for you. After that you will have edit rights so you can change whatever is needed. Attached is last year's text. 
> 
> Thank you for clarifying the work flow, Ewa! I think we can just re-use the text from last year and I will update the little bits that need to be updated for this year as soon as it?s up on the website. Does that work?
> 
> Two ideas I had that differ from what we had last year:
> 
> I wonder whether we should list an empty schedule-like thing on the open spaces page that lists room numbers and time slots... something that explains/conveys the fact that there is a schedule but we make it ourselves. Open Source Bridge does something like this for their "Birds of a Feather" day on the last day of their conference schedule on their website.
> Should we move the Open Spaces page from Events to Schedule? I see open spaces as parallel to the main talk schedule and I missed them entirely my first year at PyCon because I thought they were one-off after hour events like the auction, dinners, 5k run, etc.
> 
> 
>> * We should continue tweeting about the Open Spaces using #pyconopenspace. Taking a picture of the board a few times day and tweeting it out for attendees to see would also be a good idea.
>> 
>> * We should write another blog post about the Open Spaces and maybe try to have it added to some popular Python newsletters to gain more visibility.
>> 
>> 
>> Ideas/To Discuss:
>> 
>> 
>> [clipped]  
>> 
>> * In general it might be useful to write a short script for registration desk workers indicating what information to forward to attendees, specifically things that may not be as obvious like the hallway track, what to do in the evenings, PyLadies auction, Open Spaces, etc. This may not be possible doing busy times but at least when time allows.
>> 
>> I'm going to chime in on two points and leave the rest to Brandon. 
>> 
>> Point 1 is regarding info at registration: having the volunteers verbally mention all of these things will hold up the lines, especially the first day of tutorials and the first day of the conference, which are the two days that almost all people check-in. During the mornings there are super long lines with people trying to get checked in in time for their tutorials and/or the opening plenary. I do not want to strain that process further. Here we have two options to consider:
> 
> Agreed!
>> Have a short handout with bulleted FYIs. Open Spaces can be one of them. This handout can be given to each person that checks in. The downside is that it is just another thing that someone gets at registration. Not sure how effective it will be.
>> For those busy check-in times, have a short handout with bulleted FYIs. Open Spaces can be one of them. After the busy times, we can have the people verbally mention it. However, I am not sure how much we retain during that interaction. As an attendee myself (actually going to a conference this following week) I tend to be over stimulated at check-in and don't retain what is verbally said to me. I tend to go back through what was given to me to make sure I did not miss anything.
>> Personally, I think adding it to the printed schedule and to the Guidebook is the best way forward. 
> 
> Good points! I agree that adding an FYI section to the printed schedule and Guidebook would work best.
> 
> Yes keeping folks at the reg desk informed is great, but I also agree that most folks are going to get through registration quickly and benefit most from an informational section in the printed schedule. A one-page "PyCon cheatsheet" aimed at first time or newer PyCon attendees could be helpful. Or maybe a very small grid representation of the empty open space board on the schedule print out (if it fits)?
> 
> 
> 
>> * Can we keep the Open Spaces going during sprints? We could maybe add a column to the sprints board letting people add cards for Open Spaces. Maybe there is an extra room available. If not we could do it ?pick your own location?-style.
>> 
>> From what I see, this tends to happen naturally. When Sprinters are onsite and they want to meet with a few people to discuss anything, they find their own space and it happens. In Portland we have an unusual amount of space available for Sprints, which will not be the case for 2018 and 2019. We can try it in 2017, but I cannot guarantee that I will have enough space in 2018/19 to give to this.
>> 
>> For 2017, the D rooms (if you visualize walking to the Portland Ballroom on the lower level, the D rooms were the small rooms on the right) can be used for this effort because in 2016 that section was completely abandoned during Sprints since there was so much space in the Portland Ballrooms. There was no need for people to be so far away from the rest.
> 
> I?d say let?s try it and see how people like it. If there?s no interest or we can?t do it again in following years due to limited space, that?s ok. Would it be possible to have the Open Spaces board up for the sprints too then?
> 
> Yeah. Maybe this is a conversation maybe we could coordinate with the sprint board coordinators?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pycon-openspaces/attachments/20170110/5030d4fc/attachment-0001.html>

From ewa at python.org  Tue Jan 10 10:36:20 2017
From: ewa at python.org (Ewa Jodlowska)
Date: Tue, 10 Jan 2017 09:36:20 -0600
Subject: [Pycon-openspaces] Open Spaces 2017 Kick Off!
In-Reply-To: <B259B330-A111-409C-B418-71D38D705683@gmx.de>
References: <5CF5E3BC-0F73-43CB-9A5C-4A275867E57B@gmx.de>
 <CADx+GQM400JLoMbRzvNDMqNYDCQP8-_c8FzgzYgvo-VPY3GRLA@mail.gmail.com>
 <43917198-829F-44D5-8E88-95F53D1BB78A@gmx.de>
 <1e6065we301jubp7zows9t244-0@mailer.nylas.com>
 <B259B330-A111-409C-B418-71D38D705683@gmx.de>
Message-ID: <CADx+GQO8d=HfWgUg57ErTLJL4tD_0y-VbyZQSo-8BU43fYu1pw@mail.gmail.com>

I agree with Anna about the bot. I don't want you all to take on a work
load that will make you uncomfortable onsite.

On Mon, Jan 9, 2017 at 6:15 PM, Anna Ossowski <ossanna16 at gmx.de> wrote:

>
> I support Trey?s idea of making more prominent on the website that the
> Open Spaces are an event that takes place parallel to the talks and isn?t
> an evening event like the PyLadies auction and the PyCon dinners for
> example.
> Adding a grid to the Open Spaces page, as well as moving the Open Spaces
> page from the Events to the Schedule tab, are both great ideas.
>

I think this makes perfect sense and I can help with that. Once you have a
grid up and it looks like a schedule, I can definitely move it over to the
Schedule tab.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pycon-openspaces/attachments/20170110/fd828892/attachment.html>

From ossanna16 at gmx.de  Tue Jan 10 11:17:55 2017
From: ossanna16 at gmx.de (Anna Ossowski)
Date: Tue, 10 Jan 2017 17:17:55 +0100
Subject: [Pycon-openspaces] Open Spaces 2017 Kick Off!
In-Reply-To: <CADx+GQO8d=HfWgUg57ErTLJL4tD_0y-VbyZQSo-8BU43fYu1pw@mail.gmail.com>
References: <5CF5E3BC-0F73-43CB-9A5C-4A275867E57B@gmx.de>
 <CADx+GQM400JLoMbRzvNDMqNYDCQP8-_c8FzgzYgvo-VPY3GRLA@mail.gmail.com>
 <43917198-829F-44D5-8E88-95F53D1BB78A@gmx.de>
 <1e6065we301jubp7zows9t244-0@mailer.nylas.com>
 <B259B330-A111-409C-B418-71D38D705683@gmx.de>
 <CADx+GQO8d=HfWgUg57ErTLJL4tD_0y-VbyZQSo-8BU43fYu1pw@mail.gmail.com>
Message-ID: <8A6A5087-527E-443A-8D5F-E928E0EB1C45@gmx.de>

Maybe there is a way to automate this as much as possible and keep monitoring of the bot at a minimum but still make sure we don?t get a bunch of spammy or CoC violating tweets. Would love to hear Hobson?s and Trey?s thoughts on this.

Trey, would you have time to help with the grid or could you let me know what the best way to do this is so I can create it myself?

Thank you!
Anna

---------------------------------
You are appreciated.
You are enough.
You matter.
You are not alone.



> On Jan 10, 2017, at 4:36 PM, Ewa Jodlowska <ewa at python.org> wrote:
> 
> I agree with Anna about the bot. I don't want you all to take on a work load that will make you uncomfortable onsite.
> 
> On Mon, Jan 9, 2017 at 6:15 PM, Anna Ossowski <ossanna16 at gmx.de <mailto:ossanna16 at gmx.de>> wrote:
> 
> I support Trey?s idea of making more prominent on the website that the Open Spaces are an event that takes place parallel to the talks and isn?t an evening event like the PyLadies auction and the PyCon dinners for example.
> Adding a grid to the Open Spaces page, as well as moving the Open Spaces page from the Events to the Schedule tab, are both great ideas.
> 
> I think this makes perfect sense and I can help with that. Once you have a grid up and it looks like a schedule, I can definitely move it over to the Schedule tab. 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pycon-openspaces/attachments/20170110/729551df/attachment.html>

From ewa at python.org  Wed Jan 11 10:27:12 2017
From: ewa at python.org (Ewa Jodlowska)
Date: Wed, 11 Jan 2017 09:27:12 -0600
Subject: [Pycon-openspaces] Open Spaces 2017 Kick Off!
In-Reply-To: <8A6A5087-527E-443A-8D5F-E928E0EB1C45@gmx.de>
References: <5CF5E3BC-0F73-43CB-9A5C-4A275867E57B@gmx.de>
 <CADx+GQM400JLoMbRzvNDMqNYDCQP8-_c8FzgzYgvo-VPY3GRLA@mail.gmail.com>
 <43917198-829F-44D5-8E88-95F53D1BB78A@gmx.de>
 <1e6065we301jubp7zows9t244-0@mailer.nylas.com>
 <B259B330-A111-409C-B418-71D38D705683@gmx.de>
 <CADx+GQO8d=HfWgUg57ErTLJL4tD_0y-VbyZQSo-8BU43fYu1pw@mail.gmail.com>
 <8A6A5087-527E-443A-8D5F-E928E0EB1C45@gmx.de>
Message-ID: <CADx+GQOCwSEe0idNBdp3cvDw2dw8A6rdoUupYtzKt_NXD3MEdw@mail.gmail.com>

I have given Trey edit privileges on CMS pages just in case that is needed.

Best regards,

Ewa
Director of Operations
Python Software Foundation
Cell: 415-319-5237

On Tue, Jan 10, 2017 at 10:17 AM, Anna Ossowski <ossanna16 at gmx.de> wrote:

> Maybe there is a way to automate this as much as possible and keep
> monitoring of the bot at a minimum but still make sure we don?t get a bunch
> of spammy or CoC violating tweets. Would love to hear Hobson?s and Trey?s
> thoughts on this.
>
> Trey, would you have time to help with the grid or could you let me know
> what the best way to do this is so I can create it myself?
>
> Thank you!
> Anna
>
> ---------------------------------
> You are appreciated.
> You are enough.
> You matter.
> You are not alone.
>
>
>
> On Jan 10, 2017, at 4:36 PM, Ewa Jodlowska <ewa at python.org> wrote:
>
> I agree with Anna about the bot. I don't want you all to take on a work
> load that will make you uncomfortable onsite.
>
> On Mon, Jan 9, 2017 at 6:15 PM, Anna Ossowski <ossanna16 at gmx.de> wrote:
>
>>
>> I support Trey?s idea of making more prominent on the website that the
>> Open Spaces are an event that takes place parallel to the talks and isn?t
>> an evening event like the PyLadies auction and the PyCon dinners for
>> example.
>> Adding a grid to the Open Spaces page, as well as moving the Open Spaces
>> page from the Events to the Schedule tab, are both great ideas.
>>
>
> I think this makes perfect sense and I can help with that. Once you have a
> grid up and it looks like a schedule, I can definitely move it over to the
> Schedule tab.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pycon-openspaces/attachments/20170111/45869433/attachment.html>

From ossanna16 at gmx.de  Wed Jan 11 10:58:41 2017
From: ossanna16 at gmx.de (Anna Ossowski)
Date: Wed, 11 Jan 2017 16:58:41 +0100
Subject: [Pycon-openspaces] Open Spaces 2017 Kick Off!
In-Reply-To: <CADx+GQOCwSEe0idNBdp3cvDw2dw8A6rdoUupYtzKt_NXD3MEdw@mail.gmail.com>
References: <5CF5E3BC-0F73-43CB-9A5C-4A275867E57B@gmx.de>
 <CADx+GQM400JLoMbRzvNDMqNYDCQP8-_c8FzgzYgvo-VPY3GRLA@mail.gmail.com>
 <43917198-829F-44D5-8E88-95F53D1BB78A@gmx.de>
 <1e6065we301jubp7zows9t244-0@mailer.nylas.com>
 <B259B330-A111-409C-B418-71D38D705683@gmx.de>
 <CADx+GQO8d=HfWgUg57ErTLJL4tD_0y-VbyZQSo-8BU43fYu1pw@mail.gmail.com>
 <8A6A5087-527E-443A-8D5F-E928E0EB1C45@gmx.de>
 <CADx+GQOCwSEe0idNBdp3cvDw2dw8A6rdoUupYtzKt_NXD3MEdw@mail.gmail.com>
Message-ID: <A33800D7-EAB7-4BCD-8D33-9BB572565649@gmx.de>

Thank you, Ewa :)

---------------------------------
You are appreciated.
You are enough.
You matter.
You are not alone.



> On Jan 11, 2017, at 4:27 PM, Ewa Jodlowska <ewa at python.org> wrote:
> 
> I have given Trey edit privileges on CMS pages just in case that is needed.
> 
> Best regards,
> 
> Ewa
> Director of Operations
> Python Software Foundation
> Cell: 415-319-5237
> 
> On Tue, Jan 10, 2017 at 10:17 AM, Anna Ossowski <ossanna16 at gmx.de <mailto:ossanna16 at gmx.de>> wrote:
> Maybe there is a way to automate this as much as possible and keep monitoring of the bot at a minimum but still make sure we don?t get a bunch of spammy or CoC violating tweets. Would love to hear Hobson?s and Trey?s thoughts on this.
> 
> Trey, would you have time to help with the grid or could you let me know what the best way to do this is so I can create it myself?
> 
> Thank you!
> Anna
> 
> ---------------------------------
> You are appreciated.
> You are enough.
> You matter.
> You are not alone.
> 
> 
> 
>> On Jan 10, 2017, at 4:36 PM, Ewa Jodlowska <ewa at python.org <mailto:ewa at python.org>> wrote:
>> 
>> I agree with Anna about the bot. I don't want you all to take on a work load that will make you uncomfortable onsite.
>> 
>> On Mon, Jan 9, 2017 at 6:15 PM, Anna Ossowski <ossanna16 at gmx.de <mailto:ossanna16 at gmx.de>> wrote:
>> 
>> I support Trey?s idea of making more prominent on the website that the Open Spaces are an event that takes place parallel to the talks and isn?t an evening event like the PyLadies auction and the PyCon dinners for example.
>> Adding a grid to the Open Spaces page, as well as moving the Open Spaces page from the Events to the Schedule tab, are both great ideas.
>> 
>> I think this makes perfect sense and I can help with that. Once you have a grid up and it looks like a schedule, I can definitely move it over to the Schedule tab. 
> 
> 

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

From pycon.brandon at gmail.com  Sun Jan 15 19:51:35 2017
From: pycon.brandon at gmail.com (Brandon Rhodes)
Date: Sun, 15 Jan 2017 19:51:35 -0500
Subject: [Pycon-openspaces] Open Spaces 2017 Kick Off!
In-Reply-To: <A33800D7-EAB7-4BCD-8D33-9BB572565649@gmx.de>
References: <5CF5E3BC-0F73-43CB-9A5C-4A275867E57B@gmx.de>
 <CADx+GQM400JLoMbRzvNDMqNYDCQP8-_c8FzgzYgvo-VPY3GRLA@mail.gmail.com>
 <43917198-829F-44D5-8E88-95F53D1BB78A@gmx.de>
 <1e6065we301jubp7zows9t244-0@mailer.nylas.com>
 <B259B330-A111-409C-B418-71D38D705683@gmx.de>
 <CADx+GQO8d=HfWgUg57ErTLJL4tD_0y-VbyZQSo-8BU43fYu1pw@mail.gmail.com>
 <8A6A5087-527E-443A-8D5F-E928E0EB1C45@gmx.de>
 <CADx+GQOCwSEe0idNBdp3cvDw2dw8A6rdoUupYtzKt_NXD3MEdw@mail.gmail.com>
 <A33800D7-EAB7-4BCD-8D33-9BB572565649@gmx.de>
Message-ID: <CAD05_ovNrmA3t2Wpd2YN_S9UQUCO17ohHGXGB4NyO1aLXRLJWw@mail.gmail.com>

Good evening, everyone! I am finally caught up after my whirlwind of
holiday travel, and am now happily ensconced at home for the winter where I
can now keep abreast of things and watch the weather forecast for
snowstorms.

In no particular order, here are some responses to all of the great ideas
that you have generated on this thread over the past week:

   - I like the idea of having Guidebook make people aware of the Open
   Spaces! I am not exactly sure how that would fit into the app because I do
   not have enough experience of it to have a clear idea of how its navigation
   works, but I am happy that your committee will be looking into where Open
   Spaces will fit.

   - A blog post is a great idea! We should aim for fairly close to the
   conference, since Open Spaces can't be scheduled far in advance ? last year
   we did an April blog post, and that feels about right for this year as well.

   - I agree that the printed schedule this year should somehow, if room
   permits, show that the Open Spaces happen in parallel with the talks. When
   we design the brochure, we'll show you the result and let you know whether
   it wound up fitting. And using the printed schedule will, I agree, be a
   more feasible approach than trying to have the registration people deliver
   the information to people who are busy registering and probably wouldn't
   absorb it anyway.

   - Open Spaces can indeed continue during sprints; I have no problem with
   them overlapping.

   - I agree that attendees need an introduction to the conference, and
   that the introduction should introduce Open Spaces! Last year I tried
   mentioning Open Spaces in my half-hour introduction to the conference,
   designed to let people know how to get the most out of it:

   https://www.youtube.com/watch?v=ckW1xuGVpug

   Fast forward to about 19:00 for the segment on Open Spaces. For 2017, I
   hope to do something similar, because I think that a reminder of everything
   that goes on at the conference is good for everyone, not just the smaller
   self-selected audience we would get if we only gave this information at a
   for-beginners event.

   Please let me know how the Open Spaces segment can be improved to
   provide more context and to better situate them in attendees' minds as
   things that go on at the same time as the main talks schedule.

   - I did wish last year that there was someone, or a group of volunteers
   instead of just one, who would tweet 15 minutes before every hour about
   what Open Spaces are happening. ?Coming up in 15 minutes, Open Spaces on:
   Astronomy; SciPy; Hardware; Diversity? or something like that, based on
   walking by the board and reading the cards. I am not sure whether
   subscribers wlil want to hear N tweets about the N events per hour, and I
   am not sure that organizers will want to have to issue a tweet about their
   event (do they all even have Twitter?) in addition to getting a card up on
   the board. But I am not going to insist on any particular approach; there
   are lots of ways that Twitter and the Open Spaces could interact, and as
   long as it doesn't involve lots of tweets from the main conference Twitter
   account, I'm happy to have y'all on the committee experiment with whatever
   idea interests you most.

   - I am not sure we should add a blank Open Spaces schedule to the
   Schedule drop-down on the site. (1) It would make organizers think they can
   sign up ahead of time, but they can't. (2) People would see it blank in the
   days before the conference and conclude that something was wrong, or that
   Open Spaces weren't really going to happen, because generally conferences
   only have schedule grids up because they have data to put in them.

   I will, however, definitely plan to re-post my
   https://us.pycon.org/2016/events/ ?Overview? page again this year as we
   release the schedule and, as you can see, it (probably similarly to what
   you were thinking about the printed brochure?) depicts the Open Spaces as
   happening simultaneously with the Talks.

   - The problem with a Twitter hashtag is that people might think they're
   supposed to subscribe to it if they're interested in Open Spaces, but you
   can't control the amount of abuse that is delivered by people who figure
   that out, because Twitter doesn't let you control what's tweeted under a
   hashtag.

There, I think that covers the main points that have been raised so far?
Feel free to make further comments on any of these matters, and I'll try to
respond with a much shorter ping time now that I'm home and back in the
loop! Thanks again for all of your thoughtful work to make Open Spaces ever
more awesome. :)

On Wed, Jan 11, 2017 at 10:58 AM, Anna Ossowski <ossanna16 at gmx.de> wrote:

> Thank you, Ewa :)
>
> ---------------------------------
> You are appreciated.
> You are enough.
> You matter.
> You are not alone.
>
>
>
> On Jan 11, 2017, at 4:27 PM, Ewa Jodlowska <ewa at python.org> wrote:
>
> I have given Trey edit privileges on CMS pages just in case that is needed.
>
> Best regards,
>
> Ewa
> Director of Operations
> Python Software Foundation
> Cell: 415-319-5237 <(415)%20319-5237>
>
> On Tue, Jan 10, 2017 at 10:17 AM, Anna Ossowski <ossanna16 at gmx.de> wrote:
>
>> Maybe there is a way to automate this as much as possible and keep
>> monitoring of the bot at a minimum but still make sure we don?t get a bunch
>> of spammy or CoC violating tweets. Would love to hear Hobson?s and Trey?s
>> thoughts on this.
>>
>> Trey, would you have time to help with the grid or could you let me know
>> what the best way to do this is so I can create it myself?
>>
>> Thank you!
>> Anna
>>
>> ---------------------------------
>> You are appreciated.
>> You are enough.
>> You matter.
>> You are not alone.
>>
>>
>>
>> On Jan 10, 2017, at 4:36 PM, Ewa Jodlowska <ewa at python.org> wrote:
>>
>> I agree with Anna about the bot. I don't want you all to take on a work
>> load that will make you uncomfortable onsite.
>>
>> On Mon, Jan 9, 2017 at 6:15 PM, Anna Ossowski <ossanna16 at gmx.de> wrote:
>>
>>>
>>> I support Trey?s idea of making more prominent on the website that the
>>> Open Spaces are an event that takes place parallel to the talks and isn?t
>>> an evening event like the PyLadies auction and the PyCon dinners for
>>> example.
>>> Adding a grid to the Open Spaces page, as well as moving the Open Spaces
>>> page from the Events to the Schedule tab, are both great ideas.
>>>
>>
>> I think this makes perfect sense and I can help with that. Once you have
>> a grid up and it looks like a schedule, I can definitely move it over to
>> the Schedule tab.
>>
>>
>>
>
>
> _______________________________________________
> Pycon-openspaces mailing list
> Pycon-openspaces at python.org
> https://mail.python.org/mailman/listinfo/pycon-openspaces
>
>


-- 
Brandon Rhodes
PyCon 2016 Conference Chair
pycon.brandon at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pycon-openspaces/attachments/20170115/a9e7f767/attachment.html>

From ossanna16 at gmx.de  Mon Jan 16 13:17:01 2017
From: ossanna16 at gmx.de (Anna Ossowski)
Date: Mon, 16 Jan 2017 19:17:01 +0100
Subject: [Pycon-openspaces] Open Spaces 2017 Kick Off!
In-Reply-To: <CAD05_ovNrmA3t2Wpd2YN_S9UQUCO17ohHGXGB4NyO1aLXRLJWw@mail.gmail.com>
References: <5CF5E3BC-0F73-43CB-9A5C-4A275867E57B@gmx.de>
 <CADx+GQM400JLoMbRzvNDMqNYDCQP8-_c8FzgzYgvo-VPY3GRLA@mail.gmail.com>
 <43917198-829F-44D5-8E88-95F53D1BB78A@gmx.de>
 <1e6065we301jubp7zows9t244-0@mailer.nylas.com>
 <B259B330-A111-409C-B418-71D38D705683@gmx.de>
 <CADx+GQO8d=HfWgUg57ErTLJL4tD_0y-VbyZQSo-8BU43fYu1pw@mail.gmail.com>
 <8A6A5087-527E-443A-8D5F-E928E0EB1C45@gmx.de>
 <CADx+GQOCwSEe0idNBdp3cvDw2dw8A6rdoUupYtzKt_NXD3MEdw@mail.gmail.com>
 <A33800D7-EAB7-4BCD-8D33-9BB572565649@gmx.de>
 <CAD05_ovNrmA3t2Wpd2YN_S9UQUCO17ohHGXGB4NyO1aLXRLJWw@mail.gmail.com>
Message-ID: <4813518C-9F4B-4527-8EBA-326A5C510423@gmx.de>

Hello Brandon!

Thank you for your thoughtful reply! I?m glad you made it back home safely.
I?m a little bit short on time at the moment but I wanted to reply right away so we can keep the conversation going. My apologies for my response being a little brief.


> On Jan 16, 2017, at 1:51 AM, Brandon Rhodes <pycon.brandon at gmail.com> wrote:
> 
> Good evening, everyone! I am finally caught up after my whirlwind of holiday travel, and am now happily ensconced at home for the winter where I can now keep abreast of things and watch the weather forecast for snowstorms.
> 
> In no particular order, here are some responses to all of the great ideas that you have generated on this thread over the past week:
> I like the idea of having Guidebook make people aware of the Open Spaces! I am not exactly sure how that would fit into the app because I do not have enough experience of it to have a clear idea of how its navigation works, but I am happy that your committee will be looking into where Open Spaces will fit.
Who is responsible for the PyCon US Guidebook; i.e. who should we reach out to about this?

> A blog post is a great idea! We should aim for fairly close to the conference, since Open Spaces can't be scheduled far in advance ? last year we did an April blog post, and that feels about right for this year as well.

That sounds good! Marked on my schedule to tackle this the beginning of April. Do you think we could reuse part of last year?s blog post since the information we want to present is mostly the same, or should we work on a completely new blog post?
> I agree that the printed schedule this year should somehow, if room permits, show that the Open Spaces happen in parallel with the talks. When we design the brochure, we'll show you the result and let you know whether it wound up fitting. And using the printed schedule will, I agree, be a more feasible approach than trying to have the registration people deliver the information to people who are busy registering and probably wouldn't absorb it anyway.

That sounds good! Thank you!
> Open Spaces can indeed continue during sprints; I have no problem with them overlapping.

?
> I agree that attendees need an introduction to the conference, and that the introduction should introduce Open Spaces! Last year I tried mentioning Open Spaces in my half-hour introduction to the conference, designed to let people know how to get the most out of it:
> 
> https://www.youtube.com/watch?v=ckW1xuGVpug <https://www.youtube.com/watch?v=ckW1xuGVpug>
> 
> Fast forward to about 19:00 for the segment on Open Spaces. For 2017, I hope to do something similar, because I think that a reminder of everything that goes on at the conference is good for everyone, not just the smaller self-selected audience we would get if we only gave this information at a for-beginners event.
> 
> Please let me know how the Open Spaces segment can be improved to provide more context and to better situate them in attendees' minds as things that go on at the same time as the main talks schedule.

I remember you mentioning the Open Spaces in your opening remarks last year and also in your morning remarks during the other two conference days (?), which was great! I added a note to our Trello board to discuss how we could potentially improve that segment.
> I did wish last year that there was someone, or a group of volunteers instead of just one, who would tweet 15 minutes before every hour about what Open Spaces are happening. ?Coming up in 15 minutes, Open Spaces on: Astronomy; SciPy; Hardware; Diversity? or something like that, based on walking by the board and reading the cards. I am not sure whether subscribers wlil want to hear N tweets about the N events per hour, and I am not sure that organizers will want to have to issue a tweet about their event (do they all even have Twitter?) in addition to getting a card up on the board. But I am not going to insist on any particular approach; there are lots of ways that Twitter and the Open Spaces could interact, and as long as it doesn't involve lots of tweets from the main conference Twitter account, I'm happy to have y'all on the committee experiment with whatever idea interests you most.

I agree that this would indeed be awesome! However, I think this would be quite an effort to organize and coordinate to make it go smoothly. We would have to find a group of responsible volunteers who would be willing to do this in 2 or 3 hour shifts. Additionally we would have to make sure that all of them have access to either the PyCon (probably not the preferred way to do this) or a PyCon Open Spaces Twitter account. They could simply tweet from their personal Twitter accounts but then we?d be running into the ?What if they don?t have Twitter? problem again, and for announcements like these I think it might be best to tweet them from one account instead of just asking each volunteer to tweet from their personal account using our hashtag.

You definitely mention good points we?ll have to think about regarding the bot. If I was an organizer and I?d want for people to show up to my Open Space, I wouldn?t mind writing one tweet about it, but that may not be the case for everyone. Also I believe that a lot of people these days do have Twitter accounts but not all of them do. 
I would still like to give the bot a try. We?d have to clarify that the bot won?t provide a full summary of all Open Spaces but is just functioning as a tool to help promote those Open Spaces more whose organizers tweet about it (then we are technically discriminating against people who don?t have Twitter but I don?t now how to solve the problem in this context.) Maybe we could somehow have the bot tweet out summaries of which Open Spaces are coming up instead of simple retweets in order to keep the amount of tweets the bot sends out relatively low? Any ideas, Hobson?

Neither of the two approaches are 100% ideal but the bot would at least offer some amount of ?official? promotion and definitely an improvement to last year. I guess it?s all a matter of trial and error. If we see that the bot isn?t as successful this year as we were hoping it would be, we can always try the more hands-on volunteer approach next year.

> I am not sure we should add a blank Open Spaces schedule to the Schedule drop-down on the site. (1) It would make organizers think they can sign up ahead of time, but they can't. (2) People would see it blank in the days before the conference and conclude that something was wrong, or that Open Spaces weren't really going to happen, because generally conferences only have schedule grids up because they have data to put in them.
> 
> I will, however, definitely plan to re-post my https://us.pycon.org/2016/events/ <https://us.pycon.org/2016/events/> ?Overview? page again this year as we release the schedule and, as you can see, it (probably similarly to what you were thinking about the printed brochure?) depicts the Open Spaces as happening simultaneously with the Talks.

Trey, you mentioned Open Source bridge providing an empty schedule on their website. Do you think you could comment on Brandon?s concerns regarding if Open Source bridge face any of these problems, etc.?
> The problem with a Twitter hashtag is that people might think they're supposed to subscribe to it if they're interested in Open Spaces, but you can't control the amount of abuse that is delivered by people who figure that out, because Twitter doesn't let you control what's tweeted under a hashtag.

Agreed. 
Hobson, do you have any ideas on how to prevent abuse as much as possible? Could we use something which is more reliable than a Twitter hashtag for filtering the tweets?

> There, I think that covers the main points that have been raised so far? Feel free to make further comments on any of these matters, and I'll try to respond with a much shorter ping time now that I'm home and back in the loop! Thanks again for all of your thoughtful work to make Open Spaces ever more awesome. :)

Thanks again Brandon! I always appreciate reading your input :)
Anna
> 
> On Wed, Jan 11, 2017 at 10:58 AM, Anna Ossowski <ossanna16 at gmx.de <mailto:ossanna16 at gmx.de>> wrote:
> Thank you, Ewa :)
> 
> ---------------------------------
> You are appreciated.
> You are enough.
> You matter.
> You are not alone.
> 
> 
> 
>> On Jan 11, 2017, at 4:27 PM, Ewa Jodlowska <ewa at python.org <mailto:ewa at python.org>> wrote:
>> 
>> I have given Trey edit privileges on CMS pages just in case that is needed.
>> 
>> Best regards,
>> 
>> Ewa
>> Director of Operations
>> Python Software Foundation
>> Cell: 415-319-5237 <tel:(415)%20319-5237>
>> On Tue, Jan 10, 2017 at 10:17 AM, Anna Ossowski <ossanna16 at gmx.de <mailto:ossanna16 at gmx.de>> wrote:
>> Maybe there is a way to automate this as much as possible and keep monitoring of the bot at a minimum but still make sure we don?t get a bunch of spammy or CoC violating tweets. Would love to hear Hobson?s and Trey?s thoughts on this.
>> 
>> Trey, would you have time to help with the grid or could you let me know what the best way to do this is so I can create it myself?
>> 
>> Thank you!
>> Anna
>> 
>> ---------------------------------
>> You are appreciated.
>> You are enough.
>> You matter.
>> You are not alone.
>> 
>> 
>> 
>>> On Jan 10, 2017, at 4:36 PM, Ewa Jodlowska <ewa at python.org <mailto:ewa at python.org>> wrote:
>>> 
>>> I agree with Anna about the bot. I don't want you all to take on a work load that will make you uncomfortable onsite.
>>> 
>>> On Mon, Jan 9, 2017 at 6:15 PM, Anna Ossowski <ossanna16 at gmx.de <mailto:ossanna16 at gmx.de>> wrote:
>>> 
>>> I support Trey?s idea of making more prominent on the website that the Open Spaces are an event that takes place parallel to the talks and isn?t an evening event like the PyLadies auction and the PyCon dinners for example.
>>> Adding a grid to the Open Spaces page, as well as moving the Open Spaces page from the Events to the Schedule tab, are both great ideas.
>>> 
>>> I think this makes perfect sense and I can help with that. Once you have a grid up and it looks like a schedule, I can definitely move it over to the Schedule tab. 
>> 
>> 
> 
> 
> _______________________________________________
> 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>
> 
> 
> 
> 
> -- 
> Brandon Rhodes
> PyCon 2016 Conference Chair
> pycon.brandon at gmail.com <mailto:pycon.brandon at gmail.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pycon-openspaces/attachments/20170116/bd0504a0/attachment-0001.html>

From hobsonlane at gmail.com  Mon Jan 16 13:24:15 2017
From: hobsonlane at gmail.com (Hobson Lane)
Date: Mon, 16 Jan 2017 10:24:15 -0800
Subject: [Pycon-openspaces] Open Spaces 2017 Kick Off!
In-Reply-To: <CAD05_ovNrmA3t2Wpd2YN_S9UQUCO17ohHGXGB4NyO1aLXRLJWw@mail.gmail.com>
References: <5CF5E3BC-0F73-43CB-9A5C-4A275867E57B@gmx.de>
 <CADx+GQM400JLoMbRzvNDMqNYDCQP8-_c8FzgzYgvo-VPY3GRLA@mail.gmail.com>
 <43917198-829F-44D5-8E88-95F53D1BB78A@gmx.de>
 <1e6065we301jubp7zows9t244-0@mailer.nylas.com>
 <B259B330-A111-409C-B418-71D38D705683@gmx.de>
 <CADx+GQO8d=HfWgUg57ErTLJL4tD_0y-VbyZQSo-8BU43fYu1pw@mail.gmail.com>
 <8A6A5087-527E-443A-8D5F-E928E0EB1C45@gmx.de>
 <CADx+GQOCwSEe0idNBdp3cvDw2dw8A6rdoUupYtzKt_NXD3MEdw@mail.gmail.com>
 <A33800D7-EAB7-4BCD-8D33-9BB572565649@gmx.de>
 <CAD05_ovNrmA3t2Wpd2YN_S9UQUCO17ohHGXGB4NyO1aLXRLJWw@mail.gmail.com>
Message-ID: <CACZ_DofAT3VA2h6GWbUHOXP9R9v84y6jbZYjRFUTKMwPc8126A@mail.gmail.com>

Regarding the tweeter:

* Open spaces organizers will have a throttle to limit the tweet rate/volume
* Organizers will control a spam prefilter to minimize their curation effort
* Anna is monitoring the development effort, helping to incorporate
features suggested by PyCon organizers
* We can tweet from whatever account pycon organizers would like

Deciding a tweet-from account is important, but doesn't have to be made
until after PyCon organziers have had a chance to test the tweeter on a
private slack channel over an extended period of time, including pen
testing the bot with spam/hack DMs on twitter. Possibilities for the
twitter username include @pyconopenspaces or a name completely
unassocciated with PyCon publicly, but completely under PyCon organizer
control. And depending on the address, the tweets would be taylored to that
account's content plan and would be under that account maintainer's control.

--Hobson
(503) 974-6274
gh <https://github.com/hobson/> twtr <https://twitter.com/hobsonlane> li
<https://www.linkedin.com/in/hobsonlane> g+
<http://plus.google.com/+HobsonLane/> so
<http://stackoverflow.com/users/623735/hobs>

On Sun, Jan 15, 2017 at 4:51 PM, Brandon Rhodes <pycon.brandon at gmail.com>
wrote:

> Good evening, everyone! I am finally caught up after my whirlwind of
> holiday travel, and am now happily ensconced at home for the winter where I
> can now keep abreast of things and watch the weather forecast for
> snowstorms.
>
> In no particular order, here are some responses to all of the great ideas
> that you have generated on this thread over the past week:
>
>    - I like the idea of having Guidebook make people aware of the Open
>    Spaces! I am not exactly sure how that would fit into the app because I do
>    not have enough experience of it to have a clear idea of how its navigation
>    works, but I am happy that your committee will be looking into where Open
>    Spaces will fit.
>
>    - A blog post is a great idea! We should aim for fairly close to the
>    conference, since Open Spaces can't be scheduled far in advance ? last year
>    we did an April blog post, and that feels about right for this year as well.
>
>    - I agree that the printed schedule this year should somehow, if room
>    permits, show that the Open Spaces happen in parallel with the talks. When
>    we design the brochure, we'll show you the result and let you know whether
>    it wound up fitting. And using the printed schedule will, I agree, be a
>    more feasible approach than trying to have the registration people deliver
>    the information to people who are busy registering and probably wouldn't
>    absorb it anyway.
>
>    - Open Spaces can indeed continue during sprints; I have no problem
>    with them overlapping.
>
>    - I agree that attendees need an introduction to the conference, and
>    that the introduction should introduce Open Spaces! Last year I tried
>    mentioning Open Spaces in my half-hour introduction to the conference,
>    designed to let people know how to get the most out of it:
>
>    https://www.youtube.com/watch?v=ckW1xuGVpug
>
>    Fast forward to about 19:00 for the segment on Open Spaces. For 2017,
>    I hope to do something similar, because I think that a reminder of
>    everything that goes on at the conference is good for everyone, not just
>    the smaller self-selected audience we would get if we only gave this
>    information at a for-beginners event.
>
>    Please let me know how the Open Spaces segment can be improved to
>    provide more context and to better situate them in attendees' minds as
>    things that go on at the same time as the main talks schedule.
>
>    - I did wish last year that there was someone, or a group of
>    volunteers instead of just one, who would tweet 15 minutes before every
>    hour about what Open Spaces are happening. ?Coming up in 15 minutes, Open
>    Spaces on: Astronomy; SciPy; Hardware; Diversity? or something like that,
>    based on walking by the board and reading the cards. I am not sure whether
>    subscribers wlil want to hear N tweets about the N events per hour, and I
>    am not sure that organizers will want to have to issue a tweet about their
>    event (do they all even have Twitter?) in addition to getting a card up on
>    the board. But I am not going to insist on any particular approach; there
>    are lots of ways that Twitter and the Open Spaces could interact, and as
>    long as it doesn't involve lots of tweets from the main conference Twitter
>    account, I'm happy to have y'all on the committee experiment with whatever
>    idea interests you most.
>
>    - I am not sure we should add a blank Open Spaces schedule to the
>    Schedule drop-down on the site. (1) It would make organizers think they can
>    sign up ahead of time, but they can't. (2) People would see it blank in the
>    days before the conference and conclude that something was wrong, or that
>    Open Spaces weren't really going to happen, because generally conferences
>    only have schedule grids up because they have data to put in them.
>
>    I will, however, definitely plan to re-post my
>    https://us.pycon.org/2016/events/ <https://us.pycon.org/2016/events/>
>    ?Overview? page again this year as we release the schedule and, as you can
>    see, it (probably similarly to what you were thinking about the printed
>    brochure?) depicts the Open Spaces as happening simultaneously with the
>    Talks.
>
>    - The problem with a Twitter hashtag is that people might think
>    they're supposed to subscribe to it if they're interested in Open Spaces,
>    but you can't control the amount of abuse that is delivered by people who
>    figure that out, because Twitter doesn't let you control what's tweeted
>    under a hashtag.
>
> There, I think that covers the main points that have been raised so far?
> Feel free to make further comments on any of these matters, and I'll try to
> respond with a much shorter ping time now that I'm home and back in the
> loop! Thanks again for all of your thoughtful work to make Open Spaces ever
> more awesome. :)
>
> On Wed, Jan 11, 2017 at 10:58 AM, Anna Ossowski <ossanna16 at gmx.de> wrote:
>
>> Thank you, Ewa :)
>>
>> ---------------------------------
>> You are appreciated.
>> You are enough.
>> You matter.
>> You are not alone.
>>
>>
>>
>> On Jan 11, 2017, at 4:27 PM, Ewa Jodlowska <ewa at python.org> wrote:
>>
>> I have given Trey edit privileges on CMS pages just in case that is
>> needed.
>>
>> Best regards,
>>
>> Ewa
>> Director of Operations
>> Python Software Foundation
>> Cell: 415-319-5237 <(415)%20319-5237>
>>
>> On Tue, Jan 10, 2017 at 10:17 AM, Anna Ossowski <ossanna16 at gmx.de> wrote:
>>
>>> Maybe there is a way to automate this as much as possible and keep
>>> monitoring of the bot at a minimum but still make sure we don?t get a bunch
>>> of spammy or CoC violating tweets. Would love to hear Hobson?s and Trey?s
>>> thoughts on this.
>>>
>>> Trey, would you have time to help with the grid or could you let me know
>>> what the best way to do this is so I can create it myself?
>>>
>>> Thank you!
>>> Anna
>>>
>>> ---------------------------------
>>> You are appreciated.
>>> You are enough.
>>> You matter.
>>> You are not alone.
>>>
>>>
>>>
>>> On Jan 10, 2017, at 4:36 PM, Ewa Jodlowska <ewa at python.org> wrote:
>>>
>>> I agree with Anna about the bot. I don't want you all to take on a work
>>> load that will make you uncomfortable onsite.
>>>
>>> On Mon, Jan 9, 2017 at 6:15 PM, Anna Ossowski <ossanna16 at gmx.de> wrote:
>>>
>>>>
>>>> I support Trey?s idea of making more prominent on the website that the
>>>> Open Spaces are an event that takes place parallel to the talks and isn?t
>>>> an evening event like the PyLadies auction and the PyCon dinners for
>>>> example.
>>>> Adding a grid to the Open Spaces page, as well as moving the Open
>>>> Spaces page from the Events to the Schedule tab, are both great ideas.
>>>>
>>>
>>> I think this makes perfect sense and I can help with that. Once you have
>>> a grid up and it looks like a schedule, I can definitely move it over to
>>> the Schedule tab.
>>>
>>>
>>>
>>
>>
>> _______________________________________________
>> Pycon-openspaces mailing list
>> Pycon-openspaces at python.org
>> https://mail.python.org/mailman/listinfo/pycon-openspaces
>>
>>
>
>
> --
> Brandon Rhodes
> PyCon 2016 Conference Chair
> pycon.brandon at gmail.com
>
> _______________________________________________
> 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/20170116/cbd924ad/attachment.html>

From ossanna16 at gmx.de  Mon Jan 16 13:32:53 2017
From: ossanna16 at gmx.de (Anna Ossowski)
Date: Mon, 16 Jan 2017 19:32:53 +0100
Subject: [Pycon-openspaces] Open Spaces 2017 Kick Off!
In-Reply-To: <CACZ_DofAT3VA2h6GWbUHOXP9R9v84y6jbZYjRFUTKMwPc8126A@mail.gmail.com>
References: <5CF5E3BC-0F73-43CB-9A5C-4A275867E57B@gmx.de>
 <CADx+GQM400JLoMbRzvNDMqNYDCQP8-_c8FzgzYgvo-VPY3GRLA@mail.gmail.com>
 <43917198-829F-44D5-8E88-95F53D1BB78A@gmx.de>
 <1e6065we301jubp7zows9t244-0@mailer.nylas.com>
 <B259B330-A111-409C-B418-71D38D705683@gmx.de>
 <CADx+GQO8d=HfWgUg57ErTLJL4tD_0y-VbyZQSo-8BU43fYu1pw@mail.gmail.com>
 <8A6A5087-527E-443A-8D5F-E928E0EB1C45@gmx.de>
 <CADx+GQOCwSEe0idNBdp3cvDw2dw8A6rdoUupYtzKt_NXD3MEdw@mail.gmail.com>
 <A33800D7-EAB7-4BCD-8D33-9BB572565649@gmx.de>
 <CAD05_ovNrmA3t2Wpd2YN_S9UQUCO17ohHGXGB4NyO1aLXRLJWw@mail.gmail.com>
 <CACZ_DofAT3VA2h6GWbUHOXP9R9v84y6jbZYjRFUTKMwPc8126A@mail.gmail.com>
Message-ID: <02C741D7-2905-4FE7-AB7D-32965E155D90@gmx.de>

Thank you, Hobson! 



> On Jan 16, 2017, at 7:24 PM, Hobson Lane <hobsonlane at gmail.com> wrote:
> 
> Regarding the tweeter:
> 
> * Open spaces organizers will have a throttle to limit the tweet rate/volume
> * Organizers will control a spam prefilter to minimize their curation effort
> * Anna is monitoring the development effort, helping to incorporate features suggested by PyCon organizers
> * We can tweet from whatever account pycon organizers would like
> 
> Deciding a tweet-from account is important, but doesn't have to be made until after PyCon organziers have had a chance to test the tweeter on a private slack channel over an extended period of time, including pen testing the bot with spam/hack DMs on twitter. Possibilities for the twitter username include @pyconopenspaces or a name completely unassocciated with PyCon publicly, but completely under PyCon organizer control. And depending on the address, the tweets would be taylored to that account's content plan and would be under that account maintainer's control.
> 
> --Hobson
> (503) 974-6274
> gh <https://github.com/hobson/> twtr <https://twitter.com/hobsonlane> li <https://www.linkedin.com/in/hobsonlane> g+ <http://plus.google.com/+HobsonLane/> so <http://stackoverflow.com/users/623735/hobs>
> On Sun, Jan 15, 2017 at 4:51 PM, Brandon Rhodes <pycon.brandon at gmail.com <mailto:pycon.brandon at gmail.com>> wrote:
> Good evening, everyone! I am finally caught up after my whirlwind of holiday travel, and am now happily ensconced at home for the winter where I can now keep abreast of things and watch the weather forecast for snowstorms.
> 
> In no particular order, here are some responses to all of the great ideas that you have generated on this thread over the past week:
> I like the idea of having Guidebook make people aware of the Open Spaces! I am not exactly sure how that would fit into the app because I do not have enough experience of it to have a clear idea of how its navigation works, but I am happy that your committee will be looking into where Open Spaces will fit.
> 
> A blog post is a great idea! We should aim for fairly close to the conference, since Open Spaces can't be scheduled far in advance ? last year we did an April blog post, and that feels about right for this year as well.
> 
> I agree that the printed schedule this year should somehow, if room permits, show that the Open Spaces happen in parallel with the talks. When we design the brochure, we'll show you the result and let you know whether it wound up fitting. And using the printed schedule will, I agree, be a more feasible approach than trying to have the registration people deliver the information to people who are busy registering and probably wouldn't absorb it anyway.
> 
> Open Spaces can indeed continue during sprints; I have no problem with them overlapping.
> 
> I agree that attendees need an introduction to the conference, and that the introduction should introduce Open Spaces! Last year I tried mentioning Open Spaces in my half-hour introduction to the conference, designed to let people know how to get the most out of it:
> 
> https://www.youtube.com/watch?v=ckW1xuGVpug <https://www.youtube.com/watch?v=ckW1xuGVpug>
> 
> Fast forward to about 19:00 for the segment on Open Spaces. For 2017, I hope to do something similar, because I think that a reminder of everything that goes on at the conference is good for everyone, not just the smaller self-selected audience we would get if we only gave this information at a for-beginners event.
> 
> Please let me know how the Open Spaces segment can be improved to provide more context and to better situate them in attendees' minds as things that go on at the same time as the main talks schedule.
> 
> I did wish last year that there was someone, or a group of volunteers instead of just one, who would tweet 15 minutes before every hour about what Open Spaces are happening. ?Coming up in 15 minutes, Open Spaces on: Astronomy; SciPy; Hardware; Diversity? or something like that, based on walking by the board and reading the cards. I am not sure whether subscribers wlil want to hear N tweets about the N events per hour, and I am not sure that organizers will want to have to issue a tweet about their event (do they all even have Twitter?) in addition to getting a card up on the board. But I am not going to insist on any particular approach; there are lots of ways that Twitter and the Open Spaces could interact, and as long as it doesn't involve lots of tweets from the main conference Twitter account, I'm happy to have y'all on the committee experiment with whatever idea interests you most.
> 
> I am not sure we should add a blank Open Spaces schedule to the Schedule drop-down on the site. (1) It would make organizers think they can sign up ahead of time, but they can't. (2) People would see it blank in the days before the conference and conclude that something was wrong, or that Open Spaces weren't really going to happen, because generally conferences only have schedule grids up because they have data to put in them.
> 
> I will, however, definitely plan to re-post my https://us.pycon.org/2016/events/ <https://us.pycon.org/2016/events/> ?Overview? page again this year as we release the schedule and, as you can see, it (probably similarly to what you were thinking about the printed brochure?) depicts the Open Spaces as happening simultaneously with the Talks.
> 
> The problem with a Twitter hashtag is that people might think they're supposed to subscribe to it if they're interested in Open Spaces, but you can't control the amount of abuse that is delivered by people who figure that out, because Twitter doesn't let you control what's tweeted under a hashtag.
> There, I think that covers the main points that have been raised so far? Feel free to make further comments on any of these matters, and I'll try to respond with a much shorter ping time now that I'm home and back in the loop! Thanks again for all of your thoughtful work to make Open Spaces ever more awesome. :)
> 
> On Wed, Jan 11, 2017 at 10:58 AM, Anna Ossowski <ossanna16 at gmx.de <mailto:ossanna16 at gmx.de>> wrote:
> Thank you, Ewa :)
> 
> ---------------------------------
> You are appreciated.
> You are enough.
> You matter.
> You are not alone.
> 
> 
> 
>> On Jan 11, 2017, at 4:27 PM, Ewa Jodlowska <ewa at python.org <mailto:ewa at python.org>> wrote:
>> 
>> I have given Trey edit privileges on CMS pages just in case that is needed.
>> 
>> Best regards,
>> 
>> Ewa
>> Director of Operations
>> Python Software Foundation
>> Cell: 415-319-5237 <tel:(415)%20319-5237>
>> On Tue, Jan 10, 2017 at 10:17 AM, Anna Ossowski <ossanna16 at gmx.de <mailto:ossanna16 at gmx.de>> wrote:
>> Maybe there is a way to automate this as much as possible and keep monitoring of the bot at a minimum but still make sure we don?t get a bunch of spammy or CoC violating tweets. Would love to hear Hobson?s and Trey?s thoughts on this.
>> 
>> Trey, would you have time to help with the grid or could you let me know what the best way to do this is so I can create it myself?
>> 
>> Thank you!
>> Anna
>> 
>> ---------------------------------
>> You are appreciated.
>> You are enough.
>> You matter.
>> You are not alone.
>> 
>> 
>> 
>>> On Jan 10, 2017, at 4:36 PM, Ewa Jodlowska <ewa at python.org <mailto:ewa at python.org>> wrote:
>>> 
>>> I agree with Anna about the bot. I don't want you all to take on a work load that will make you uncomfortable onsite.
>>> 
>>> On Mon, Jan 9, 2017 at 6:15 PM, Anna Ossowski <ossanna16 at gmx.de <mailto:ossanna16 at gmx.de>> wrote:
>>> 
>>> I support Trey?s idea of making more prominent on the website that the Open Spaces are an event that takes place parallel to the talks and isn?t an evening event like the PyLadies auction and the PyCon dinners for example.
>>> Adding a grid to the Open Spaces page, as well as moving the Open Spaces page from the Events to the Schedule tab, are both great ideas.
>>> 
>>> I think this makes perfect sense and I can help with that. Once you have a grid up and it looks like a schedule, I can definitely move it over to the Schedule tab. 
>> 
>> 
> 
> 
> _______________________________________________
> 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>
> 
> 
> 
> 
> -- 
> Brandon Rhodes
> PyCon 2016 Conference Chair
> pycon.brandon at gmail.com <mailto:pycon.brandon at gmail.com>
> _______________________________________________
> 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/20170116/a52d5614/attachment-0001.html>

From hobsonlane at gmail.com  Mon Jan 16 13:34:22 2017
From: hobsonlane at gmail.com (Hobson Lane)
Date: Mon, 16 Jan 2017 10:34:22 -0800
Subject: [Pycon-openspaces] Open Spaces 2017 Kick Off!
In-Reply-To: <4813518C-9F4B-4527-8EBA-326A5C510423@gmx.de>
References: <5CF5E3BC-0F73-43CB-9A5C-4A275867E57B@gmx.de>
 <CADx+GQM400JLoMbRzvNDMqNYDCQP8-_c8FzgzYgvo-VPY3GRLA@mail.gmail.com>
 <43917198-829F-44D5-8E88-95F53D1BB78A@gmx.de>
 <1e6065we301jubp7zows9t244-0@mailer.nylas.com>
 <B259B330-A111-409C-B418-71D38D705683@gmx.de>
 <CADx+GQO8d=HfWgUg57ErTLJL4tD_0y-VbyZQSo-8BU43fYu1pw@mail.gmail.com>
 <8A6A5087-527E-443A-8D5F-E928E0EB1C45@gmx.de>
 <CADx+GQOCwSEe0idNBdp3cvDw2dw8A6rdoUupYtzKt_NXD3MEdw@mail.gmail.com>
 <A33800D7-EAB7-4BCD-8D33-9BB572565649@gmx.de>
 <CAD05_ovNrmA3t2Wpd2YN_S9UQUCO17ohHGXGB4NyO1aLXRLJWw@mail.gmail.com>
 <4813518C-9F4B-4527-8EBA-326A5C510423@gmx.de>
Message-ID: <CACZ_DofKAccuvW4RyBkeCk82BBD-tu262NdZ9ysoq=UCd8Coeg@mail.gmail.com>

Hi Anna,

Good idea on the schedule summarizer. It's definitely straightforward for
the twitter buffer to summarize several upcoming Open Spaces events with
single tweet to reduce the tweet volume/rate. All tweets from the bot can
include a link to its schedule of upcoming openspaces and an image of the
latest Open Spaces poster.

--Hobson
(503) 974-6274
gh <https://github.com/hobson/> twtr <https://twitter.com/hobsonlane> li
<https://www.linkedin.com/in/hobsonlane> g+
<http://plus.google.com/+HobsonLane/> so
<http://stackoverflow.com/users/623735/hobs>

On Mon, Jan 16, 2017 at 10:17 AM, Anna Ossowski <ossanna16 at gmx.de> wrote:

> Hello Brandon!
>
> Thank you for your thoughtful reply! I?m glad you made it back home safely.
> I?m a little bit short on time at the moment but I wanted to reply right
> away so we can keep the conversation going. My apologies for my response
> being a little brief.
>
>
> On Jan 16, 2017, at 1:51 AM, Brandon Rhodes <pycon.brandon at gmail.com>
> wrote:
>
> Good evening, everyone! I am finally caught up after my whirlwind of
> holiday travel, and am now happily ensconced at home for the winter where I
> can now keep abreast of things and watch the weather forecast for
> snowstorms.
>
> In no particular order, here are some responses to all of the great ideas
> that you have generated on this thread over the past week:
>
>    - I like the idea of having Guidebook make people aware of the Open
>    Spaces! I am not exactly sure how that would fit into the app because I do
>    not have enough experience of it to have a clear idea of how its navigation
>    works, but I am happy that your committee will be looking into where Open
>    Spaces will fit.
>
> Who is responsible for the PyCon US Guidebook; i.e. who should we reach
> out to about this?
>
>
>    - A blog post is a great idea! We should aim for fairly close to the
>    conference, since Open Spaces can't be scheduled far in advance ? last year
>    we did an April blog post, and that feels about right for this year as well.
>
>
> That sounds good! Marked on my schedule to tackle this the beginning of
> April. Do you think we could reuse part of last year?s blog post since the
> information we want to present is mostly the same, or should we work on a
> completely new blog post?
>
>
>    - I agree that the printed schedule this year should somehow, if room
>    permits, show that the Open Spaces happen in parallel with the talks. When
>    we design the brochure, we'll show you the result and let you know whether
>    it wound up fitting. And using the printed schedule will, I agree, be a
>    more feasible approach than trying to have the registration people deliver
>    the information to people who are busy registering and probably wouldn't
>    absorb it anyway.
>
>
> That sounds good! Thank you!
>
>
>    - Open Spaces can indeed continue during sprints; I have no problem
>    with them overlapping.
>
>
> ?
>
>
>    - I agree that attendees need an introduction to the conference, and
>    that the introduction should introduce Open Spaces! Last year I tried
>    mentioning Open Spaces in my half-hour introduction to the conference,
>    designed to let people know how to get the most out of it:
>
>    https://www.youtube.com/watch?v=ckW1xuGVpug
>
>    Fast forward to about 19:00 for the segment on Open Spaces. For 2017,
>    I hope to do something similar, because I think that a reminder of
>    everything that goes on at the conference is good for everyone, not just
>    the smaller self-selected audience we would get if we only gave this
>    information at a for-beginners event.
>
>    Please let me know how the Open Spaces segment can be improved to
>    provide more context and to better situate them in attendees' minds as
>    things that go on at the same time as the main talks schedule.
>
>
> I remember you mentioning the Open Spaces in your opening remarks last
> year and also in your morning remarks during the other two conference days
> (?), which was great! I added a note to our Trello board to discuss how we
> could potentially improve that segment.
>
>
>    - I did wish last year that there was someone, or a group of
>    volunteers instead of just one, who would tweet 15 minutes before every
>    hour about what Open Spaces are happening. ?Coming up in 15 minutes, Open
>    Spaces on: Astronomy; SciPy; Hardware; Diversity? or something like that,
>    based on walking by the board and reading the cards. I am not sure whether
>    subscribers wlil want to hear N tweets about the N events per hour, and I
>    am not sure that organizers will want to have to issue a tweet about their
>    event (do they all even have Twitter?) in addition to getting a card up on
>    the board. But I am not going to insist on any particular approach; there
>    are lots of ways that Twitter and the Open Spaces could interact, and as
>    long as it doesn't involve lots of tweets from the main conference Twitter
>    account, I'm happy to have y'all on the committee experiment with whatever
>    idea interests you most.
>
>
> I agree that this would indeed be awesome! However, I think this would be
> quite an effort to organize and coordinate to make it go smoothly. We would
> have to find a group of responsible volunteers who would be willing to do
> this in 2 or 3 hour shifts. Additionally we would have to make sure that
> all of them have access to either the PyCon (probably not the preferred way
> to do this) or a PyCon Open Spaces Twitter account. They could simply tweet
> from their personal Twitter accounts but then we?d be running into the
> ?What if they don?t have Twitter? problem again, and for announcements like
> these I think it might be best to tweet them from one account instead of
> just asking each volunteer to tweet from their personal account using our
> hashtag.
>
> You definitely mention good points we?ll have to think about regarding the
> bot. If I was an organizer and I?d want for people to show up to my Open
> Space, I wouldn?t mind writing one tweet about it, but that may not be the
> case for everyone. Also I believe that a lot of people these days do have
> Twitter accounts but not all of them do.
> I would still like to give the bot a try. We?d have to clarify that the
> bot won?t provide a full summary of all Open Spaces but is just functioning
> as a tool to help promote those Open Spaces more whose organizers tweet
> about it (then we are technically discriminating against people who don?t
> have Twitter but I don?t now how to solve the problem in this context.)
> Maybe we could somehow have the bot tweet out summaries of which Open
> Spaces are coming up instead of simple retweets in order to keep the amount
> of tweets the bot sends out relatively low? Any ideas, Hobson?
>
> Neither of the two approaches are 100% ideal but the bot would at least
> offer some amount of ?official? promotion and definitely an improvement to
> last year. I guess it?s all a matter of trial and error. If we see that the
> bot isn?t as successful this year as we were hoping it would be, we can
> always try the more hands-on volunteer approach next year.
>
>
>    - I am not sure we should add a blank Open Spaces schedule to the
>    Schedule drop-down on the site. (1) It would make organizers think they can
>    sign up ahead of time, but they can't. (2) People would see it blank in the
>    days before the conference and conclude that something was wrong, or that
>    Open Spaces weren't really going to happen, because generally conferences
>    only have schedule grids up because they have data to put in them.
>
>    I will, however, definitely plan to re-post my
>    https://us.pycon.org/2016/events/ <https://us.pycon.org/2016/events/>
>    ?Overview? page again this year as we release the schedule and, as you can
>    see, it (probably similarly to what you were thinking about the printed
>    brochure?) depicts the Open Spaces as happening simultaneously with the
>    Talks.
>
>
> Trey, you mentioned Open Source bridge providing an empty schedule on
> their website. Do you think you could comment on Brandon?s concerns
> regarding if Open Source bridge face any of these problems, etc.?
>
>
>    - The problem with a Twitter hashtag is that people might think
>    they're supposed to subscribe to it if they're interested in Open Spaces,
>    but you can't control the amount of abuse that is delivered by people who
>    figure that out, because Twitter doesn't let you control what's tweeted
>    under a hashtag.
>
>
> Agreed.
> Hobson, do you have any ideas on how to prevent abuse as much as possible?
> Could we use something which is more reliable than a Twitter hashtag for
> filtering the tweets?
>
> There, I think that covers the main points that have been raised so far?
> Feel free to make further comments on any of these matters, and I'll try to
> respond with a much shorter ping time now that I'm home and back in the
> loop! Thanks again for all of your thoughtful work to make Open Spaces ever
> more awesome. :)
>
>
> Thanks again Brandon! I always appreciate reading your input :)
> Anna
>
>
> On Wed, Jan 11, 2017 at 10:58 AM, Anna Ossowski <ossanna16 at gmx.de> wrote:
>
>> Thank you, Ewa :)
>>
>> ---------------------------------
>> You are appreciated.
>> You are enough.
>> You matter.
>> You are not alone.
>>
>>
>>
>> On Jan 11, 2017, at 4:27 PM, Ewa Jodlowska <ewa at python.org> wrote:
>>
>> I have given Trey edit privileges on CMS pages just in case that is
>> needed.
>>
>> Best regards,
>>
>> Ewa
>> Director of Operations
>> Python Software Foundation
>> Cell: 415-319-5237 <(415)%20319-5237>
>>
>> On Tue, Jan 10, 2017 at 10:17 AM, Anna Ossowski <ossanna16 at gmx.de> wrote:
>>
>>> Maybe there is a way to automate this as much as possible and keep
>>> monitoring of the bot at a minimum but still make sure we don?t get a bunch
>>> of spammy or CoC violating tweets. Would love to hear Hobson?s and Trey?s
>>> thoughts on this.
>>>
>>> Trey, would you have time to help with the grid or could you let me know
>>> what the best way to do this is so I can create it myself?
>>>
>>> Thank you!
>>> Anna
>>>
>>> ---------------------------------
>>> You are appreciated.
>>> You are enough.
>>> You matter.
>>> You are not alone.
>>>
>>>
>>>
>>> On Jan 10, 2017, at 4:36 PM, Ewa Jodlowska <ewa at python.org> wrote:
>>>
>>> I agree with Anna about the bot. I don't want you all to take on a work
>>> load that will make you uncomfortable onsite.
>>>
>>> On Mon, Jan 9, 2017 at 6:15 PM, Anna Ossowski <ossanna16 at gmx.de> wrote:
>>>
>>>>
>>>> I support Trey?s idea of making more prominent on the website that the
>>>> Open Spaces are an event that takes place parallel to the talks and isn?t
>>>> an evening event like the PyLadies auction and the PyCon dinners for
>>>> example.
>>>> Adding a grid to the Open Spaces page, as well as moving the Open
>>>> Spaces page from the Events to the Schedule tab, are both great ideas.
>>>>
>>>
>>> I think this makes perfect sense and I can help with that. Once you have
>>> a grid up and it looks like a schedule, I can definitely move it over to
>>> the Schedule tab.
>>>
>>>
>>>
>>
>>
>> _______________________________________________
>> Pycon-openspaces mailing list
>> Pycon-openspaces at python.org
>> https://mail.python.org/mailman/listinfo/pycon-openspaces
>>
>>
>
>
> --
> Brandon Rhodes
> PyCon 2016 Conference Chair
> pycon.brandon at gmail.com
>
>
>
> _______________________________________________
> 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/20170116/4dbddd6f/attachment-0001.html>

From ossanna16 at gmx.de  Mon Jan 16 13:49:59 2017
From: ossanna16 at gmx.de (Anna Ossowski)
Date: Mon, 16 Jan 2017 19:49:59 +0100
Subject: [Pycon-openspaces] Open Spaces 2017 Kick Off!
In-Reply-To: <CACZ_DofKAccuvW4RyBkeCk82BBD-tu262NdZ9ysoq=UCd8Coeg@mail.gmail.com>
References: <5CF5E3BC-0F73-43CB-9A5C-4A275867E57B@gmx.de>
 <CADx+GQM400JLoMbRzvNDMqNYDCQP8-_c8FzgzYgvo-VPY3GRLA@mail.gmail.com>
 <43917198-829F-44D5-8E88-95F53D1BB78A@gmx.de>
 <1e6065we301jubp7zows9t244-0@mailer.nylas.com>
 <B259B330-A111-409C-B418-71D38D705683@gmx.de>
 <CADx+GQO8d=HfWgUg57ErTLJL4tD_0y-VbyZQSo-8BU43fYu1pw@mail.gmail.com>
 <8A6A5087-527E-443A-8D5F-E928E0EB1C45@gmx.de>
 <CADx+GQOCwSEe0idNBdp3cvDw2dw8A6rdoUupYtzKt_NXD3MEdw@mail.gmail.com>
 <A33800D7-EAB7-4BCD-8D33-9BB572565649@gmx.de>
 <CAD05_ovNrmA3t2Wpd2YN_S9UQUCO17ohHGXGB4NyO1aLXRLJWw@mail.gmail.com>
 <4813518C-9F4B-4527-8EBA-326A5C510423@gmx.de>
 <CACZ_DofKAccuvW4RyBkeCk82BBD-tu262NdZ9ysoq=UCd8Coeg@mail.gmail.com>
Message-ID: <A450DEA9-FCA3-4C4C-8229-8C24548E957B@gmx.de>

That sounds great, Hobson! ?
---------------------------------
You are appreciated.
You are enough.
You matter.
You are not alone.



> On Jan 16, 2017, at 7:34 PM, Hobson Lane <hobsonlane at gmail.com> wrote:
> 
> Hi Anna,
> 
> Good idea on the schedule summarizer. It's definitely straightforward for the twitter buffer to summarize several upcoming Open Spaces events with single tweet to reduce the tweet volume/rate. All tweets from the bot can include a link to its schedule of upcoming openspaces and an image of the latest Open Spaces poster.
> 
> --Hobson
> (503) 974-6274
> gh <https://github.com/hobson/> twtr <https://twitter.com/hobsonlane> li <https://www.linkedin.com/in/hobsonlane> g+ <http://plus.google.com/+HobsonLane/> so <http://stackoverflow.com/users/623735/hobs>
> On Mon, Jan 16, 2017 at 10:17 AM, Anna Ossowski <ossanna16 at gmx.de <mailto:ossanna16 at gmx.de>> wrote:
> Hello Brandon!
> 
> Thank you for your thoughtful reply! I?m glad you made it back home safely.
> I?m a little bit short on time at the moment but I wanted to reply right away so we can keep the conversation going. My apologies for my response being a little brief.
> 
> 
>> On Jan 16, 2017, at 1:51 AM, Brandon Rhodes <pycon.brandon at gmail.com <mailto:pycon.brandon at gmail.com>> wrote:
>> 
>> Good evening, everyone! I am finally caught up after my whirlwind of holiday travel, and am now happily ensconced at home for the winter where I can now keep abreast of things and watch the weather forecast for snowstorms.
>> 
>> In no particular order, here are some responses to all of the great ideas that you have generated on this thread over the past week:
>> I like the idea of having Guidebook make people aware of the Open Spaces! I am not exactly sure how that would fit into the app because I do not have enough experience of it to have a clear idea of how its navigation works, but I am happy that your committee will be looking into where Open Spaces will fit.
> Who is responsible for the PyCon US Guidebook; i.e. who should we reach out to about this?
> 
>> A blog post is a great idea! We should aim for fairly close to the conference, since Open Spaces can't be scheduled far in advance ? last year we did an April blog post, and that feels about right for this year as well.
> 
> That sounds good! Marked on my schedule to tackle this the beginning of April. Do you think we could reuse part of last year?s blog post since the information we want to present is mostly the same, or should we work on a completely new blog post?
>> I agree that the printed schedule this year should somehow, if room permits, show that the Open Spaces happen in parallel with the talks. When we design the brochure, we'll show you the result and let you know whether it wound up fitting. And using the printed schedule will, I agree, be a more feasible approach than trying to have the registration people deliver the information to people who are busy registering and probably wouldn't absorb it anyway.
> 
> That sounds good! Thank you!
>> Open Spaces can indeed continue during sprints; I have no problem with them overlapping.
> 
> ?
>> I agree that attendees need an introduction to the conference, and that the introduction should introduce Open Spaces! Last year I tried mentioning Open Spaces in my half-hour introduction to the conference, designed to let people know how to get the most out of it:
>> 
>> https://www.youtube.com/watch?v=ckW1xuGVpug <https://www.youtube.com/watch?v=ckW1xuGVpug>
>> 
>> Fast forward to about 19:00 for the segment on Open Spaces. For 2017, I hope to do something similar, because I think that a reminder of everything that goes on at the conference is good for everyone, not just the smaller self-selected audience we would get if we only gave this information at a for-beginners event.
>> 
>> Please let me know how the Open Spaces segment can be improved to provide more context and to better situate them in attendees' minds as things that go on at the same time as the main talks schedule.
> 
> I remember you mentioning the Open Spaces in your opening remarks last year and also in your morning remarks during the other two conference days (?), which was great! I added a note to our Trello board to discuss how we could potentially improve that segment.
>> I did wish last year that there was someone, or a group of volunteers instead of just one, who would tweet 15 minutes before every hour about what Open Spaces are happening. ?Coming up in 15 minutes, Open Spaces on: Astronomy; SciPy; Hardware; Diversity? or something like that, based on walking by the board and reading the cards. I am not sure whether subscribers wlil want to hear N tweets about the N events per hour, and I am not sure that organizers will want to have to issue a tweet about their event (do they all even have Twitter?) in addition to getting a card up on the board. But I am not going to insist on any particular approach; there are lots of ways that Twitter and the Open Spaces could interact, and as long as it doesn't involve lots of tweets from the main conference Twitter account, I'm happy to have y'all on the committee experiment with whatever idea interests you most.
> 
> I agree that this would indeed be awesome! However, I think this would be quite an effort to organize and coordinate to make it go smoothly. We would have to find a group of responsible volunteers who would be willing to do this in 2 or 3 hour shifts. Additionally we would have to make sure that all of them have access to either the PyCon (probably not the preferred way to do this) or a PyCon Open Spaces Twitter account. They could simply tweet from their personal Twitter accounts but then we?d be running into the ?What if they don?t have Twitter? problem again, and for announcements like these I think it might be best to tweet them from one account instead of just asking each volunteer to tweet from their personal account using our hashtag.
> 
> You definitely mention good points we?ll have to think about regarding the bot. If I was an organizer and I?d want for people to show up to my Open Space, I wouldn?t mind writing one tweet about it, but that may not be the case for everyone. Also I believe that a lot of people these days do have Twitter accounts but not all of them do. 
> I would still like to give the bot a try. We?d have to clarify that the bot won?t provide a full summary of all Open Spaces but is just functioning as a tool to help promote those Open Spaces more whose organizers tweet about it (then we are technically discriminating against people who don?t have Twitter but I don?t now how to solve the problem in this context.) Maybe we could somehow have the bot tweet out summaries of which Open Spaces are coming up instead of simple retweets in order to keep the amount of tweets the bot sends out relatively low? Any ideas, Hobson?
> 
> Neither of the two approaches are 100% ideal but the bot would at least offer some amount of ?official? promotion and definitely an improvement to last year. I guess it?s all a matter of trial and error. If we see that the bot isn?t as successful this year as we were hoping it would be, we can always try the more hands-on volunteer approach next year.
> 
>> I am not sure we should add a blank Open Spaces schedule to the Schedule drop-down on the site. (1) It would make organizers think they can sign up ahead of time, but they can't. (2) People would see it blank in the days before the conference and conclude that something was wrong, or that Open Spaces weren't really going to happen, because generally conferences only have schedule grids up because they have data to put in them.
>> 
>> I will, however, definitely plan to re-post my https://us.pycon.org/2016/events/ <https://us.pycon.org/2016/events/> ?Overview? page again this year as we release the schedule and, as you can see, it (probably similarly to what you were thinking about the printed brochure?) depicts the Open Spaces as happening simultaneously with the Talks.
> 
> Trey, you mentioned Open Source bridge providing an empty schedule on their website. Do you think you could comment on Brandon?s concerns regarding if Open Source bridge face any of these problems, etc.?
>> The problem with a Twitter hashtag is that people might think they're supposed to subscribe to it if they're interested in Open Spaces, but you can't control the amount of abuse that is delivered by people who figure that out, because Twitter doesn't let you control what's tweeted under a hashtag.
> 
> Agreed. 
> Hobson, do you have any ideas on how to prevent abuse as much as possible? Could we use something which is more reliable than a Twitter hashtag for filtering the tweets?
> 
>> There, I think that covers the main points that have been raised so far? Feel free to make further comments on any of these matters, and I'll try to respond with a much shorter ping time now that I'm home and back in the loop! Thanks again for all of your thoughtful work to make Open Spaces ever more awesome. :)
> 
> Thanks again Brandon! I always appreciate reading your input :)
> Anna
>> 
>> On Wed, Jan 11, 2017 at 10:58 AM, Anna Ossowski <ossanna16 at gmx.de <mailto:ossanna16 at gmx.de>> wrote:
>> Thank you, Ewa :)
>> 
>> ---------------------------------
>> You are appreciated.
>> You are enough.
>> You matter.
>> You are not alone.
>> 
>> 
>> 
>>> On Jan 11, 2017, at 4:27 PM, Ewa Jodlowska <ewa at python.org <mailto:ewa at python.org>> wrote:
>>> 
>>> I have given Trey edit privileges on CMS pages just in case that is needed.
>>> 
>>> Best regards,
>>> 
>>> Ewa
>>> Director of Operations
>>> Python Software Foundation
>>> Cell: 415-319-5237 <tel:(415)%20319-5237>
>>> On Tue, Jan 10, 2017 at 10:17 AM, Anna Ossowski <ossanna16 at gmx.de <mailto:ossanna16 at gmx.de>> wrote:
>>> Maybe there is a way to automate this as much as possible and keep monitoring of the bot at a minimum but still make sure we don?t get a bunch of spammy or CoC violating tweets. Would love to hear Hobson?s and Trey?s thoughts on this.
>>> 
>>> Trey, would you have time to help with the grid or could you let me know what the best way to do this is so I can create it myself?
>>> 
>>> Thank you!
>>> Anna
>>> 
>>> ---------------------------------
>>> You are appreciated.
>>> You are enough.
>>> You matter.
>>> You are not alone.
>>> 
>>> 
>>> 
>>>> On Jan 10, 2017, at 4:36 PM, Ewa Jodlowska <ewa at python.org <mailto:ewa at python.org>> wrote:
>>>> 
>>>> I agree with Anna about the bot. I don't want you all to take on a work load that will make you uncomfortable onsite.
>>>> 
>>>> On Mon, Jan 9, 2017 at 6:15 PM, Anna Ossowski <ossanna16 at gmx.de <mailto:ossanna16 at gmx.de>> wrote:
>>>> 
>>>> I support Trey?s idea of making more prominent on the website that the Open Spaces are an event that takes place parallel to the talks and isn?t an evening event like the PyLadies auction and the PyCon dinners for example.
>>>> Adding a grid to the Open Spaces page, as well as moving the Open Spaces page from the Events to the Schedule tab, are both great ideas.
>>>> 
>>>> I think this makes perfect sense and I can help with that. Once you have a grid up and it looks like a schedule, I can definitely move it over to the Schedule tab. 
>>> 
>>> 
>> 
>> 
>> _______________________________________________
>> 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>
>> 
>> 
>> 
>> 
>> -- 
>> Brandon Rhodes
>> PyCon 2016 Conference Chair
>> pycon.brandon at gmail.com <mailto:pycon.brandon at gmail.com>
> 
> _______________________________________________
> 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/20170116/c7f25b95/attachment-0001.html>

From ewa at python.org  Mon Jan 16 14:11:11 2017
From: ewa at python.org (Ewa Jodlowska)
Date: Mon, 16 Jan 2017 13:11:11 -0600
Subject: [Pycon-openspaces] Open Spaces 2017 Kick Off!
In-Reply-To: <4813518C-9F4B-4527-8EBA-326A5C510423@gmx.de>
References: <5CF5E3BC-0F73-43CB-9A5C-4A275867E57B@gmx.de>
 <CADx+GQM400JLoMbRzvNDMqNYDCQP8-_c8FzgzYgvo-VPY3GRLA@mail.gmail.com>
 <43917198-829F-44D5-8E88-95F53D1BB78A@gmx.de>
 <1e6065we301jubp7zows9t244-0@mailer.nylas.com>
 <B259B330-A111-409C-B418-71D38D705683@gmx.de>
 <CADx+GQO8d=HfWgUg57ErTLJL4tD_0y-VbyZQSo-8BU43fYu1pw@mail.gmail.com>
 <8A6A5087-527E-443A-8D5F-E928E0EB1C45@gmx.de>
 <CADx+GQOCwSEe0idNBdp3cvDw2dw8A6rdoUupYtzKt_NXD3MEdw@mail.gmail.com>
 <A33800D7-EAB7-4BCD-8D33-9BB572565649@gmx.de>
 <CAD05_ovNrmA3t2Wpd2YN_S9UQUCO17ohHGXGB4NyO1aLXRLJWw@mail.gmail.com>
 <4813518C-9F4B-4527-8EBA-326A5C510423@gmx.de>
Message-ID: <CADx+GQMs7B6=tevTu-snmVWZANZZRh7By9+mqGOa5FmGSo6BOA@mail.gmail.com>

On Mon, Jan 16, 2017 at 12:17 PM, Anna Ossowski <ossanna16 at gmx.de> wrote:

[clipped]

>
>    - Who is responsible for the PyCon US Guidebook; i.e. who should we
>    reach out to about this?
>
>
It is usually something I manage with the help of volunteers. You can email
any requests to the ML: pycon-mobile-guide at python.org. We will begin
working on it after all of the schedules are released.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pycon-openspaces/attachments/20170116/05f73e80/attachment.html>

From ossanna16 at gmx.de  Mon Jan 16 15:02:00 2017
From: ossanna16 at gmx.de (Anna Ossowski)
Date: Mon, 16 Jan 2017 21:02:00 +0100
Subject: [Pycon-openspaces] Open Spaces 2017 Kick Off!
In-Reply-To: <CADx+GQMs7B6=tevTu-snmVWZANZZRh7By9+mqGOa5FmGSo6BOA@mail.gmail.com>
References: <5CF5E3BC-0F73-43CB-9A5C-4A275867E57B@gmx.de>
 <CADx+GQM400JLoMbRzvNDMqNYDCQP8-_c8FzgzYgvo-VPY3GRLA@mail.gmail.com>
 <43917198-829F-44D5-8E88-95F53D1BB78A@gmx.de>
 <1e6065we301jubp7zows9t244-0@mailer.nylas.com>
 <B259B330-A111-409C-B418-71D38D705683@gmx.de>
 <CADx+GQO8d=HfWgUg57ErTLJL4tD_0y-VbyZQSo-8BU43fYu1pw@mail.gmail.com>
 <8A6A5087-527E-443A-8D5F-E928E0EB1C45@gmx.de>
 <CADx+GQOCwSEe0idNBdp3cvDw2dw8A6rdoUupYtzKt_NXD3MEdw@mail.gmail.com>
 <A33800D7-EAB7-4BCD-8D33-9BB572565649@gmx.de>
 <CAD05_ovNrmA3t2Wpd2YN_S9UQUCO17ohHGXGB4NyO1aLXRLJWw@mail.gmail.com>
 <4813518C-9F4B-4527-8EBA-326A5C510423@gmx.de>
 <CADx+GQMs7B6=tevTu-snmVWZANZZRh7By9+mqGOa5FmGSo6BOA@mail.gmail.com>
Message-ID: <3B2F0989-EE22-4ADC-90D9-FD78F2BBDD8A@gmx.de>

Thank you, Ewa! :)
---------------------------------
You are appreciated.
You are enough.
You matter.
You are not alone.



> On Jan 16, 2017, at 8:11 PM, Ewa Jodlowska <ewa at python.org> wrote:
> 
> On Mon, Jan 16, 2017 at 12:17 PM, Anna Ossowski <ossanna16 at gmx.de <mailto:ossanna16 at gmx.de>> wrote:
> 
> [clipped] 
>> Who is responsible for the PyCon US Guidebook; i.e. who should we reach out to about this?
> 
> 
> It is usually something I manage with the help of volunteers. You can email any requests to the ML: pycon-mobile-guide at python.org <mailto:pycon-mobile-guide at python.org>. We will begin working on it after all of the schedules are released.  

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pycon-openspaces/attachments/20170116/32fde189/attachment.html>

From chelseakaye89 at gmail.com  Sat Jan 21 13:22:17 2017
From: chelseakaye89 at gmail.com (Chelsea Emery)
Date: Sat, 21 Jan 2017 13:22:17 -0500
Subject: [Pycon-openspaces] Adding to PyCon Website
Message-ID: <CAAfMDzbP64AkTKptZUhiL9HLJb1kfi6Y+_OQVsu5tAEZoY1CUA@mail.gmail.com>

Hey there,

I want to add an open space to the list on the Open Spaces page for PyCon
2017. Am I missing where to edit the page?

Thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pycon-openspaces/attachments/20170121/2027183a/attachment.html>

From ossanna16 at gmx.de  Sun Jan 22 07:37:36 2017
From: ossanna16 at gmx.de (Anna Ossowski)
Date: Sun, 22 Jan 2017 13:37:36 +0100
Subject: [Pycon-openspaces] Adding to PyCon Website
In-Reply-To: <CAAfMDzbP64AkTKptZUhiL9HLJb1kfi6Y+_OQVsu5tAEZoY1CUA@mail.gmail.com>
References: <CAAfMDzbP64AkTKptZUhiL9HLJb1kfi6Y+_OQVsu5tAEZoY1CUA@mail.gmail.com>
Message-ID: <069080D3-2D14-4FF2-A73F-D26156D9320D@gmx.de>

Hey Chelsea!

Could you please let me know the topic and a potential date and time for your Open Space? I will add it to the list for you :)

Thank you!
Anna

---------------------------------
You are appreciated.
You are enough.
You matter.
You are not alone.



> On Jan 21, 2017, at 7:22 PM, Chelsea Emery <chelseakaye89 at gmail.com> wrote:
> 
> Hey there,
> 
> I want to add an open space to the list on the Open Spaces page for PyCon 2017. Am I missing where to edit the page?
> 
> Thanks!
> 
> _______________________________________________
> Pycon-openspaces mailing list
> Pycon-openspaces at python.org
> https://mail.python.org/mailman/listinfo/pycon-openspaces


From helenopetunde at gmail.com  Mon Jan 23 17:08:35 2017
From: helenopetunde at gmail.com (Opetunde Adepoju)
Date: Mon, 23 Jan 2017 23:08:35 +0100
Subject: [Pycon-openspaces] Proposition to talk at the open space.
In-Reply-To: <CAKrQeeVSzBGuNF4JcBoVs+HD+d5enbnEoRh0XG+s_eJCM2R+jQ@mail.gmail.com>
References: <CAKrQeeUnLDo3aGiGCM=uXe=8x2waQUYGMizxSEe4Cif585nhwQ@mail.gmail.com>
 <CAKrQeeVSzBGuNF4JcBoVs+HD+d5enbnEoRh0XG+s_eJCM2R+jQ@mail.gmail.com>
Message-ID: <CAKrQeeVaciJJwiC13Z9uZKBY+bVr46=13-5-NjYh7oMzO3Hjrg@mail.gmail.com>

Hello there,

I hope this meets you well. I am an organiser of Django Girls
Ogbomoso/Accra and a data scientist. I would like a slot to speak about
Artificial intelligence and how it affects Africa and other developing
worlds.

I hope I am given the privilege to speak at the open space. Thank you
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pycon-openspaces/attachments/20170123/1915ac70/attachment.html>

From ossanna16 at gmx.de  Tue Jan 24 01:04:50 2017
From: ossanna16 at gmx.de (Anna Ossowski)
Date: Tue, 24 Jan 2017 07:04:50 +0100
Subject: [Pycon-openspaces] Proposition to talk at the open space.
In-Reply-To: <CAKrQeeVaciJJwiC13Z9uZKBY+bVr46=13-5-NjYh7oMzO3Hjrg@mail.gmail.com>
References: <CAKrQeeUnLDo3aGiGCM=uXe=8x2waQUYGMizxSEe4Cif585nhwQ@mail.gmail.com>
 <CAKrQeeVSzBGuNF4JcBoVs+HD+d5enbnEoRh0XG+s_eJCM2R+jQ@mail.gmail.com>
 <CAKrQeeVaciJJwiC13Z9uZKBY+bVr46=13-5-NjYh7oMzO3Hjrg@mail.gmail.com>
Message-ID: <2E53A444-0CE3-4BC3-909C-9F5CF4C8956C@gmx.de>

Hi Opetunde!

Thank you for your email! So awesome to hear that you are a Django Girls organizer. I have organized a couple of Django Girls events myself :)

I am happy to add your Open Space to the website so that people know this is one of the Open Spaces you plan to host. Do you have an idea for a time and day you would like to host this Open Space during PyCon?

Everyone can host an Open Space at PyCon and your idea is great! Please keep in mind that an Open Space is not a traditional way of giving a talk. The idea behind Open Spaces is to get people together who are interested in the same topic and to further the discussion around this topic and learn from each other.

Please also note that by adding your idea to the website, you are not officially signed up for an Open Space, you will still have to fill out an Open Spaces card and add it to the Open Spaces board onsite at PyCon.

Thank you!
Anna


---------------------------------
You are appreciated.
You are enough.
You matter.
You are not alone.



> On Jan 23, 2017, at 11:08 PM, Opetunde Adepoju <helenopetunde at gmail.com> wrote:
> 
> Hello there,
> 
> I hope this meets you well. I am an organiser of Django Girls Ogbomoso/Accra and a data scientist. I would like a slot to speak about Artificial intelligence and how it affects Africa and other developing worlds.
> 
> I hope I am given the privilege to speak at the open space. Thank you
> 
> _______________________________________________
> 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/20170124/1a17f921/attachment.html>

From ossanna16 at gmx.de  Tue Jan 24 05:49:41 2017
From: ossanna16 at gmx.de (Anna Ossowski)
Date: Tue, 24 Jan 2017 11:49:41 +0100
Subject: [Pycon-openspaces] Proposition to talk at the open space.
In-Reply-To: <CAKrQeeUKy1Sx7vB0khswO1oggd8yJ+31zmV2+9QRr7GgUm2JBg@mail.gmail.com>
References: <CAKrQeeUnLDo3aGiGCM=uXe=8x2waQUYGMizxSEe4Cif585nhwQ@mail.gmail.com>
 <CAKrQeeVSzBGuNF4JcBoVs+HD+d5enbnEoRh0XG+s_eJCM2R+jQ@mail.gmail.com>
 <CAKrQeeVaciJJwiC13Z9uZKBY+bVr46=13-5-NjYh7oMzO3Hjrg@mail.gmail.com>
 <2E53A444-0CE3-4BC3-909C-9F5CF4C8956C@gmx.de>
 <CAKrQeeUKy1Sx7vB0khswO1oggd8yJ+31zmV2+9QRr7GgUm2JBg@mail.gmail.com>
Message-ID: <EE863814-F0A7-49BE-9407-CD005D97C1B2@gmx.de>

Hey Opetunde!

I added your Open Space idea to the website.

We are not involved with financial aid decisions but I?m keeping my fingers crossed for you and hope to see you at PyCon :)

All the best to you,
Anna

---------------------------------
You are appreciated.
You are enough.
You matter.
You are not alone.



> On Jan 24, 2017, at 8:19 AM, Opetunde Adepoju <helenopetunde at gmail.com> wrote:
> 
> Hello Anna,
> 
> Thank you for your awesomeness. I would prefer to speak on the second day of the PyCon.
> 
> I would also require financial assistance because I am an undergraduate student who cannot afford the ticket, flight and accommodation fees. I would gladly appreciate it if any help is given so that I can be available to fill the Open space card. I have requested for financial assistance and I hope to be given.
> 
> Thank you
> 
> Hugs and cupcakes
> 
> 
> On Jan 24, 2017 7:04 AM, "Anna Ossowski" <ossanna16 at gmx.de <mailto:ossanna16 at gmx.de>> wrote:
> Hi Opetunde!
> 
> Thank you for your email! So awesome to hear that you are a Django Girls organizer. I have organized a couple of Django Girls events myself :)
> 
> I am happy to add your Open Space to the website so that people know this is one of the Open Spaces you plan to host. Do you have an idea for a time and day you would like to host this Open Space during PyCon?
> 
> Everyone can host an Open Space at PyCon and your idea is great! Please keep in mind that an Open Space is not a traditional way of giving a talk. The idea behind Open Spaces is to get people together who are interested in the same topic and to further the discussion around this topic and learn from each other.
> 
> Please also note that by adding your idea to the website, you are not officially signed up for an Open Space, you will still have to fill out an Open Spaces card and add it to the Open Spaces board onsite at PyCon.
> 
> Thank you!
> Anna
> 
> 
> ---------------------------------
> You are appreciated.
> You are enough.
> You matter.
> You are not alone.
> 
> 
> 
>> On Jan 23, 2017, at 11:08 PM, Opetunde Adepoju <helenopetunde at gmail.com <mailto:helenopetunde at gmail.com>> wrote:
>> 
>> Hello there,
>> 
>> I hope this meets you well. I am an organiser of Django Girls Ogbomoso/Accra and a data scientist. I would like a slot to speak about Artificial intelligence and how it affects Africa and other developing worlds.
>> 
>> I hope I am given the privilege to speak at the open space. Thank you
>> 
>> _______________________________________________
>> 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/20170124/2110dfd2/attachment.html>

From ossanna16 at gmx.de  Tue Jan 24 21:53:24 2017
From: ossanna16 at gmx.de (Anna Ossowski)
Date: Wed, 25 Jan 2017 03:53:24 +0100
Subject: [Pycon-openspaces] Adding to PyCon Website
In-Reply-To: <CAAfMDzaDyDySmwUx3A3NpxKzYqxnPbQJgDPAOzXpc8b717YtcA@mail.gmail.com>
References: <CAAfMDzbP64AkTKptZUhiL9HLJb1kfi6Y+_OQVsu5tAEZoY1CUA@mail.gmail.com>
 <069080D3-2D14-4FF2-A73F-D26156D9320D@gmx.de>
 <CAAfMDzaDyDySmwUx3A3NpxKzYqxnPbQJgDPAOzXpc8b717YtcA@mail.gmail.com>
Message-ID: <F74E4717-F59F-4DE8-8480-776AF8F9FE47@gmx.de>

Hey Chelsea!

Ah, the famous AcroYoga Open Space, it?s always a big hit at PyCon. Thank you so much to you and your partner for running it every year. It?s now up on the website.

Please let me know if I can do anything else for you.

Thank you!
Anna

---------------------------------
You are appreciated.
You are enough.
You matter.
You are not alone.



> On Jan 24, 2017, at 4:54 PM, Chelsea Emery <chelseakaye89 at gmail.com> wrote:
> 
> Hey there, Anna - 
> 
> The open space my partner and I run is: import antigravity (AcroYoga)
> 
> We typically run it the evening of the first day of talks but I can't commit to that time without the schedule. So if you can just list it, that will be good. Thanks!
> 
> 
> On Sun, Jan 22, 2017 at 7:37 AM, Anna Ossowski <ossanna16 at gmx.de <mailto:ossanna16 at gmx.de>> wrote:
> Hey Chelsea!
> 
> Could you please let me know the topic and a potential date and time for your Open Space? I will add it to the list for you :)
> 
> Thank you!
> Anna
> 
> ---------------------------------
> You are appreciated.
> You are enough.
> You matter.
> You are not alone.
> 
> 
> 
> > On Jan 21, 2017, at 7:22 PM, Chelsea Emery <chelseakaye89 at gmail.com <mailto:chelseakaye89 at gmail.com>> wrote:
> >
> > Hey there,
> >
> > I want to add an open space to the list on the Open Spaces page for PyCon 2017. Am I missing where to edit the page?
> >
> > Thanks!
> >
> > _______________________________________________
> > 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/20170125/8702466a/attachment.html>