Open Spaces blog post
Hello everyone! I had it on my calendar for today to take a final look at the Open Spaces blog post. The blog post is almost good to go, we just need to add a sentence or two about the Open Spaces bot and explain the promotional aspect of using our hashtag. The blog post is here https://docs.google.com/document/d/1ZvEyX-xH6VccLpL5TK_EcWt5me0Y6tlMP4QOwLfb... <https://docs.google.com/document/d/1ZvEyX-xH6VccLpL5TK_EcWt5me0Y6tlMP4QOwLfb...> Hobson and Trey, would one of you be able to add the part that is missing to the blog post and then give Brandon the final go once you’ve done so please? Hobson gave me instructions on how to test the Open Spaces bot but I have been busy with conferences and work and I am going on a much needed work-free (that also includes volunteer work) vacation on Wednesday for a week so I actually won’t have time to test the bot before I leave. I was planning on having time to test the bot today or tomorrow but I had something come up at work and I actually have to put my job before my volunteer work this time, which is something that I rarely do and which I feel bad about. I trust Hobson that the bot works. If however one of you still would like to test the bot, please reach out to Hobson for instructions. Thank you all for your help in making the Open Spaces awesome again this year! Anna --------------------------------- You are appreciated. You are enough. You matter. You are not alone.
Thank you Anna, Zak, since you built the bot, would you mind working with Trey to put together a sentence explaining how it works? The key is to make it clear that the twitter bot interaction is entirely optional, "just for fun". It's a way for someone to promote their Open Spaces event. This blog post that you are writing the sentence for with trey is for the public, so they will only interact with the bot through tweets with the hashtag #pyconopenspaces. In addition, Open Spaces organizers (like myself) can tweet on behalf of any events in order to help the bot promote an event that we see on the scheduling poster boards. The poster boards are where PyCon attendees put up cards to schedule/suggest an open spaces meetup. Trey, the bot simply extracts date, time and room number from any tweets that contain #pyconopenspaces . If the tweet looks like someone promoting a valid open spaces event time slot that no one else has yet "claimed" with the bot, the bot will retweet the tweet 15 minutes before the event. It, of course, can't verify that that event exists on the scheduling poster boards, however. Organizers, like you and I and Anna will have access to the twitter bot's schedule and can delete any tweets that are inappropriate or have the bot ignore (blacklist) any accounts that are spamming that hashtag. And we'll have some pretty robust spam filters in place. It may not retweet all the legitimate openspaces tweets, but it will be highly unlikely to embarrass us. And it will not be tweeting from an official pycon account. We can set that account to whatever you and Anna would like. The current test account is @tw_testy . That's where the promotional tweets will come from, not a name attendees need to remember or tweet to. --Hobson (503) 974-6274 On Mon, Apr 24, 2017 at 5:12 PM, Anna Ossowski <ossanna16@gmx.de> wrote:
Hello everyone!
I had it on my calendar for today to take a final look at the Open Spaces blog post. The blog post is almost good to go, we just need to add a sentence or two about the Open Spaces bot and explain the promotional aspect of using our hashtag. The blog post is here https://docs.google.com/document/d/1ZvEyX-xH6VccLpL5TK_ EcWt5me0Y6tlMP4QOwLfbLVM/edit#heading=h.55czulx95ir4
Hobson and Trey, would one of you be able to add the part that is missing to the blog post and then give Brandon the final go once you’ve done so please?
Hobson gave me instructions on how to test the Open Spaces bot but I have been busy with conferences and work and I am going on a much needed work-free (that also includes volunteer work) vacation on Wednesday for a week so I actually won’t have time to test the bot before I leave. I was planning on having time to test the bot today or tomorrow but I had something come up at work and I actually have to put my job before my volunteer work this time, which is something that I rarely do and which I feel bad about. I trust Hobson that the bot works. If however one of you still would like to test the bot, please reach out to Hobson for instructions.
Thank you all for your help in making the Open Spaces awesome again this year! Anna
--------------------------------- You are appreciated. You are enough. You matter. You are not alone.
_______________________________________________ Pycon-openspaces mailing list Pycon-openspaces@python.org https://mail.python.org/mailman/listinfo/pycon-openspaces
Hobson, this all sounds great! For the name maybe something like @openspaces_bot if it’s still available? Thank you all for your hard work! Anna --------------------------------- You are appreciated. You are enough. You matter. You are not alone.
On Apr 25, 2017, at 11:19 AM, Hobson Lane <hobsonlane@gmail.com> wrote:
Thank you Anna,
Zak, since you built the bot, would you mind working with Trey to put together a sentence explaining how it works? The key is to make it clear that the twitter bot interaction is entirely optional, "just for fun". It's a way for someone to promote their Open Spaces event. This blog post that you are writing the sentence for with trey is for the public, so they will only interact with the bot through tweets with the hashtag #pyconopenspaces. In addition, Open Spaces organizers (like myself) can tweet on behalf of any events in order to help the bot promote an event that we see on the scheduling poster boards. The poster boards are where PyCon attendees put up cards to schedule/suggest an open spaces meetup.
Trey, the bot simply extracts date, time and room number from any tweets that contain #pyconopenspaces . If the tweet looks like someone promoting a valid open spaces event time slot that no one else has yet "claimed" with the bot, the bot will retweet the tweet 15 minutes before the event. It, of course, can't verify that that event exists on the scheduling poster boards, however. Organizers, like you and I and Anna will have access to the twitter bot's schedule and can delete any tweets that are inappropriate or have the bot ignore (blacklist) any accounts that are spamming that hashtag. And we'll have some pretty robust spam filters in place. It may not retweet all the legitimate openspaces tweets, but it will be highly unlikely to embarrass us. And it will not be tweeting from an official pycon account. We can set that account to whatever you and Anna would like. The current test account is @tw_testy . That's where the promotional tweets will come from, not a name attendees need to remember or tweet to.
--Hobson (503) 974-6274
On Mon, Apr 24, 2017 at 5:12 PM, Anna Ossowski <ossanna16@gmx.de <mailto:ossanna16@gmx.de>> wrote: Hello everyone!
I had it on my calendar for today to take a final look at the Open Spaces blog post. The blog post is almost good to go, we just need to add a sentence or two about the Open Spaces bot and explain the promotional aspect of using our hashtag. The blog post is here https://docs.google.com/document/d/1ZvEyX-xH6VccLpL5TK_EcWt5me0Y6tlMP4QOwLfb... <https://docs.google.com/document/d/1ZvEyX-xH6VccLpL5TK_EcWt5me0Y6tlMP4QOwLfb...>
Hobson and Trey, would one of you be able to add the part that is missing to the blog post and then give Brandon the final go once you’ve done so please?
Hobson gave me instructions on how to test the Open Spaces bot but I have been busy with conferences and work and I am going on a much needed work-free (that also includes volunteer work) vacation on Wednesday for a week so I actually won’t have time to test the bot before I leave. I was planning on having time to test the bot today or tomorrow but I had something come up at work and I actually have to put my job before my volunteer work this time, which is something that I rarely do and which I feel bad about. I trust Hobson that the bot works. If however one of you still would like to test the bot, please reach out to Hobson for instructions.
Thank you all for your help in making the Open Spaces awesome again this year! Anna
--------------------------------- You are appreciated. You are enough. You matter. You are not alone.
_______________________________________________ Pycon-openspaces mailing list Pycon-openspaces@python.org <mailto:Pycon-openspaces@python.org> https://mail.python.org/mailman/listinfo/pycon-openspaces <https://mail.python.org/mailman/listinfo/pycon-openspaces>
Hi everyone, I just setup a twitter account with the name @openspaces_bot and will set up the bot using that account this week sometime. For the moment it's still using the old @tw_testy account. I'm totally willing to help out with the a sentence or two promoting the use of the bot for the blog post if needed. I noticed in the google doc that there is already a section talking about the use of the #PyConOpenSpace hashtag. I've included a message about the bot that could possibly be added to that paragraph below. Feel free to change anything or everything :) ----------------------------------------------------------------------------------------------- # possible message about bot "If you would like to reach a wider audience when promoting your Open Space, please take advantage of the Open Spaces Twitter Bot, @openspaces_bot. Send out a tweet that contains the hashtag #PyConOpenSpace, the time of your event, and the room number where the event will be held and the bot will retweet your message 15 minutes before your Open Space is scheduled!" ----------------------------------------------------------------------------------------------- We can also have the bot send out multiple reminder tweets before the event at different time intervals if that is needed. For example retweets 15 & 30 mins before an Open Space, etc. Let me know if y'all have any other questions about the bot setup or anything else. Thank you for letting us use the bot to help promote Open Spaces at PyCon!!! - Zak On Tue, Apr 25, 2017 at 10:36 AM, Anna Ossowski <ossanna16@gmx.de> wrote:
Hobson, this all sounds great!
For the name maybe something like @openspaces_bot if it’s still available?
Thank you all for your hard work! Anna
--------------------------------- You are appreciated. You are enough. You matter. You are not alone.
On Apr 25, 2017, at 11:19 AM, Hobson Lane <hobsonlane@gmail.com> wrote:
Thank you Anna,
Zak, since you built the bot, would you mind working with Trey to put together a sentence explaining how it works? The key is to make it clear that the twitter bot interaction is entirely optional, "just for fun". It's a way for someone to promote their Open Spaces event. This blog post that you are writing the sentence for with trey is for the public, so they will only interact with the bot through tweets with the hashtag #pyconopenspaces. In addition, Open Spaces organizers (like myself) can tweet on behalf of any events in order to help the bot promote an event that we see on the scheduling poster boards. The poster boards are where PyCon attendees put up cards to schedule/suggest an open spaces meetup.
Trey, the bot simply extracts date, time and room number from any tweets that contain #pyconopenspaces . If the tweet looks like someone promoting a valid open spaces event time slot that no one else has yet "claimed" with the bot, the bot will retweet the tweet 15 minutes before the event. It, of course, can't verify that that event exists on the scheduling poster boards, however. Organizers, like you and I and Anna will have access to the twitter bot's schedule and can delete any tweets that are inappropriate or have the bot ignore (blacklist) any accounts that are spamming that hashtag. And we'll have some pretty robust spam filters in place. It may not retweet all the legitimate openspaces tweets, but it will be highly unlikely to embarrass us. And it will not be tweeting from an official pycon account. We can set that account to whatever you and Anna would like. The current test account is @tw_testy . That's where the promotional tweets will come from, not a name attendees need to remember or tweet to.
--Hobson (503) 974-6274
On Mon, Apr 24, 2017 at 5:12 PM, Anna Ossowski <ossanna16@gmx.de> wrote:
Hello everyone!
I had it on my calendar for today to take a final look at the Open Spaces blog post. The blog post is almost good to go, we just need to add a sentence or two about the Open Spaces bot and explain the promotional aspect of using our hashtag. The blog post is here https://docs.google.com/document/d/1ZvEyX-xH6VccLpL5TK_ EcWt5me0Y6tlMP4QOwLfbLVM/edit#heading=h.55czulx95ir4
Hobson and Trey, would one of you be able to add the part that is missing to the blog post and then give Brandon the final go once you’ve done so please?
Hobson gave me instructions on how to test the Open Spaces bot but I have been busy with conferences and work and I am going on a much needed work-free (that also includes volunteer work) vacation on Wednesday for a week so I actually won’t have time to test the bot before I leave. I was planning on having time to test the bot today or tomorrow but I had something come up at work and I actually have to put my job before my volunteer work this time, which is something that I rarely do and which I feel bad about. I trust Hobson that the bot works. If however one of you still would like to test the bot, please reach out to Hobson for instructions.
Thank you all for your help in making the Open Spaces awesome again this year! Anna
--------------------------------- You are appreciated. You are enough. You matter. You are not alone.
_______________________________________________ Pycon-openspaces mailing list Pycon-openspaces@python.org https://mail.python.org/mailman/listinfo/pycon-openspaces
I grabbed @openspacesbot at the same time. Just keep using yours for now, but we have backup if we get blocked/throttled by Twitter for some reason. --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 Tue, Apr 25, 2017 at 12:15 PM, Zak Kent <zak.kent@gmail.com> wrote:
Hi everyone,
I just setup a twitter account with the name @openspaces_bot and will set up the bot using that account this week sometime. For the moment it's still using the old @tw_testy account.
I'm totally willing to help out with the a sentence or two promoting the use of the bot for the blog post if needed. I noticed in the google doc that there is already a section talking about the use of the #PyConOpenSpace hashtag. I've included a message about the bot that could possibly be added to that paragraph below. Feel free to change anything or everything :)
------------------------------------------------------------ ----------------------------------- # possible message about bot
"If you would like to reach a wider audience when promoting your Open Space, please take advantage of the Open Spaces Twitter Bot, @openspaces_bot. Send out a tweet that contains the hashtag #PyConOpenSpace, the time of your event, and the room number where the event will be held and the bot will retweet your message 15 minutes before your Open Space is scheduled!" ------------------------------------------------------------ -----------------------------------
We can also have the bot send out multiple reminder tweets before the event at different time intervals if that is needed. For example retweets 15 & 30 mins before an Open Space, etc.
Let me know if y'all have any other questions about the bot setup or anything else.
Thank you for letting us use the bot to help promote Open Spaces at PyCon!!!
- Zak
On Tue, Apr 25, 2017 at 10:36 AM, Anna Ossowski <ossanna16@gmx.de> wrote:
Hobson, this all sounds great!
For the name maybe something like @openspaces_bot if it’s still available?
Thank you all for your hard work! Anna
--------------------------------- You are appreciated. You are enough. You matter. You are not alone.
On Apr 25, 2017, at 11:19 AM, Hobson Lane <hobsonlane@gmail.com> wrote:
Thank you Anna,
Zak, since you built the bot, would you mind working with Trey to put together a sentence explaining how it works? The key is to make it clear that the twitter bot interaction is entirely optional, "just for fun". It's a way for someone to promote their Open Spaces event. This blog post that you are writing the sentence for with trey is for the public, so they will only interact with the bot through tweets with the hashtag #pyconopenspaces. In addition, Open Spaces organizers (like myself) can tweet on behalf of any events in order to help the bot promote an event that we see on the scheduling poster boards. The poster boards are where PyCon attendees put up cards to schedule/suggest an open spaces meetup.
Trey, the bot simply extracts date, time and room number from any tweets that contain #pyconopenspaces . If the tweet looks like someone promoting a valid open spaces event time slot that no one else has yet "claimed" with the bot, the bot will retweet the tweet 15 minutes before the event. It, of course, can't verify that that event exists on the scheduling poster boards, however. Organizers, like you and I and Anna will have access to the twitter bot's schedule and can delete any tweets that are inappropriate or have the bot ignore (blacklist) any accounts that are spamming that hashtag. And we'll have some pretty robust spam filters in place. It may not retweet all the legitimate openspaces tweets, but it will be highly unlikely to embarrass us. And it will not be tweeting from an official pycon account. We can set that account to whatever you and Anna would like. The current test account is @tw_testy . That's where the promotional tweets will come from, not a name attendees need to remember or tweet to.
--Hobson (503) 974-6274
On Mon, Apr 24, 2017 at 5:12 PM, Anna Ossowski <ossanna16@gmx.de> wrote:
Hello everyone!
I had it on my calendar for today to take a final look at the Open Spaces blog post. The blog post is almost good to go, we just need to add a sentence or two about the Open Spaces bot and explain the promotional aspect of using our hashtag. The blog post is here https://docs.google.com/document/d/1ZvEyX-xH6VccLpL5TK_ EcWt5me0Y6tlMP4QOwLfbLVM/edit#heading=h.55czulx95ir4
Hobson and Trey, would one of you be able to add the part that is missing to the blog post and then give Brandon the final go once you’ve done so please?
Hobson gave me instructions on how to test the Open Spaces bot but I have been busy with conferences and work and I am going on a much needed work-free (that also includes volunteer work) vacation on Wednesday for a week so I actually won’t have time to test the bot before I leave. I was planning on having time to test the bot today or tomorrow but I had something come up at work and I actually have to put my job before my volunteer work this time, which is something that I rarely do and which I feel bad about. I trust Hobson that the bot works. If however one of you still would like to test the bot, please reach out to Hobson for instructions.
Thank you all for your help in making the Open Spaces awesome again this year! Anna
--------------------------------- You are appreciated. You are enough. You matter. You are not alone.
_______________________________________________ Pycon-openspaces mailing list Pycon-openspaces@python.org https://mail.python.org/mailman/listinfo/pycon-openspaces
On Tue, Apr 25, 2017 at 2:15 PM, Zak Kent <zak.kent@gmail.com> wrote:
Hi everyone,
I just setup a twitter account with the name @openspaces_bot and will set up the bot using that account this week sometime. For the moment it's still using the old @tw_testy account.
I'm totally willing to help out with the a sentence or two promoting the use of the bot for the blog post if needed. I noticed in the google doc that there is already a section talking about the use of the #PyConOpenSpace hashtag. I've included a message about the bot that could possibly be added to that paragraph below. Feel free to change anything or everything :)
------------------------------------------------------------ ----------------------------------- # possible message about bot
"If you would like to reach a wider audience when promoting your Open Space, please take advantage of the Open Spaces Twitter Bot, @openspaces_bot. Send out a tweet that contains the hashtag #PyConOpenSpace, the time of your event, and the room number where the event will be held and the bot will retweet your message 15 minutes before your Open Space is scheduled!" ------------------------------------------------------------ -----------------------------------
Sorry to interject mid-convo, but I may use the above text for a sign to place by the board.
On Tue, Apr 25, 2017 at 2:27 PM, Ewa Jodlowska <ewa@python.org> wrote:
On Tue, Apr 25, 2017 at 2:15 PM, Zak Kent <zak.kent@gmail.com> wrote:
Hi everyone,
I just setup a twitter account with the name @openspaces_bot and will set up the bot using that account this week sometime. For the moment it's still using the old @tw_testy account.
I'm totally willing to help out with the a sentence or two promoting the use of the bot for the blog post if needed. I noticed in the google doc that there is already a section talking about the use of the #PyConOpenSpace hashtag. I've included a message about the bot that could possibly be added to that paragraph below. Feel free to change anything or everything :)
------------------------------------------------------------ ----------------------------------- # possible message about bot
"If you would like to reach a wider audience when promoting your Open Space, please take advantage of the Open Spaces Twitter Bot, @openspaces_bot. Send out a tweet that contains the hashtag #PyConOpenSpace, the time of your event, and the room number where the event will be held and the bot will retweet your message 15 minutes before your Open Space is scheduled!" ------------------------------------------------------------ -----------------------------------
Sorry to interject mid-convo, but I may use the above text for a sign to place by the board.
Sigh, email sent before I was finished typing: Sorry to interject mid-convo, but I may use the above text for a sign to place by the board. If you all think that is appropriate and approve, let me know.
Hi all! Thank you for the great work! I currently don’t have time to catch up with the conversation but I’ll do so when I’m back next week. +1 on the blog post text. Thank you, Zak! Thank you for snagging those two Twitter handles. Also +1 for adding that text to a sign by the board. Have a great week! Anna --------------------------------- You are appreciated. You are enough. You matter. You are not alone.
On Apr 25, 2017, at 2:28 PM, Ewa Jodlowska <ewa@python.org> wrote:
On Tue, Apr 25, 2017 at 2:27 PM, Ewa Jodlowska <ewa@python.org <mailto:ewa@python.org>> wrote:
On Tue, Apr 25, 2017 at 2:15 PM, Zak Kent <zak.kent@gmail.com <mailto:zak.kent@gmail.com>> wrote: Hi everyone,
I just setup a twitter account with the name @openspaces_bot and will set up the bot using that account this week sometime. For the moment it's still using the old @tw_testy account.
I'm totally willing to help out with the a sentence or two promoting the use of the bot for the blog post if needed. I noticed in the google doc that there is already a section talking about the use of the #PyConOpenSpace hashtag. I've included a message about the bot that could possibly be added to that paragraph below. Feel free to change anything or everything :)
----------------------------------------------------------------------------------------------- # possible message about bot
"If you would like to reach a wider audience when promoting your Open Space, please take advantage of the Open Spaces Twitter Bot, @openspaces_bot. Send out a tweet that contains the hashtag #PyConOpenSpace, the time of your event, and the room number where the event will be held and the bot will retweet your message 15 minutes before your Open Space is scheduled!" -----------------------------------------------------------------------------------------------
Sorry to interject mid-convo, but I may use the above text for a sign to place by the board.
Sigh, email sent before I was finished typing:
Sorry to interject mid-convo, but I may use the above text for a sign to place by the board. If you all think that is appropriate and approve, let me know.
On Tue, Apr 25, 2017 at 3:34 PM, Anna Ossowski <ossanna16@gmx.de> wrote:
Hi all! Thank you for the great work! I currently don’t have time to catch up with the conversation but I’ll do so when I’m back next week.
+1 on the blog post text. Thank you, Zak! Thank you for snagging those two Twitter handles. …
Anna, at this point do I need to be waiting for you to catch up, or is the blog post text pretty much ready to go at this point? When you think it's ready, please visit the blog https://www.blogger.com/blogger.g?blogID=11638628 and create a new draft post and paste the text in, so that you get properly credited as the author. Let me know once it's up, and I'll do a final proofread and get it ready for release! When should this go out? This week? Or next week, when it's even closer to the conference? Which would have the most impact, do you think? -- Brandon Rhodes PyCon 2017 Conference Chair pycon.brandon@gmail.com
IMO, it should go out closer to the conference. May 13th or May 14th even. Best regards, Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 On Mon, May 1, 2017 at 7:33 PM, Brandon Rhodes <pycon.brandon@gmail.com> wrote:
On Tue, Apr 25, 2017 at 3:34 PM, Anna Ossowski <ossanna16@gmx.de> wrote:
Hi all! Thank you for the great work! I currently don’t have time to catch up with the conversation but I’ll do so when I’m back next week.
+1 on the blog post text. Thank you, Zak! Thank you for snagging those two Twitter handles. …
Anna, at this point do I need to be waiting for you to catch up, or is the blog post text pretty much ready to go at this point? When you think it's ready, please visit the blog https://www.blogger.com/ blogger.g?blogID=11638628 and create a new draft post and paste the text in, so that you get properly credited as the author. Let me know once it's up, and I'll do a final proofread and get it ready for release!
When should this go out? This week? Or next week, when it's even closer to the conference? Which would have the most impact, do you think?
-- Brandon Rhodes PyCon 2017 Conference Chair pycon.brandon@gmail.com
Hello Brandon! I am currently still visiting friends in Nebraska and super busy. I had something come up and decided to extend my trip to help out a friend here. Next week I will be at OSCON all week. I won’t have time to take a look at the blog post until the weekend of May 13 at the earliest. The blog post was good to go on my end, I just thought we needed to add one sentence about the hashtag and the bot. Once that has been added, it is good to go as far as I’m concerned. Also agree with Ewa about the blog post going out closer to the conference. May 13/14 is a weekend though and people don’t check social media as much on the weekends so maybe either May 12 or May 15? Hobson and/or Trey, could one of you please take a look at the blog post and give the final go? I appreciate your help during my absence. Warm regards, Anna --------------------------------- You are appreciated. You are enough. You matter. You are not alone.
On May 1, 2017, at 9:18 PM, Ewa Jodlowska <ewa@python.org <mailto:ewa@python.org>> wrote:
IMO, it should go out closer to the conference. May 13th or May 14th even.
Best regards,
Ewa Director of Operations Python Software Foundation Cell: 415-319-5237
On Mon, May 1, 2017 at 7:33 PM, Brandon Rhodes <pycon.brandon@gmail.com <mailto:pycon.brandon@gmail.com>> wrote: On Tue, Apr 25, 2017 at 3:34 PM, Anna Ossowski <ossanna16@gmx.de <mailto:ossanna16@gmx.de>> wrote: Hi all! Thank you for the great work! I currently don’t have time to catch up with the conversation but I’ll do so when I’m back next week.
+1 on the blog post text. Thank you, Zak! Thank you for snagging those two Twitter handles. …
Anna, at this point do I need to be waiting for you to catch up, or is the blog post text pretty much ready to go at this point? When you think it's ready, please visit the blog https://www.blogger.com/blogger.g?blogID=11638628 <https://www.blogger.com/blogger.g?blogID=11638628> and create a new draft post and paste the text in, so that you get properly credited as the author. Let me know once it's up, and I'll do a final proofread and get it ready for release!
When should this go out? This week? Or next week, when it's even closer to the conference? Which would have the most impact, do you think?
-- Brandon Rhodes PyCon 2017 Conference Chair pycon.brandon@gmail.com <mailto:pycon.brandon@gmail.com>
--------------------------------- You are appreciated. You are enough. You matter. You are not alone.
Hey all! I’m back in office for today before flying to Portland tomorrow. Thank you all for your great work during my absence. I just wanted to check if the blog post has been published. We were aiming for May 15 as the publishing date. Also are we good to go otherwise or is there anything else we need to work on/discuss? I’m brining a friend to Portland with me and we are driving out to the coast tomorrow and spending a night there before returning to Portland on Wednesday. I will check my emails tomorrow evening and plan to be at the staff dinner on Wednesday. In any emergencies you can reach me at 636.465.4916. So excited for PyCon and looking forward to seeing you! Anna --------------------------------- You are appreciated. You are enough. You matter. You are not alone.
On May 1, 2017, at 11:17 PM, Anna Ossowski <annabell.ossowski@gmail.com> wrote:
Hello Brandon!
I am currently still visiting friends in Nebraska and super busy. I had something come up and decided to extend my trip to help out a friend here. Next week I will be at OSCON all week. I won’t have time to take a look at the blog post until the weekend of May 13 at the earliest. The blog post was good to go on my end, I just thought we needed to add one sentence about the hashtag and the bot. Once that has been added, it is good to go as far as I’m concerned. Also agree with Ewa about the blog post going out closer to the conference. May 13/14 is a weekend though and people don’t check social media as much on the weekends so maybe either May 12 or May 15?
Hobson and/or Trey, could one of you please take a look at the blog post and give the final go? I appreciate your help during my absence.
Warm regards, Anna
--------------------------------- You are appreciated. You are enough. You matter. You are not alone.
On May 1, 2017, at 9:18 PM, Ewa Jodlowska <ewa@python.org <mailto:ewa@python.org>> wrote:
IMO, it should go out closer to the conference. May 13th or May 14th even.
Best regards,
Ewa Director of Operations Python Software Foundation Cell: 415-319-5237
On Mon, May 1, 2017 at 7:33 PM, Brandon Rhodes <pycon.brandon@gmail.com <mailto:pycon.brandon@gmail.com>> wrote: On Tue, Apr 25, 2017 at 3:34 PM, Anna Ossowski <ossanna16@gmx.de <mailto:ossanna16@gmx.de>> wrote: Hi all! Thank you for the great work! I currently don’t have time to catch up with the conversation but I’ll do so when I’m back next week.
+1 on the blog post text. Thank you, Zak! Thank you for snagging those two Twitter handles. …
Anna, at this point do I need to be waiting for you to catch up, or is the blog post text pretty much ready to go at this point? When you think it's ready, please visit the blog https://www.blogger.com/blogger.g?blogID=11638628 <https://www.blogger.com/blogger.g?blogID=11638628> and create a new draft post and paste the text in, so that you get properly credited as the author. Let me know once it's up, and I'll do a final proofread and get it ready for release!
When should this go out? This week? Or next week, when it's even closer to the conference? Which would have the most impact, do you think?
-- Brandon Rhodes PyCon 2017 Conference Chair pycon.brandon@gmail.com <mailto:pycon.brandon@gmail.com>
--------------------------------- You are appreciated. You are enough. You matter. You are not alone.
_______________________________________________ Pycon-openspaces mailing list Pycon-openspaces@python.org https://mail.python.org/mailman/listinfo/pycon-openspaces
Zak's configuring the bot to go "live" and will show you how to monitor and curate the tweets by Thursday's start date. Have fun on the coast! --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, May 15, 2017 at 1:31 PM, Anna Ossowski <annabell.ossowski@gmail.com> wrote:
Hey all!
I’m back in office for today before flying to Portland tomorrow. Thank you all for your great work during my absence.
I just wanted to check if the blog post has been published. We were aiming for May 15 as the publishing date.
Also are we good to go otherwise or is there anything else we need to work on/discuss?
I’m brining a friend to Portland with me and we are driving out to the coast tomorrow and spending a night there before returning to Portland on Wednesday. I will check my emails tomorrow evening and plan to be at the staff dinner on Wednesday. In any emergencies you can reach me at 636.465.4916 <(636)%20465-4916>.
So excited for PyCon and looking forward to seeing you! Anna
--------------------------------- You are appreciated. You are enough. You matter. You are not alone.
On May 1, 2017, at 11:17 PM, Anna Ossowski <annabell.ossowski@gmail.com> wrote:
Hello Brandon!
I am currently still visiting friends in Nebraska and super busy. I had something come up and decided to extend my trip to help out a friend here. Next week I will be at OSCON all week. I won’t have time to take a look at the blog post until the weekend of May 13 at the earliest. The blog post was good to go on my end, I just thought we needed to add one sentence about the hashtag and the bot. Once that has been added, it is good to go as far as I’m concerned. Also agree with Ewa about the blog post going out closer to the conference. May 13/14 is a weekend though and people don’t check social media as much on the weekends so maybe either May 12 or May 15?
Hobson and/or Trey, could one of you please take a look at the blog post and give the final go? I appreciate your help during my absence.
Warm regards, Anna
--------------------------------- You are appreciated. You are enough. You matter. You are not alone.
On May 1, 2017, at 9:18 PM, Ewa Jodlowska <ewa@python.org> wrote:
IMO, it should go out closer to the conference. May 13th or May 14th even.
Best regards,
Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 <(415)%20319-5237>
On Mon, May 1, 2017 at 7:33 PM, Brandon Rhodes <pycon.brandon@gmail.com> wrote:
On Tue, Apr 25, 2017 at 3:34 PM, Anna Ossowski <ossanna16@gmx.de> wrote:
Hi all! Thank you for the great work! I currently don’t have time to catch up with the conversation but I’ll do so when I’m back next week.
+1 on the blog post text. Thank you, Zak! Thank you for snagging those two Twitter handles. …
Anna, at this point do I need to be waiting for you to catch up, or is the blog post text pretty much ready to go at this point? When you think it's ready, please visit the blog https://www.blogger.com/b logger.g?blogID=11638628 and create a new draft post and paste the text in, so that you get properly credited as the author. Let me know once it's up, and I'll do a final proofread and get it ready for release!
When should this go out? This week? Or next week, when it's even closer to the conference? Which would have the most impact, do you think?
-- Brandon Rhodes PyCon 2017 Conference Chair pycon.brandon@gmail.com
--------------------------------- You are appreciated. You are enough. You matter. You are not alone.
_______________________________________________ Pycon-openspaces mailing list Pycon-openspaces@python.org https://mail.python.org/mailman/listinfo/pycon-openspaces
_______________________________________________ Pycon-openspaces mailing list Pycon-openspaces@python.org https://mail.python.org/mailman/listinfo/pycon-openspaces
Awesome! I’ll be around at the conference pretty much all day on Thursday. Let’s catch up in person then? --------------------------------- You are appreciated. You are enough. You matter. You are not alone.
On May 15, 2017, at 6:00 PM, Hobson Lane <hobsonlane@gmail.com> wrote:
Zak's configuring the bot to go "live" and will show you how to monitor and curate the tweets by Thursday's start date. Have fun on the coast!
--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, May 15, 2017 at 1:31 PM, Anna Ossowski <annabell.ossowski@gmail.com <mailto:annabell.ossowski@gmail.com>> wrote: Hey all!
I’m back in office for today before flying to Portland tomorrow. Thank you all for your great work during my absence.
I just wanted to check if the blog post has been published. We were aiming for May 15 as the publishing date.
Also are we good to go otherwise or is there anything else we need to work on/discuss?
I’m brining a friend to Portland with me and we are driving out to the coast tomorrow and spending a night there before returning to Portland on Wednesday. I will check my emails tomorrow evening and plan to be at the staff dinner on Wednesday. In any emergencies you can reach me at 636.465.4916 <tel:(636)%20465-4916>.
So excited for PyCon and looking forward to seeing you! Anna
--------------------------------- You are appreciated. You are enough. You matter. You are not alone.
On May 1, 2017, at 11:17 PM, Anna Ossowski <annabell.ossowski@gmail.com <mailto:annabell.ossowski@gmail.com>> wrote:
Hello Brandon!
I am currently still visiting friends in Nebraska and super busy. I had something come up and decided to extend my trip to help out a friend here. Next week I will be at OSCON all week. I won’t have time to take a look at the blog post until the weekend of May 13 at the earliest. The blog post was good to go on my end, I just thought we needed to add one sentence about the hashtag and the bot. Once that has been added, it is good to go as far as I’m concerned. Also agree with Ewa about the blog post going out closer to the conference. May 13/14 is a weekend though and people don’t check social media as much on the weekends so maybe either May 12 or May 15?
Hobson and/or Trey, could one of you please take a look at the blog post and give the final go? I appreciate your help during my absence.
Warm regards, Anna
--------------------------------- You are appreciated. You are enough. You matter. You are not alone.
On May 1, 2017, at 9:18 PM, Ewa Jodlowska <ewa@python.org <mailto:ewa@python.org>> wrote:
IMO, it should go out closer to the conference. May 13th or May 14th even.
Best regards,
Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 <tel:(415)%20319-5237> On Mon, May 1, 2017 at 7:33 PM, Brandon Rhodes <pycon.brandon@gmail.com <mailto:pycon.brandon@gmail.com>> wrote: On Tue, Apr 25, 2017 at 3:34 PM, Anna Ossowski <ossanna16@gmx.de <mailto:ossanna16@gmx.de>> wrote: Hi all! Thank you for the great work! I currently don’t have time to catch up with the conversation but I’ll do so when I’m back next week.
+1 on the blog post text. Thank you, Zak! Thank you for snagging those two Twitter handles. …
Anna, at this point do I need to be waiting for you to catch up, or is the blog post text pretty much ready to go at this point? When you think it's ready, please visit the blog https://www.blogger.com/blogger.g?blogID=11638628 <https://www.blogger.com/blogger.g?blogID=11638628> and create a new draft post and paste the text in, so that you get properly credited as the author. Let me know once it's up, and I'll do a final proofread and get it ready for release!
When should this go out? This week? Or next week, when it's even closer to the conference? Which would have the most impact, do you think?
-- Brandon Rhodes PyCon 2017 Conference Chair pycon.brandon@gmail.com <mailto:pycon.brandon@gmail.com>
--------------------------------- You are appreciated. You are enough. You matter. You are not alone.
_______________________________________________ Pycon-openspaces mailing list Pycon-openspaces@python.org <mailto:Pycon-openspaces@python.org> https://mail.python.org/mailman/listinfo/pycon-openspaces <https://mail.python.org/mailman/listinfo/pycon-openspaces>
_______________________________________________ Pycon-openspaces mailing list Pycon-openspaces@python.org <mailto:Pycon-openspaces@python.org> https://mail.python.org/mailman/listinfo/pycon-openspaces <https://mail.python.org/mailman/listinfo/pycon-openspaces>
Anna, so that you get credit as author, could you quickly paste the text into a "New post" here? https://www.blogger.com/blogger.g?blogID=11638628#allposts Don't bother spending your own busy time formatting etc, as I'll be happy to do that; I just want you to get credit for the work or writing, and to help people associate you with the Open Spaces in case they have questions on-site. Thanks! On Mon, May 15, 2017 at 4:31 PM, Anna Ossowski <annabell.ossowski@gmail.com> wrote:
Hey all!
I’m back in office for today before flying to Portland tomorrow. Thank you all for your great work during my absence.
I just wanted to check if the blog post has been published. We were aiming for May 15 as the publishing date.
Also are we good to go otherwise or is there anything else we need to work on/discuss?
I’m brining a friend to Portland with me and we are driving out to the coast tomorrow and spending a night there before returning to Portland on Wednesday. I will check my emails tomorrow evening and plan to be at the staff dinner on Wednesday. In any emergencies you can reach me at 636.465.4916 <(636)%20465-4916>.
So excited for PyCon and looking forward to seeing you! Anna
--------------------------------- You are appreciated. You are enough. You matter. You are not alone.
On May 1, 2017, at 11:17 PM, Anna Ossowski <annabell.ossowski@gmail.com> wrote:
Hello Brandon!
I am currently still visiting friends in Nebraska and super busy. I had something come up and decided to extend my trip to help out a friend here. Next week I will be at OSCON all week. I won’t have time to take a look at the blog post until the weekend of May 13 at the earliest. The blog post was good to go on my end, I just thought we needed to add one sentence about the hashtag and the bot. Once that has been added, it is good to go as far as I’m concerned. Also agree with Ewa about the blog post going out closer to the conference. May 13/14 is a weekend though and people don’t check social media as much on the weekends so maybe either May 12 or May 15?
Hobson and/or Trey, could one of you please take a look at the blog post and give the final go? I appreciate your help during my absence.
Warm regards, Anna
--------------------------------- You are appreciated. You are enough. You matter. You are not alone.
On May 1, 2017, at 9:18 PM, Ewa Jodlowska <ewa@python.org> wrote:
IMO, it should go out closer to the conference. May 13th or May 14th even.
Best regards,
Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 <(415)%20319-5237>
On Mon, May 1, 2017 at 7:33 PM, Brandon Rhodes <pycon.brandon@gmail.com> wrote:
On Tue, Apr 25, 2017 at 3:34 PM, Anna Ossowski <ossanna16@gmx.de> wrote:
Hi all! Thank you for the great work! I currently don’t have time to catch up with the conversation but I’ll do so when I’m back next week.
+1 on the blog post text. Thank you, Zak! Thank you for snagging those two Twitter handles. …
Anna, at this point do I need to be waiting for you to catch up, or is the blog post text pretty much ready to go at this point? When you think it's ready, please visit the blog https://www.blogger.com/b logger.g?blogID=11638628 and create a new draft post and paste the text in, so that you get properly credited as the author. Let me know once it's up, and I'll do a final proofread and get it ready for release!
When should this go out? This week? Or next week, when it's even closer to the conference? Which would have the most impact, do you think?
-- Brandon Rhodes PyCon 2017 Conference Chair pycon.brandon@gmail.com
--------------------------------- You are appreciated. You are enough. You matter. You are not alone.
_______________________________________________ Pycon-openspaces mailing list Pycon-openspaces@python.org https://mail.python.org/mailman/listinfo/pycon-openspaces
_______________________________________________ Pycon-openspaces mailing list Pycon-openspaces@python.org https://mail.python.org/mailman/listinfo/pycon-openspaces
-- Brandon Rhodes PyCon 2017 Conference Chair pycon.brandon@gmail.com
I added the post and saved it as a draft, Brandon. Thank you so much for offering to format it. I appreciate it! Please let me know if you need me to do anything else. Anna --------------------------------- You are appreciated. You are enough. You matter. You are not alone.
On May 15, 2017, at 6:07 PM, Brandon Rhodes <pycon.brandon@gmail.com> wrote:
Anna, so that you get credit as author, could you quickly paste the text into a "New post" here?
https://www.blogger.com/blogger.g?blogID=11638628#allposts <https://www.blogger.com/blogger.g?blogID=11638628#allposts>
Don't bother spending your own busy time formatting etc, as I'll be happy to do that; I just want you to get credit for the work or writing, and to help people associate you with the Open Spaces in case they have questions on-site. Thanks!
On Mon, May 15, 2017 at 4:31 PM, Anna Ossowski <annabell.ossowski@gmail.com <mailto:annabell.ossowski@gmail.com>> wrote: Hey all!
I’m back in office for today before flying to Portland tomorrow. Thank you all for your great work during my absence.
I just wanted to check if the blog post has been published. We were aiming for May 15 as the publishing date.
Also are we good to go otherwise or is there anything else we need to work on/discuss?
I’m brining a friend to Portland with me and we are driving out to the coast tomorrow and spending a night there before returning to Portland on Wednesday. I will check my emails tomorrow evening and plan to be at the staff dinner on Wednesday. In any emergencies you can reach me at 636.465.4916 <tel:(636)%20465-4916>.
So excited for PyCon and looking forward to seeing you! Anna
--------------------------------- You are appreciated. You are enough. You matter. You are not alone.
On May 1, 2017, at 11:17 PM, Anna Ossowski <annabell.ossowski@gmail.com <mailto:annabell.ossowski@gmail.com>> wrote:
Hello Brandon!
I am currently still visiting friends in Nebraska and super busy. I had something come up and decided to extend my trip to help out a friend here. Next week I will be at OSCON all week. I won’t have time to take a look at the blog post until the weekend of May 13 at the earliest. The blog post was good to go on my end, I just thought we needed to add one sentence about the hashtag and the bot. Once that has been added, it is good to go as far as I’m concerned. Also agree with Ewa about the blog post going out closer to the conference. May 13/14 is a weekend though and people don’t check social media as much on the weekends so maybe either May 12 or May 15?
Hobson and/or Trey, could one of you please take a look at the blog post and give the final go? I appreciate your help during my absence.
Warm regards, Anna
--------------------------------- You are appreciated. You are enough. You matter. You are not alone.
On May 1, 2017, at 9:18 PM, Ewa Jodlowska <ewa@python.org <mailto:ewa@python.org>> wrote:
IMO, it should go out closer to the conference. May 13th or May 14th even.
Best regards,
Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 <tel:(415)%20319-5237> On Mon, May 1, 2017 at 7:33 PM, Brandon Rhodes <pycon.brandon@gmail.com <mailto:pycon.brandon@gmail.com>> wrote: On Tue, Apr 25, 2017 at 3:34 PM, Anna Ossowski <ossanna16@gmx.de <mailto:ossanna16@gmx.de>> wrote: Hi all! Thank you for the great work! I currently don’t have time to catch up with the conversation but I’ll do so when I’m back next week.
+1 on the blog post text. Thank you, Zak! Thank you for snagging those two Twitter handles. …
Anna, at this point do I need to be waiting for you to catch up, or is the blog post text pretty much ready to go at this point? When you think it's ready, please visit the blog https://www.blogger.com/blogger.g?blogID=11638628 <https://www.blogger.com/blogger.g?blogID=11638628> and create a new draft post and paste the text in, so that you get properly credited as the author. Let me know once it's up, and I'll do a final proofread and get it ready for release!
When should this go out? This week? Or next week, when it's even closer to the conference? Which would have the most impact, do you think?
-- Brandon Rhodes PyCon 2017 Conference Chair pycon.brandon@gmail.com <mailto:pycon.brandon@gmail.com>
--------------------------------- You are appreciated. You are enough. You matter. You are not alone.
_______________________________________________ Pycon-openspaces mailing list Pycon-openspaces@python.org <mailto:Pycon-openspaces@python.org> https://mail.python.org/mailman/listinfo/pycon-openspaces <https://mail.python.org/mailman/listinfo/pycon-openspaces>
_______________________________________________ Pycon-openspaces mailing list Pycon-openspaces@python.org <mailto:Pycon-openspaces@python.org> https://mail.python.org/mailman/listinfo/pycon-openspaces <https://mail.python.org/mailman/listinfo/pycon-openspaces>
-- Brandon Rhodes PyCon 2017 Conference Chair pycon.brandon@gmail.com <mailto:pycon.brandon@gmail.com>_______________________________________________ Pycon-openspaces mailing list Pycon-openspaces@python.org https://mail.python.org/mailman/listinfo/pycon-openspaces
Thanks for drafting and publishing the post Anna and Brandon! I'll also be at the PyCon staff dinner on Wednesday. Look forward to seeing you all during the conference. FYI if any of you need to locate me in real-time during the conference, my number is 619-320-8739. \-- Trey Hunner Python & Django trainer [Truthful Technology](http://truthful.technology) [Weekly Python Chat](https://weeklypython.chat) On May 15 2017, at 4:22 pm, Anna Ossowski <annabell.ossowski@gmail.com> wrote:
I added the post and saved it as a draft, Brandon. Thank you so much for offering to format it. I appreciate it!
Please let me know if you need me to do anything else.
Anna
\---------------------------------
You are appreciated.
You are enough.
You matter.
You are not alone.
On May 15, 2017, at 6:07 PM, Brandon Rhodes <[pycon.brandon@gmail.com](mailto:pycon.brandon@gmail.com)> wrote:
Anna, so that you get credit as author, could you quickly paste the text into a "New post" here?
<https://www.blogger.com/blogger.g?blogID=11638628#allposts>
Don't bother spending your own busy time formatting etc, as I'll be happy to do that; I just want you to get credit for the work or writing, and to help people associate you with the Open Spaces in case they have questions on-site. Thanks!
On Mon, May 15, 2017 at 4:31 PM, Anna Ossowski <[annabell.ossowski@gmail.com](mailto:annabell.ossowski@gmail.com)> wrote:
Hey all!
I’m back in office for today before flying to Portland tomorrow. Thank you all for your great work during my absence.
I just wanted to check if the blog post has been published. We were aiming for May 15 as the publishing date.
Also are we good to go otherwise or is there anything else we need to work on/discuss?
I’m brining a friend to Portland with me and we are driving out to the coast tomorrow and spending a night there before returning to Portland on Wednesday. I will check my emails tomorrow evening and plan to be at the staff dinner on Wednesday. In any emergencies you can reach me at 636.465.4916.
So excited for PyCon and looking forward to seeing you!
Anna
\------------------------------\---
You are appreciated.
You are enough.
You matter.
You are not alone.
On May 1, 2017, at 11:17 PM, Anna Ossowski <[annabell.ossowski@gmail.com](mailto:annabell.ossowski@gmail.com)> wrote:
Hello Brandon!
I am currently still visiting friends in Nebraska and super busy. I had something come up and decided to extend my trip to help out a friend here. Next week I will be at OSCON all week. I won’t have time to take a look at the blog post until the weekend of May 13 at the earliest. The blog post was good to go on my end, I just thought we needed to add one sentence about the hashtag and the bot. Once that has been added, it is good to go as far as I’m concerned. Also agree with Ewa about the blog post going out closer to the conference. May 13/14 is a weekend though and people don’t check social media as much on the weekends so maybe either May 12 or May 15?
Hobson and/or Trey, could one of you please take a look at the blog post and give the final go? I appreciate your help during my absence.
Warm regards,
Anna
\------------------------------\---
You are appreciated.
You are enough.
You matter.
You are not alone.
On May 1, 2017, at 9:18 PM, Ewa Jodlowska <[ewa@python.org](mailto:ewa@python.org)> wrote:
IMO, it should go out closer to the conference. May 13th or May 14th even.
Best regards,
Ewa
Director of Operations
Python Software Foundation
Cell: 415-319-5237
On Mon, May 1, 2017 at 7:33 PM, Brandon Rhodes <[pycon.brandon@gmail.com](mailto:pycon.brandon@gmail.com)> wrote:
On Tue, Apr 25, 2017 at 3:34 PM, Anna Ossowski <[ossanna16@gmx.de](mailto:ossanna16@gmx.de)> wrote:
> Hi all! Thank you for the great work! I currently don’t have time to catch up with the conversation but I’ll do so when I’m back next week.
>
>
>
> +1 on the blog post text. Thank you, Zak! Thank you for snagging those two Twitter handles. …
Anna, at this point do I need to be waiting for you to catch up, or is the blog post text pretty much ready to go at this point? When you think it's ready, please visit the blog [https://www.blogger.com/blogger.g?blogID=1163862 8](https://www.blogger.com/blogger.g?blogID=11638628) and create a new draft post and paste the text in, so that you get properly credited as the author. Let me know once it's up, and I'll do a final proofread and get it ready for release!
When should this go out? This week? Or next week, when it's even closer to the conference? Which would have the most impact, do you think?
\--
Brandon Rhodes
PyCon 2017 Conference Chair
[pycon.brandon@gmail.com](mailto:pycon.brandon@gmail.com)
\------------------------------\---
You are appreciated.
You are enough.
You matter.
You are not alone.
_______________________________________________ Pycon-openspaces mailing list [Pycon-openspaces@python.org](mailto:Pycon-openspaces@python.org) [https://mail.python.org/mailman/listinfo/pycon- openspaces](https://mail.python.org/mailman/listinfo/pycon-openspaces)
Pycon-openspaces mailing list [Pycon-openspaces@python.org](mailto:Pycon-openspaces@python.org) [https://mail.python.org/mailman/listinfo/pycon- openspaces](https://mail.python.org/mailman/listinfo/pycon-openspaces)
\--
Brandon Rhodes
PyCon 2017 Conference Chair
[pycon.brandon@gmail.com](mailto:pycon.brandon@gmail.com)
_______________________________________________ Pycon-openspaces mailing list [Pycon-openspaces@python.org](mailto:Pycon-openspaces@python.org) https://mail.python.org/mailman/listinfo/pycon-openspaces
The post is now public! Feel free to tweak anywhere I introduced a typo :) http://pycon.blogspot.com/2017/05/dont-overlook-open-spaces-at-pycon-this.ht... Thanks for your work, everyone, and I look forward to seeing the Open Spaces that our attendees will organize this year! On Mon, May 15, 2017 at 7:21 PM, Anna Ossowski <annabell.ossowski@gmail.com> wrote:
I added the post and saved it as a draft, Brandon. Thank you so much for offering to format it. I appreciate it!
Please let me know if you need me to do anything else.
Anna
--------------------------------- You are appreciated. You are enough. You matter. You are not alone.
On May 15, 2017, at 6:07 PM, Brandon Rhodes <pycon.brandon@gmail.com> wrote:
Anna, so that you get credit as author, could you quickly paste the text into a "New post" here?
https://www.blogger.com/blogger.g?blogID=11638628#allposts
Don't bother spending your own busy time formatting etc, as I'll be happy to do that; I just want you to get credit for the work or writing, and to help people associate you with the Open Spaces in case they have questions on-site. Thanks!
On Mon, May 15, 2017 at 4:31 PM, Anna Ossowski < annabell.ossowski@gmail.com> wrote:
Hey all!
I’m back in office for today before flying to Portland tomorrow. Thank you all for your great work during my absence.
I just wanted to check if the blog post has been published. We were aiming for May 15 as the publishing date.
Also are we good to go otherwise or is there anything else we need to work on/discuss?
I’m brining a friend to Portland with me and we are driving out to the coast tomorrow and spending a night there before returning to Portland on Wednesday. I will check my emails tomorrow evening and plan to be at the staff dinner on Wednesday. In any emergencies you can reach me at 636.465.4916 <(636)%20465-4916>.
So excited for PyCon and looking forward to seeing you! Anna
--------------------------------- You are appreciated. You are enough. You matter. You are not alone.
On May 1, 2017, at 11:17 PM, Anna Ossowski <annabell.ossowski@gmail.com> wrote:
Hello Brandon!
I am currently still visiting friends in Nebraska and super busy. I had something come up and decided to extend my trip to help out a friend here. Next week I will be at OSCON all week. I won’t have time to take a look at the blog post until the weekend of May 13 at the earliest. The blog post was good to go on my end, I just thought we needed to add one sentence about the hashtag and the bot. Once that has been added, it is good to go as far as I’m concerned. Also agree with Ewa about the blog post going out closer to the conference. May 13/14 is a weekend though and people don’t check social media as much on the weekends so maybe either May 12 or May 15?
Hobson and/or Trey, could one of you please take a look at the blog post and give the final go? I appreciate your help during my absence.
Warm regards, Anna
--------------------------------- You are appreciated. You are enough. You matter. You are not alone.
On May 1, 2017, at 9:18 PM, Ewa Jodlowska <ewa@python.org> wrote:
IMO, it should go out closer to the conference. May 13th or May 14th even.
Best regards,
Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 <(415)%20319-5237>
On Mon, May 1, 2017 at 7:33 PM, Brandon Rhodes <pycon.brandon@gmail.com> wrote:
On Tue, Apr 25, 2017 at 3:34 PM, Anna Ossowski <ossanna16@gmx.de> wrote:
Hi all! Thank you for the great work! I currently don’t have time to catch up with the conversation but I’ll do so when I’m back next week.
+1 on the blog post text. Thank you, Zak! Thank you for snagging those two Twitter handles. …
Anna, at this point do I need to be waiting for you to catch up, or is the blog post text pretty much ready to go at this point? When you think it's ready, please visit the blog https://www.blogger.com/b logger.g?blogID=11638628 and create a new draft post and paste the text in, so that you get properly credited as the author. Let me know once it's up, and I'll do a final proofread and get it ready for release!
When should this go out? This week? Or next week, when it's even closer to the conference? Which would have the most impact, do you think?
-- Brandon Rhodes PyCon 2017 Conference Chair pycon.brandon@gmail.com
--------------------------------- You are appreciated. You are enough. You matter. You are not alone.
_______________________________________________ Pycon-openspaces mailing list Pycon-openspaces@python.org https://mail.python.org/mailman/listinfo/pycon-openspaces
_______________________________________________ Pycon-openspaces mailing list Pycon-openspaces@python.org https://mail.python.org/mailman/listinfo/pycon-openspaces
-- Brandon Rhodes PyCon 2017 Conference Chair pycon.brandon@gmail.com _______________________________________________ Pycon-openspaces mailing list Pycon-openspaces@python.org https://mail.python.org/mailman/listinfo/pycon-openspaces
-- Brandon Rhodes PyCon 2017 Conference Chair pycon.brandon@gmail.com
I agree. --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, May 1, 2017 at 7:18 PM, Ewa Jodlowska <ewa@python.org> wrote:
IMO, it should go out closer to the conference. May 13th or May 14th even.
Best regards,
Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 <(415)%20319-5237>
On Mon, May 1, 2017 at 7:33 PM, Brandon Rhodes <pycon.brandon@gmail.com> wrote:
On Tue, Apr 25, 2017 at 3:34 PM, Anna Ossowski <ossanna16@gmx.de> wrote:
Hi all! Thank you for the great work! I currently don’t have time to catch up with the conversation but I’ll do so when I’m back next week.
+1 on the blog post text. Thank you, Zak! Thank you for snagging those two Twitter handles. …
Anna, at this point do I need to be waiting for you to catch up, or is the blog post text pretty much ready to go at this point? When you think it's ready, please visit the blog https://www.blogger.com/b logger.g?blogID=11638628 and create a new draft post and paste the text in, so that you get properly credited as the author. Let me know once it's up, and I'll do a final proofread and get it ready for release!
When should this go out? This week? Or next week, when it's even closer to the conference? Which would have the most impact, do you think?
-- Brandon Rhodes PyCon 2017 Conference Chair pycon.brandon@gmail.com
_______________________________________________ Pycon-openspaces mailing list Pycon-openspaces@python.org https://mail.python.org/mailman/listinfo/pycon-openspaces
Thank you — I'll consider the blog post ready for release, then! Per Ewa and Anna, I will indeed wait before posting it, and probably aim for May 15th as its release date. Thanks, everyone! On Tue, May 2, 2017 at 1:23 AM, Hobson Lane <hobsonlane@gmail.com> wrote:
I agree.
--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, May 1, 2017 at 7:18 PM, Ewa Jodlowska <ewa@python.org> wrote:
IMO, it should go out closer to the conference. May 13th or May 14th even.
Best regards,
Ewa Director of Operations Python Software Foundation Cell: 415-319-5237 <(415)%20319-5237>
On Mon, May 1, 2017 at 7:33 PM, Brandon Rhodes <pycon.brandon@gmail.com> wrote:
On Tue, Apr 25, 2017 at 3:34 PM, Anna Ossowski <ossanna16@gmx.de> wrote:
Hi all! Thank you for the great work! I currently don’t have time to catch up with the conversation but I’ll do so when I’m back next week.
+1 on the blog post text. Thank you, Zak! Thank you for snagging those two Twitter handles. …
Anna, at this point do I need to be waiting for you to catch up, or is the blog post text pretty much ready to go at this point? When you think it's ready, please visit the blog https://www.blogger.com/b logger.g?blogID=11638628 and create a new draft post and paste the text in, so that you get properly credited as the author. Let me know once it's up, and I'll do a final proofread and get it ready for release!
When should this go out? This week? Or next week, when it's even closer to the conference? Which would have the most impact, do you think?
-- Brandon Rhodes PyCon 2017 Conference Chair pycon.brandon@gmail.com
_______________________________________________ Pycon-openspaces mailing list Pycon-openspaces@python.org https://mail.python.org/mailman/listinfo/pycon-openspaces
-- Brandon Rhodes PyCon 2017 Conference Chair pycon.brandon@gmail.com
+1 good idea! --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 Tue, Apr 25, 2017 at 12:28 PM, Ewa Jodlowska <ewa@python.org> wrote:
On Tue, Apr 25, 2017 at 2:27 PM, Ewa Jodlowska <ewa@python.org> wrote:
On Tue, Apr 25, 2017 at 2:15 PM, Zak Kent <zak.kent@gmail.com> wrote:
Hi everyone,
I just setup a twitter account with the name @openspaces_bot and will set up the bot using that account this week sometime. For the moment it's still using the old @tw_testy account.
I'm totally willing to help out with the a sentence or two promoting the use of the bot for the blog post if needed. I noticed in the google doc that there is already a section talking about the use of the #PyConOpenSpace hashtag. I've included a message about the bot that could possibly be added to that paragraph below. Feel free to change anything or everything :)
------------------------------------------------------------ ----------------------------------- # possible message about bot
"If you would like to reach a wider audience when promoting your Open Space, please take advantage of the Open Spaces Twitter Bot, @openspaces_bot. Send out a tweet that contains the hashtag #PyConOpenSpace, the time of your event, and the room number where the event will be held and the bot will retweet your message 15 minutes before your Open Space is scheduled!" ------------------------------------------------------------ -----------------------------------
Sorry to interject mid-convo, but I may use the above text for a sign to place by the board.
Sigh, email sent before I was finished typing:
Sorry to interject mid-convo, but I may use the above text for a sign to place by the board. If you all think that is appropriate and approve, let me know.
_______________________________________________ Pycon-openspaces mailing list Pycon-openspaces@python.org https://mail.python.org/mailman/listinfo/pycon-openspaces
Chiming in a little late. Thanks for re-starting the conversation Anna and thanks for the bot explanation Hobson. Zak, I think that blurb sounds good. Ewa, I really like the idea of using a blurb for the open spaces board so people filling out a card know how to promote it on Twitter. I think a slightly shorter blurb might stand out more near for the in-person board. Maybe a one sentence one: "Tweet the time, room number, and description of your event using #PyConOpenSpace and the Twitter @openspaces_bot will help you promote your open space." Also I wonder whether we should remind folks looking at the board that find open space reminders on Twitter too. Same idea, but different audience (since most people looking at the board will not be open space organizers but open space attendees). On Tue, Apr 25, 2017 at 12:42 PM, Hobson Lane <hobsonlane@gmail.com> wrote:
+1 good idea!
--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 Tue, Apr 25, 2017 at 12:28 PM, Ewa Jodlowska <ewa@python.org> wrote:
On Tue, Apr 25, 2017 at 2:27 PM, Ewa Jodlowska <ewa@python.org> wrote:
On Tue, Apr 25, 2017 at 2:15 PM, Zak Kent <zak.kent@gmail.com> wrote:
Hi everyone,
I just setup a twitter account with the name @openspaces_bot and will set up the bot using that account this week sometime. For the moment it's still using the old @tw_testy account.
I'm totally willing to help out with the a sentence or two promoting the use of the bot for the blog post if needed. I noticed in the google doc that there is already a section talking about the use of the #PyConOpenSpace hashtag. I've included a message about the bot that could possibly be added to that paragraph below. Feel free to change anything or everything :)
------------------------------------------------------------ ----------------------------------- # possible message about bot
"If you would like to reach a wider audience when promoting your Open Space, please take advantage of the Open Spaces Twitter Bot, @openspaces_bot. Send out a tweet that contains the hashtag #PyConOpenSpace, the time of your event, and the room number where the event will be held and the bot will retweet your message 15 minutes before your Open Space is scheduled!" ------------------------------------------------------------ -----------------------------------
Sorry to interject mid-convo, but I may use the above text for a sign to place by the board.
Sigh, email sent before I was finished typing:
Sorry to interject mid-convo, but I may use the above text for a sign to place by the board. If you all think that is appropriate and approve, let me know.
_______________________________________________ Pycon-openspaces mailing list Pycon-openspaces@python.org https://mail.python.org/mailman/listinfo/pycon-openspaces
_______________________________________________ Pycon-openspaces mailing list Pycon-openspaces@python.org https://mail.python.org/mailman/listinfo/pycon-openspaces
-- Trey Hunner Truthful Technology, LLC http://truthful.technology
On Wed, Apr 26, 2017 at 6:18 PM, Trey Hunner <trey@truthful.technology> wrote:
Chiming in a little late. Thanks for re-starting the conversation Anna and thanks for the bot explanation Hobson.
Zak, I think that blurb sounds good.
Ewa, I really like the idea of using a blurb for the open spaces board so people filling out a card know how to promote it on Twitter.
I think a slightly shorter blurb might stand out more near for the in-person board. Maybe a one sentence one: "Tweet the time, room number, and description of your event using #PyConOpenSpace and the Twitter @openspaces_bot will help you promote your open space."
Unfortunately, too late. This has already gone to print. This close to the conference, we have pretty quick turn over :)
Also I wonder whether we should remind folks looking at the board that find open space reminders on Twitter too. Same idea, but different audience (since most people looking at the board will not be open space organizers but open space attendees).
Of course, thanks :) On Tue, Apr 25, 2017 at 12:27 PM, Ewa Jodlowska <ewa@python.org> wrote:
On Tue, Apr 25, 2017 at 2:15 PM, Zak Kent <zak.kent@gmail.com> wrote:
Hi everyone,
I just setup a twitter account with the name @openspaces_bot and will set up the bot using that account this week sometime. For the moment it's still using the old @tw_testy account.
I'm totally willing to help out with the a sentence or two promoting the use of the bot for the blog post if needed. I noticed in the google doc that there is already a section talking about the use of the #PyConOpenSpace hashtag. I've included a message about the bot that could possibly be added to that paragraph below. Feel free to change anything or everything :)
------------------------------------------------------------ ----------------------------------- # possible message about bot
"If you would like to reach a wider audience when promoting your Open Space, please take advantage of the Open Spaces Twitter Bot, @openspaces_bot. Send out a tweet that contains the hashtag #PyConOpenSpace, the time of your event, and the room number where the event will be held and the bot will retweet your message 15 minutes before your Open Space is scheduled!" ------------------------------------------------------------ -----------------------------------
Sorry to interject mid-convo, but I may use the above text for a sign to place by the board.
participants (7)
-
Anna Ossowski -
Anna Ossowski -
Brandon Rhodes -
Ewa Jodlowska -
Hobson Lane -
Trey Hunner -
Zak Kent