<p dir="ltr">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.</p>
<br><div class="gmail_quote"><div dir="ltr">On Sat, Jan 7, 2017, 3:58 PM Trey Hunner <trey@truthful.technology> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_quote m_5896832455565697055nylas-quote m_5896832455565697055nylas-quote-id-92xlvqjbazgd3nck8xbopa7n2 gmail_msg"><div class="gmail_msg">Hi all!</div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">Thanks for the welcome Brandon. Nice to meet you Hobson. Ewa, I just requested to join the pycon-staff list. Thanks for the reminder!</div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">I replied inline below.</div></div><div class="gmail_quote m_5896832455565697055nylas-quote m_5896832455565697055nylas-quote-id-92xlvqjbazgd3nck8xbopa7n2 gmail_msg"><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">On Jan 6 2017, at 5:33 pm, Anna Ossowski <<a href="mailto:ossanna16@gmx.de" class="gmail_msg" target="_blank">ossanna16@gmx.de</a>> wrote: <br class="gmail_msg"></div>
<blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="gmail_msg"><div class="gmail_msg"><br class="gmail_msg"></div></div><div class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg">On Jan 6, 2017, at 3:46 PM, Ewa Jodlowska <<a href="mailto:ewa@python.org" class="gmail_msg" target="_blank">ewa@python.org</a>> wrote:</div><br class="gmail_msg"><div class="gmail_msg"><div dir="ltr" class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div dir="ltr" class="gmail_msg"><div dir="ltr" class="gmail_msg">On Thu, Jan 5, 2017 at 9:32 PM, Anna Ossowski <span dir="ltr" class="gmail_msg"><<a href="mailto:ossanna16@gmx.de" class="gmail_msg" target="_blank">ossanna16@gmx.de</a>></span> wrote:<br class="gmail_msg"></div></div></div></div><div class="gmail_msg"><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">[clipped] </div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_msg">
<br class="gmail_msg">
* 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.<br class="gmail_msg"></blockquote><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">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. </div></div></div></div></div></blockquote><div class="gmail_msg"><br class="gmail_msg"></div>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?</div></blockquote><div class="gmail_quote m_5896832455565697055nylas-quote m_5896832455565697055nylas-quote-id-92xlvqjbazgd3nck8xbopa7n2 gmail_msg"><br class="gmail_msg"></div></div><div class="gmail_quote m_5896832455565697055nylas-quote m_5896832455565697055nylas-quote-id-92xlvqjbazgd3nck8xbopa7n2 gmail_msg"><div class="gmail_quote m_5896832455565697055nylas-quote m_5896832455565697055nylas-quote-id-92xlvqjbazgd3nck8xbopa7n2 gmail_msg">Two ideas I had that differ from what we had last year:</div><div class="gmail_quote m_5896832455565697055nylas-quote m_5896832455565697055nylas-quote-id-92xlvqjbazgd3nck8xbopa7n2 gmail_msg"><br class="gmail_msg"></div><div class="gmail_quote m_5896832455565697055nylas-quote m_5896832455565697055nylas-quote-id-92xlvqjbazgd3nck8xbopa7n2 gmail_msg"><ul class="gmail_msg"><li class="gmail_msg">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.</li><li class="gmail_msg">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.</li></ul><br class="gmail_msg"></div></div><div class="gmail_quote m_5896832455565697055nylas-quote m_5896832455565697055nylas-quote-id-92xlvqjbazgd3nck8xbopa7n2 gmail_msg"><div class="gmail_quote m_5896832455565697055nylas-quote m_5896832455565697055nylas-quote-id-92xlvqjbazgd3nck8xbopa7n2 gmail_msg"><br class="gmail_msg"></div><blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg"><div dir="ltr" class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_msg">
* 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.<br class="gmail_msg">
<br class="gmail_msg">
* 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.<br class="gmail_msg">
<br class="gmail_msg">
<br class="gmail_msg">
Ideas/To Discuss:<br class="gmail_msg">
<br class="gmail_msg"><br class="gmail_msg"></blockquote><div class="gmail_msg">[clipped] </div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_msg">
<br class="gmail_msg">
* 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.<br class="gmail_msg"></blockquote><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">I'm going to chime in on two points and leave the rest to Brandon. </div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">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:<br class="gmail_msg"></div></div></div></div></div></blockquote><div class="gmail_msg"><br class="gmail_msg"></div>Agreed!<br class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg"><div dir="ltr" class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><ol class="gmail_msg"><li class="gmail_msg">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.<br class="gmail_msg"></li><li class="gmail_msg">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.</li></ol><div class="gmail_msg">Personally, I think adding it to the printed schedule and to the Guidebook is the best way forward. </div></div></div></div></div></div></blockquote><div class="gmail_msg"><br class="gmail_msg"></div>Good points! I agree that adding an FYI section to the printed schedule and Guidebook would work best.</div></blockquote><div class="gmail_quote m_5896832455565697055nylas-quote m_5896832455565697055nylas-quote-id-92xlvqjbazgd3nck8xbopa7n2 gmail_msg"><br class="gmail_msg"></div></div><div class="gmail_quote m_5896832455565697055nylas-quote m_5896832455565697055nylas-quote-id-92xlvqjbazgd3nck8xbopa7n2 gmail_msg">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)?</div><div class="gmail_quote m_5896832455565697055nylas-quote m_5896832455565697055nylas-quote-id-92xlvqjbazgd3nck8xbopa7n2 gmail_msg"><br class="gmail_msg"><br class="gmail_msg"><br class="gmail_msg"><br class="gmail_msg"><blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg"><div dir="ltr" class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_msg">
* 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.<br class="gmail_msg"></blockquote><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">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.</div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">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.</div></div></div></div>
</div></blockquote><br class="gmail_msg"></div><div class="gmail_msg">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?</div></blockquote><br class="gmail_msg">
</div><div class="gmail_quote m_5896832455565697055nylas-quote m_5896832455565697055nylas-quote-id-92xlvqjbazgd3nck8xbopa7n2 gmail_msg"></div><div class="gmail_quote m_5896832455565697055nylas-quote m_5896832455565697055nylas-quote-id-92xlvqjbazgd3nck8xbopa7n2 gmail_msg">Yeah. Maybe this is a conversation maybe we could coordinate with the sprint board coordinators?</div><div id="m_5896832455565697055n1-quoted-text-marker" class="gmail_msg"></div>_______________________________________________<br class="gmail_msg">
Pycon-openspaces mailing list<br class="gmail_msg">
<a href="mailto:Pycon-openspaces@python.org" class="gmail_msg" target="_blank">Pycon-openspaces@python.org</a><br class="gmail_msg">
<a href="https://mail.python.org/mailman/listinfo/pycon-openspaces" rel="noreferrer" class="gmail_msg" target="_blank">https://mail.python.org/mailman/listinfo/pycon-openspaces</a><br class="gmail_msg">
</blockquote></div>