Evangelism WG

[mikeal]

The website team is currently undertaking two tasks: messaging and website development.

Over the last week it has become clear that io.js needs a team that is just working on messaging and evangelism. I can't even keep up with all he requests for speakers and podcast interviewees. In the last week we've also gain a twitter, G+, youtube and facebook pages/accounts.

Having a fork is confusing enough, we need to build simple messaging and stay consistent across all these channels, especially in these first few months, if we want to continue to grow the user base and gain even more contributors.

What I would like to do is break off the messaging and management of social media in to an evangelism working group. This group would then work closely with the website team to update the messaging and coordinate any changes in the messaging. The website team would then be free to focus on the site functionality, content and design.

[snostorm]

Good topic @mikeal. I'm not sure if this should be considered its own group or not, as there are a lot of coordinated efforts -- like press release/announcement sync across mediums -- needed across the two groups.

Regardless, I think it is important to define some roles/ownership spheres within the WG to make sure this stuff is all happening. It actually might make sense to break things up this way and use the existing "Website" WG meetings for the sub-project leads/reps to all check in on progress and coordinate the next round of efforts.

[snostorm]

It would be great if this team helped to track some external media as well. Who wrote articles about us? Positive/negative feedback? Maybe a good tutorial... etc. Things we can later blog about, retweet, post on a "media" page, etc.

[mikeal]

I'd also like this group to maintain a list of contributors, TC members, WG members, who are interested in speaking on podcasts or at conferences so that we can forward along requests to good people.

[mikeal]

A few things we need to get organization around:

• Twitter Account
• Youtube Page
• Google Plus Page
• Facebook Page
• Soundcloud Page

@SVincent registered the soundcloud page and is creating audio-only versions of the TC and WG meetings.

As far as the other social media accounts, I have them all setup in buffer which is a great system for managing and scheduling outreach but I have a limit number of "managers" I can add.

[mikeal]

I've also reached out to people at twitter to see if we can move official_iojs to just iojs since that account is dead. This used to be really easy but now I'm having difficulty so if anyone has additional contacts at twitter we can work with that would be great.

[dotproto]

The goal with the SoundCloud page was to create a podcast that folks could subscribe to to stay up to date with the project. At the moment I'm using the username iojs (https://soundcloud.com/iojs) and the name "io.js Audio". All audio is a straight rip of the YouTube videos with some custom ID3 work.

I've put in a request to join the SoundCloud Podcast beta program. I don't know how long the review process takes, but if someone has contacts at SoundCloud and could help get this account into the beta that would be fantastic.

[mikeal]

Reached out to Tiffany at Soundcloud, she got me in the beta program a year ago for another account :)

[mikeal]

Tiffany got us in the podcast beta, feed is here http://feeds.soundcloud.com/users/soundcloud:users:134301918/sounds.rss

[dotproto]

Awesome! I just updated the account to add some more podcast-y info and submitted it to iTunes. I had to re-make the io.js logo because iTunes requires a minimum 1400x1400 image. High res version available here.

@mikeal, do you know if SoundCloud has any kind of OSS licensing? We exceeded the maximum amount of time for the free tier, so I put down for a pro subscription.

[mikeal]

@SVincent I don't know of anything like that. I'm paying for a few things out-of-pocket at the moment as well. I'll put together a list of things individuals are paying for and see what our options are while we are in this "pre-foundation" phase :)