Skip to content
This repository was archived by the owner on Aug 1, 2019. It is now read-only.

Social Media Campaign to Use/Test RC candidates #95

Closed
mikeal opened this issue Jun 8, 2015 · 4 comments
Closed

Social Media Campaign to Use/Test RC candidates #95

mikeal opened this issue Jun 8, 2015 · 4 comments

Comments

@mikeal
Copy link
Contributor

mikeal commented Jun 8, 2015

Let's help these people out with a good campaign nodejs/nodejs.org#369

@bnb
Copy link
Contributor

bnb commented Jun 8, 2015

How about a scheduled series of weekly tweets (different text and multiple days) to alert people/remind them to try it out?

@bnb
Copy link
Contributor

bnb commented Jun 8, 2015

Want to help Node (|| io.js)? Run the nightly builds to help test the next major version! <link>

Test the Node (|| io.js) nightly builds to find bugs and improve the next major release! <link>

Be on the bleeding edge and help node by running the nightly builds! <link>

We need YOU! Help Node (|| io.js) by running the nightly release candidate build! <link>

Like Node (|| io.js)? Like testing? Help Node (|| io.js) out by testing the nightly release candidates

@mikeal
Copy link
Contributor Author

mikeal commented Jun 8, 2015

Is there a single link to "latest nightly" we can use for all of these?

What is the idea schedule to reach all active timezones but not annoying people in the same timezone?

@bnb
Copy link
Contributor

bnb commented Jun 8, 2015

@mikeal A single, immutable link is definitely a possibility, and would make the messages useful no matter when they are viewed. @nodejs/build is probably the group to talk to, as it would be a forwarding thing on the domain.

As for schedule for maximum reach, here's a basic plan:

  • Monday: Mid-day US
  • Wednesday: Mid-day EU
  • Friday: Mid-day Asia/Russia

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants