Hi Rich,

the coming tweets are all scheduled for 3 pm and 3 am, posting a podcast link after a video link. The first scheduled link was just posted.

The queue is filled until June 14th 3am and can successively be feeded with more tweets. For the videos, I suggest to post them according to the playlist order, for the podcasts, I've started with the oldest poscasts tagged as APACHECONNA2017.

Regards,

Michael


Am 08.06.17 um 13:48 schrieb Rich Bowen:
So, to whichever one of you scheduled the tweets, two things.

1) THANK YOU!!! This is an enormous help, and something that I haven't
had time to get to ... well, since the event.

2) For future scheduled tweets, please spread them out. Say, one at 9am,
and the other at 2pm, for example. This gives us wider timezone
coverage, rather than having both tweets go out at the same time.

But, again, thank you so much.

On 06/07/2017 09:46 AM, Rich Bowen wrote:
As you know, we have all of our video and audio content from ApacheCon
posted at this time.

https://www.youtube.com/playlist?list=PLbzoR-pLrL6pLDCyPxByWQwYTL-JrF5Rp
for the video, and of course feathercast.apache.org for all of the audio.

I need help scheduling this content for twice-daily tweets on
@feathercast to keep this content in front of the world until the next
event.

If you are a Twitter user, and use the TweetDeck tool -
https://tweetdeck.twitter.com/ - I can add your account to the
@feathercast "team", thus giving you permission to tweet on behalf of
that account, and schedule future tweets.

Or, we could use a tool like HootSuite or Buffer, but if we do that I'd
like to coordinate with ComDev so that we can perhaps share the costs of
such an account, since they're not cheap. Tweetdeck is free and seems
like a reasonable place to start.

Anyways, I'd like to see a video, and a podcast, scheduled every day, so
that we are making the most of our investment in this content. Please
contact me if you are willing/able to participate in this process. I'd
also appreciate someone being willing to help me document the process,
so that it's easier for people to participate in the future.

Thanks.




Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to