Skip to content
This repository has been archived by the owner on Jan 20, 2022. It is now read-only.

Welcome! #1

Closed
9 of 11 tasks
mikeal opened this issue Feb 7, 2015 · 11 comments
Closed
9 of 11 tasks

Welcome! #1

mikeal opened this issue Feb 7, 2015 · 11 comments

Comments

@mikeal
Copy link

mikeal commented Feb 7, 2015

Welcome, new localizations team :)

To get this team up and running you have a few initial tasks to accomplish:

  • Create a README.md for this repository, it should include:
    • A "call to action" pointing to the Issue tracker for new translators to find tasks.
    • A list of the team members.
    • Instructions on how to log an issue to be added to this team.
  • Set the repository description. This should not be in English, it should be in the language for this community :)
    • Social Media
    • Create a twitter account for this language. Share the password privately with the team.
    • Create accounts on other social media popular in this language. Share the passwords private with the rest of the team.
    • Make sure you use these accounts not just to promote newly translated material but also to attract people in your community to help with translation tasks.
    • Optional: If you plan to do a Google hangout w/ your localization team have @mikeal add you to the Google+ account so that it can post to the iojs YouTube channel. Once you are added there is documentation on how to setup a hangout-on-air.
  • Finally, create a new Issue to translate and publish the latest io.js post. Once translated you should post it wherever you think it will get the most visibility to the community speaking you language, you don't have to post it to Medium unless you think that it is best.
@edsadr
Copy link
Member

edsadr commented Feb 7, 2015

Ok so far the README is done and the description was changed, some items at the README are missing because would be nice to have an open discussion about the best approach to work, establish the rules submitting issues and assigning them.

I tried to register at Twitter but @ios_es is taken, not sure if someone owns it here?

@stringparser
Copy link

Is @iojs_es taken? let me check. Yes it is, sure has to be someone here, is empty. I still can commit anything I guess mikeal is waiting to have more people. Anyhow, I can take the translate post part.

@stringparser
Copy link

I wanted to write "I still cannot commit" haha, these fingers... :)

@mikeal
Copy link
Author

mikeal commented Feb 7, 2015

I think maybe @a0viedo or @julianduque registered twitter, they'll pop in here soon :)

@stringparser
Copy link

Ok, in the mean time I have written to this account. Let see :D

@stringparser
Copy link

For sharing passwords this is what they are saying in iojs-de

you can use https://keybase.io/ to send encrypted message.

I've setup an email at: [email protected]

@a0viedo
Copy link
Member

a0viedo commented Feb 8, 2015

Hey everyone, I don't registered @iojs_es. Maybe @julianduque?

Finally, create a new Issue to translate and publish the latest io.js post. Once translated you should post it wherever you think it will get the most visibility to the community speaking you language, you don't have to post it to Medium unless you think that it is best.

Can we discuss this? I created the translation on Medium, but I don't know if it's the best way to get visibility.

@stringparser
Copy link

I don't know either, but I think Medium is the place. Alternatives would be wordpress or blogspot, in es_ES at least. Anyhow, what do you guys think?

@jamlfy
Copy link

jamlfy commented Feb 10, 2015

I think there are better options, I suggest using Ghost, but not if now multilanguage

@julianduque
Copy link

I registered @iojs_es but was disconnected from the interwebs for a week, password was shared with the team so all good now, sorry for not sharing it on time 😅

@stringparser
Copy link

I'm just glad you are here 😄

@stringparser stringparser added this to the go live milestone Feb 14, 2015
stringparser added a commit that referenced this issue Feb 14, 2015
@edsadr edsadr closed this as completed Jul 12, 2016
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

6 participants