search

nodejs / nodejs-hu

io.js magyarul
7 stars 13 forks source link

Translate latest Medium post #2

Open madbence opened 9 years ago

madbence commented 9 years ago

io.js Week of February 6th 2015

Translation can be published on Medium.

tamascsaba commented 9 years ago

Update: io.js Week of February 13th 2015 io.js Week of February 20th 2015

We do every medium post seprecate issue?

bling5630 commented 9 years ago

I have started io.js Week of February 13th 2015 https://medium.com/node-js-javascript/io-js-week-of-february-13th-2015-7846b94074a2 this yesterday :)

On 23 February 2015 at 12:00, Tamás Csaba notifications@github.com wrote:

Update: io.js Week of February 13th 2015 https://medium.com/node-js-javascript/io-js-week-of-february-13th-2015-7846b94074a2 io.js Week of February 20th 2015 https://medium.com/node-js-javascript/io-js-week-of-february-20th-2015-48486615980

— Reply to this email directly or view it on GitHub https://github.com/iojs/iojs-hu/issues/2#issuecomment-75523121.

Tamas Puski

Journeyman Ninja - Chünin @ IseeQ http://www.iseeq.hu/en

Cell & Viber: +36.30.533.0873| Skype: tamas5630 | LinkedIn http://www.linkedin.com/pub/tam%C3%A1s-p%C3%BCski/31/386/656 |TPuski https://twitter.com/TPuski|

bling5630 commented 9 years ago

Hi, I created a medium folder with translated "io.js_ofFebruary13th2015.md" post but it isn't complete and has several formal mistakes, what should be the next step?

Sorry for my lack of experiences with this platform:(

Tamas

bling5630 commented 9 years ago

Update:

io.js Week of February 27th

flaki commented 9 years ago

Hi folks! I can help out translating the posts but first we have to decide on

We are several posts and release versions behind, so I would say we should do monthly releases, aggregating the weekly updates into a single post (that should be more manageable), while in the meantime translating individual posts separately.

I would even say it would be nice to have a post that is not a mere translation of the node.js vs io.js post from February, but one that includes the primer on the reconciliation efforts, as things have progressed enough that translating and publishing the original article could be misleading.

Comments, thoughts are much welcome!

bling5630 commented 9 years ago

Hi Flaki,

Welcome on board, at first glance I am totally agree with your suggestions so if you have a free slot this week let's set up a rapid talk about the next steps. Monthly releases fine for me, I could separate time for translation as well as reviewing. So waiting for your response regarding the date, here or other channels :)

Have a nice evening,

Tamas

madbence commented 9 years ago

Welcome in the team @flaki !

The optimal workflow for me would be:

  1. If there is no issue for a blogpost, create one and assign it to yourself. If there is an issue for it, just assign it to yourself
  2. Write the post in markdown, and create a pull request for it :smile:

We should always try to translate the latest posts, and if we have time, we can translate older ones too.

For helping the review process, every translation pr should contain 2 commits, the first is the original post, the second one is the translated (this was we can see side-by-side comparison). I'm not sure whether the original ones are available in markdown or not :confused:

If you think that you want to merge several posts into one, that's fine for me :wink: