Welcome!

[mikeal]

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.

[jbergstroem]

Hey, fellow Swedes. Happy to join and help out with occasional translation efforts or similar - but won't be driving this bus. Feel free to ping me if you want to get it going and need some extra horsepower.

Edit: have a look at the Norwegian team for inspiration :-)

[fl0w]

I'll pitch in on this for sure. Registered twitter account @iojs_sv, and iojs.se (following iojs.no convention). I'll complete a pull request tonight regarding README.md. Accounts will be shared as requested (or even transfered?).

[ralphtheninja]

I'd be happy to help out with translations.

[jbergstroem]

@fl0w - great job picking up domain/twitter. Could you possibly do a PR for README.md? (see @mikeal's suggestions above) -- it'd be a good way to get going. Also, I think we should seek out a few additional people if possible. Ask around :-)

[fl0w]

@jbergstroem Aye, I was going to - but apparently my CC got rejected (due some non-activated VISA feature ... sigh) and now the domain is taken. Noticed rejection post vacation :(.

Anyway, I was wondering if it's worth waiting for the potential merger to settle before we kick this off or should I just get right to it? I'm counting on you and @ralphtheninja to be part of the initial team Swedish i18n team.

[jbergstroem]

@fl0w I'd suggest not holding up for the potential merger; not based on its progress but rather that the work that's being put in regardless will be for good use. As mentioned previously, I probably won't be a strong driver of this project but are happy to occasionally help out. The reasoning behind this is that I'm less a evangelist/social media guy, more a developer.

[jbergstroem]

@fl0w still keen to get this off the ground? iojs-related stuff is now less relevant but having a Swedish entry page with the most common questions answered would be pretty awesome. Most of our Scandinavian neighbours already seem to have something going; hopefully that could work as motivation :-)

[jbergstroem]

This group looks very active; people in Sweden should attend and try to rally some over to this issue!

[fl0w]

@jbergstroem I apologise for not committing to this issue previously. I had issues finding motivation to translate docs to Swedish, as I know most of us actually prefer english terminology anyway - especially myself.

What's the expected scope for a sv_SE l10n? Blog, homepage and releases notes? Is @mikeal's original list still relevant as a starting point?

Edit; Just to be clear, I'll do it - depending on the expected scope

[fl0w]

How do I create a pull-request with a README to a repo without content, i.e. "not forkable"?

@jbergstroem mind committing an empty'ish README? (I have no push rights so I need to fork)

[jbergstroem]

@fl0w I think @mikeal's list is somewhat out of date. I'll chase what's required and see if I can get permissions to add a skeleton. Happy to get this going, but don't forget that you don't have to participate :) As I've outlined above I'm probably not going to be very active but I'd love to help out here and there -- if i18n/website/docs/community isn't your thing then feel no pressure.

[fl0w]

@jbergstroem Understood. I'll try to get the ball rolling - and we'll just have to see what it becomes. Just ping me whenever there's a skeleton/something forkable and I'll PR from there. I'm happy to work with community questions but again - I'm subjectively hesitant about translating docs.