[Pycon-openspaces] Open Spaces Update

[Brandon Rhodes]

I am not sure you should try to avoid sending your email to people whose
talks were rejected.

First, we don’t know whether the topic of their talk had anything to do
with the Open Space — if they got a rejection note for their talk on
“Python Iterators” and saw the note about the possibility of doing an Open
Space, that would not necessarily have inspired them to make CherryPy — the
technology *you* are thinking of them as an expert and leader in — the
topic of an Open Space.

Second, an email from you, the actual Open Spaces people, asking whether
they are planning to host a CherryPy Open Space, is going to be so much
more personal and inspiring than a little addendum to a talk rejection!

Thirdly, think of the small team of core CherryPy people. Some get Open
Spaces invitations. Others do not. They eventually get curious and compare
notes about this. It turns out, they realize, that if you have had a talk
rejected, then you are blackballed by the PyCon leadership from receiving
any further invitations sent to you about contributing to the conference.
It could make people feel bad.

Finally, I’d like to preserve the feeling people have that their rejection
is private between them and the Talks committee, and not being shared with
other committees.

So I’d say, go ahead and plan an email, without worrying about whether they
had talks rejected. If you worry that your language might sound
inappropriate to someone who received an earlier rejection notice, then
feel free to post the text here in this thread first, and the rest of us
can let you know if there are any awkward phrasings you might improve.
Thanks!

On Sat, Mar 19, 2016 at 5:18 PM, Anna Ossowski <ossanna16 at gmx.de> wrote:

> Good question!
>
> Brandon or Ewa, could you please help/advise with this?
> -----
> https://calendly.com/ossanna16/
>
>
>
> Am 19.03.2016 um 22:12 schrieb Hobson Lane <hobsonlane at gmail.com>:
>
> Is it possible to get a list of the email addresses of folks who've
> already been informed of open spaces (paper rejections and acceptances)? I
> can make sure the open spaces mailing list doesn't include those e-mails.
>
> --Hobson
>
> --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 Fri, Mar 18, 2016 at 7:04 AM, Anna Ossowski <ossanna16 at gmx.de> wrote:
>
>> Hello Ewa,
>>
>> Thank you for your prompt response :) I can see the edit button.
>>
>> (And noted ;))
>>
>> Thanks so much and have a great Friday and weekend!
>> Anna
>>
>> Am 18.03.2016 um 14:57 schrieb Ewa Jodlowska <ewa at python.org>:
>>
>> Hi Anna -
>>
>> I have made you a page editor but our django permissions are not 100%
>> functional. Can you try now to see if you see an edit button on the page?
>>
>> (FYI - I am on this mailing list and do not need to be cc'ed :))
>>
>> Best regards,
>>
>> Ewa
>> Director of Operations
>> Python Software Foundation
>> Cell: 415-319-5237
>>
>> On Fri, Mar 18, 2016 at 8:54 AM, Anna Ossowski <ossanna16 at gmx.de> wrote:
>>
>>> Thank you so much Brandon! I’m glad Open Spaces were mentioned in
>>> rejection emails :)
>>>
>>> Have a good Friday!
>>> Anna
>>>
>>> Am 18.03.2016 um 14:52 schrieb Brandon Rhodes <pycon.brandon at gmail.com>:
>>>
>>> On Tue, Mar 15, 2016 at 7:30 AM, Anna Ossowski <ossanna16 at gmx.de> wrote:
>>>
>>>> Good morning Kinga, Hobson, and Brandon!
>>>>
>>>
>>> Good morning! :)
>>>
>>>
>>>> Brandon, we had discussed reaching out to everyone whose talk or
>>>> tutorial didn’t get accepted and to encourage them to host an open space on
>>>> that topic instead. Do you think this is a good idea or not? It would
>>>> surely involve a lot of emails so I was wondering if you had a better idea
>>>> :)
>>>>
>>>
>>> That has already happened, I think — in general, when a committee sends
>>> a rejection, or at least when they follow up with someone who asks about
>>> their rejected proposal, we always mention Open Spaces, Lightning Talks,
>>> and Tutorials as other ways to share with PyCon attendees. I am working to
>>> make that message more consistent each year, and to make sure
>>> communications always include those options.
>>>
>>> I was particularly careful this year to mention these consistently as
>>> sponsors and open source projects asked about involvement.
>>>
>>> So, I think that you can consider those audiences informed, without
>>> needing a further email spree.
>>>
>>>
>>>> Brandon, I would also like to edit the open spaces page on the PyCon
>>>> website. How do I do that?
>>>
>>>
>>> I'm not sure. I have some hours tomorrow dedicated to web site work, so
>>> I'll slate it for then! (Unless Ewa knows off the top of her head? I'll Cc
>>> her on this email.)
>>>
>>> --
>>> 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
>>
>>
>
>
> _______________________________________________
> 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/20160321/c0fcfc48/attachment.html>