[Pycon-openspaces] Open Spaces 2017 Kick Off!
Hobson Lane
hobsonlane at gmail.com
Mon Jan 16 13:34:22 EST 2017
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>
More information about the Pycon-openspaces
mailing list