[Pycon-openspaces] Open spaces blog post

[Anna Ossowski]

Thank you, Zak!

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



> On Apr 20, 2018, at 4:23 PM, Zak <zak.kent at gmail.com> wrote:
> 
> Hi everyone, 
> 
> If it helps I could take a crack at writing a first draft this weekend. Hobs has been helping me a bunch with getting the bot deployed on a new server. I don’t mind taking this on to help free up some time elsewhere.
> 
> On Fri, Apr 20, 2018 at 6:59 AM Anna Ossowski <annabell.ossowski at gmail.com <mailto:annabell.ossowski at gmail.com>> wrote:
> Hi Hobson,
> 
> I would recommend writing the first draft and then running it by the rest of the team for edits and suggestions. I worked with Brandon Rhodes in order to get it up on the blog. I assume Ernest or Ewa will be able to help with this.
> 
> I believe Trey isn’t working on the post as of right now so if you have some time to write the first draft, that would be helpful.
> 
> Thank you!
> Anna
> 
> ——
> You are appreciated.
> You are enough.
> You matter.
> You are not alone.
> 
> 
> 
>> On Apr 20, 2018, at 11:39 AM, Hobson Lane <hobsonlane at gmail.com <mailto:hobsonlane at gmail.com>> wrote:
>> 
>> Hi Anna thank you for the reminder. Sorry for the delay in replying. What is the procedure for composing a blog post? Is trey working on this?
>> 
>> On Wed, Apr 11, 2018, 8:09 AM Anna Ossowski <annabell.ossowski at gmail.com <mailto:annabell.ossowski at gmail.com>> wrote:
>> Hi Trey,
>> 
>> I like the idea of writing a longer blog post including all the great notes Zak put together. I would recommend writing one longer post, maybe with a short Open Spaces overview in the beginning and then going more into detail on how to run a good Open Space and how to get the most out of participating. This way everything is in one place and people can decide what information is relevant to them individually.
>> 
>> Thank you!
>> Anna
>> 
>> ——
>> You are appreciated.
>> You are enough.
>> You matter.
>> You are not alone.
>> 
>> 
>> 
>>> On Apr 11, 2018, at 4:38 PM, Trey Hunner <trey at truthful.technology <mailto:trey at truthful.technology>> wrote:
>>> 
>>> Hey Anna,
>>> 
>>> Do you think we should keep the open spaces blog post short like you did last year <https://pycon.blogspot.com/2017/05/dont-overlook-open-spaces-at-pycon-this.html>?
>>> 
>>> Or do you think we should include a more detailed explanation on how to run a good open space (like the document Zak started <https://docs.google.com/document/d/1scTO9mNxNk2vXbK-_yubvPLH51DCM97u4Jag4HL4-eM/edit?usp=sharing>) or how to get the most out of participating? Should those be on separate pages or in separate posts instead?
>>> 
>>> On Mon, Apr 9, 2018 at 9:09 AM, Anna Ossowski <annabell.ossowski at gmail.com <mailto:annabell.ossowski at gmail.com>> wrote:
>>> Hi all,
>>> 
>>> PyCon is less than a month away (how exciting!) and I wanted to bring up the idea to write a blog post about the Open spaces again. This has worked well in the past 2 years. I suggest publishing it about 10-14 days before PyCon.
>>> I am happy to review or help in other ways.
>>> 
>>> Thank you!
>>> Anna
>>> 
>>> ——
>>> You are appreciated.
>>> You are enough.
>>> You matter.
>>> You are not alone.
>>> 
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> Pycon-openspaces mailing list
>>> Pycon-openspaces at python.org <mailto:Pycon-openspaces at python.org>
>>> https://mail.python.org/mailman/listinfo/pycon-openspaces <https://mail.python.org/mailman/listinfo/pycon-openspaces>
>>> 
>>> 
>>> 
>>> 
>>> -- 
>>> Trey Hunner
>>> Truthful Technology, LLC
>>> http://truthful.technology <http://truthful.technology/>
>> _______________________________________________
>> Pycon-openspaces mailing list
>> Pycon-openspaces at python.org <mailto:Pycon-openspaces at python.org>
>> https://mail.python.org/mailman/listinfo/pycon-openspaces <https://mail.python.org/mailman/listinfo/pycon-openspaces>
> 
> _______________________________________________
> 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/20180420/a1188a08/attachment-0001.html>