Skip to content
This repository has been archived by the owner on Nov 21, 2018. It is now read-only.

Evangelism: Social Media #109

Closed
mikeal opened this issue Jan 28, 2015 · 21 comments
Closed

Evangelism: Social Media #109

mikeal opened this issue Jan 28, 2015 · 21 comments

Comments

@mikeal
Copy link
Contributor

mikeal commented Jan 28, 2015

I've been amping up what we currently do on social media. I'm going to document it so that people can jump in to help that aren't just me :)

The current channels we have are:

We're working on a better vanity URL for G+ and taking over @iojs on twitter (which is a dead account).

A few high level goals:

  • Create a bi-directional relationship with the broader community.
    • Post links to interesting developments in the project like issues that are of broad interest, etc.
    • Respond to any issues or complaints about iojs or nodejs (currently using Sprout Social to track all of that)
    • Favorite and retweet posts from the community
  • PMA (Positive Mental Attitude)
    • Never post anything negative or respond negatively.
    • When people complain, kill them with kindness :)

The more time I spend in the feed the more I think that having such an active presence could be what brings the broader community in to the project. We can use this presence to reach end users and the front end developers we've traditionally lacked engagement with.

I'm still exploring and experimenting with tooling. All the good tools cost some amount of money and are either per-user or have tiers with user caps so it's going to be hard to have a lot of people helping out :(

Let me know about anything you'd like promoted or if you feel like there's something we should be doing that we aren't yet.

@julianduque
Copy link
Contributor

Would love to help on this front, also do you think it would be valuable to have social media channels or communications in other langs?

@mikeal
Copy link
Contributor Author

mikeal commented Feb 1, 2015

@julianduque ya, I was thinking about that earlier, I'm just wondering what the best way to organize it is. Does it make sense to have it integrated with the rest of the localization work we want to spin up?

@julianduque
Copy link
Contributor

@mikeal it can be handled using different accounts, eg: (@iojs_es, @iojs_cn) but we would need owners in charge of the communication in those account, localization work makes sense in this if we want to send the same message using the different channels, otherwise channels can be independent in matters of what kind of content is being published in that lang.

Regarding tools I mainly use TweetDeck to handle multiple accounts and scheduled messaging but will want to hear another suggestions in this matter.

I see value in this because not a lot of people knows english and sometimes the language barrier doesn't bring enough people to the technology, what we want to do in ColombiaJS is having quality and updated content in spanish to help bring down this barrier, not about other languages or regions where english isn't official.

@mikeal
Copy link
Contributor Author

mikeal commented Feb 2, 2015

@julianduque ya, that all makes sense, but what I was wondering if how it should be organized in terms of the group of people doing the work. For instance, should we do a iojs-co working group which covers social media, evangelism, and possibly even documentation localization for Columbia? If you have a few other people from Columbia that would like to help out maybe we could experiment with creating a localization group for you all?

@julianduque
Copy link
Contributor

@mikeal Yes, I think it would be a good idea (but not only for Colombia of course, it could be just iojs-es)

So, if there is enough people interested we can have iojs-pt in portuguese or iojs-ja in japanese, etc. see learnyounode as translation example.

So like this we can coordinate communication in spanish for social networks (through @iojs_es, help local meetups in latin america and spain and answer questions all in our language :)

Summoning @a0viedo and @italoacasas who have been doing a great job in translating things to spanish and running nodeschool, into this experimental working group, would love to see others involved though :)

@a0viedo
Copy link
Member

a0viedo commented Feb 3, 2015

I think it could be really positive to have working groups for different languages. At nodeschool we've been working to increase the number of resources in Spanish, but there's a lot of work to do. For example, I don't think we have any blog post about iojs translated to Spanish.

I'm using also TweetDeck as tooling, are there other alternatives that we can try?

@therebelrobot
Copy link
Contributor

+1 to language specific content/evangelism groups. It is a million times better to have a native speaker curate content rather than us try to translate into a second or third language.

@julianduque
Copy link
Contributor

@a0viedo finding good content in spanish is difficult tho, we should be doing something so here is a great opportunity to tackle this ;) also better to have original content than translated IMHO, translation efforts in this working group should be focused more in the website/documentation side of things

@a0viedo
Copy link
Member

a0viedo commented Feb 6, 2015

@julianduque we can start with the weekly updates. My neutral spanish it's not getting better.

@mikeal
Copy link
Contributor Author

mikeal commented Feb 6, 2015

@julianduque & @a0viedo would you two like a repository where you organize all of this, maybe iojs/iojs-es?

@therebelrobot
Copy link
Contributor

@mikeal what if we had an iojs/iojs-i18n repo for organizing this? I know we'll need additional space for other languages.

@therebelrobot
Copy link
Contributor

Than have separate branches or separate issues for different languages?

@mikeal
Copy link
Contributor Author

mikeal commented Feb 6, 2015

I think that these groups will be collaborating with a bunch of different working groups. If they have a language specific space to organize that they can share and edit each others work much easier. If we lump it all together the japanese translators will be getting notifications about all the spanish work and vice versa.

@mikeal
Copy link
Contributor Author

mikeal commented Feb 6, 2015

oh, and branches don't really work because most of this is organized in Issues.

@a0viedo
Copy link
Member

a0viedo commented Feb 7, 2015

@mikeal iojs/iojs-es would be nice.

@mikeal
Copy link
Contributor Author

mikeal commented Feb 7, 2015

@julianduque @a0viedo you have a repo and a team now :) https://github.com/iojs/iojs-es

Let me know if there are any other people you would like to have added.

@bnb
Copy link

bnb commented Feb 12, 2015

Hey there. This is a bit off the topic this Issue has gone to, but it seems like the best place to put it.

I'd absolutely love to get involved with content creation. I'd be happy to write blog posts and update social media accounts. I'm a pretty decent writer, and have written about JavaScript before (at http://methodjs.com/, which is about to go offline, as a part of a Social Media academic course). I would love to get started anywhere I can--I'm open to learning whatever is needed to write accurate and succinct posts on all fronts.

Let me know what I can do to help out, if you'd like to have me.

@mikeal
Copy link
Contributor Author

mikeal commented Feb 12, 2015

@bnb I would love help with the weekly updates :) pop in to this thread #122 and we'll figure out how to collaborate on it :)

@bnb
Copy link

bnb commented Feb 13, 2015

@mikeal I'd like to post the weekly update to EchoJS. I'll post it from my personal account, but for the future I created an account with the username iojs, which I'll be happy to hand over to you.

@mikeal
Copy link
Contributor Author

mikeal commented Feb 13, 2015

@bnb +1 :)

@bnb
Copy link

bnb commented Feb 13, 2015

Also made a Hacker News account called iojs, with the same (42 character) password, for future use.

Edit: And, of course, I'll be happy to hand it over.

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

5 participants